write-statement

Converts an architect_spec.json blueprint into a complete competitive programming problem statement with samples and constraints.

1|Updated Jul 17, 2026
One-click install
npx skills add https://github.com/vaskoyudha/agent-skills-problem-gen --skill write-statement-vaskoyudha
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-statement
Source: https://github.com/vaskoyudha/agent-skills-problem-gen/tree/main/.qwen/skills/write-statement
Command: npx skills add https://github.com/vaskoyudha/agent-skills-problem-gen --skill write-statement-vaskoyudha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing contest-quality competitive programming problem statements is error-prone: ambiguous terms, missing indexing conventions, incomplete constraints, and weak sample tests cause solver confusion and rejudging. This Skill transforms a structured architect blueprint into a precise, unambiguous problem statement package. ## Core Features & Use Cases - Statement Generation: Produces title, story, statement, input/output format, constraints, and sample tests as a structured problem_draft.json from an architect_spec.json input. - Anti-Ambiguity Checklist: Enforces an 8-item verification gate covering term definitions, indexing, edge cases, output format, and constraint completeness before any output is accepted. - Constraint-Complexity Design: Maps intended algorithmic complexity (O(N), O(N log N), O(N^2), etc.) to appropriate constraint bounds so brute-force solutions fail and intended solutions pass. - Use Case: Given an architect spec for a binary-search-on-answer problem rated 1400, generate a full statement with a motivating story, 3-5 purposeful sample tests with explanations, and constraints that force the intended complexity. ## Quick Start Convert this architect_spec.json into a complete problem statement with story, input/output format, constraints, and sample tests, then run the anti-ambiguity checklist.

Frequently Asked Questions about write-statement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a competitive programming problem statement from a blueprint?▼

Provide an architect_spec.json containing domain, topic, difficulty, core concept, and constraint hints. The Skill produces a problem_draft.json with title, story, statement, input/output format, constraints, and sample tests, verified against an anti-ambiguity checklist.

How to set constraints that match the intended solution complexity?▼

Use the constraint-complexity table: O(N log N) maps to N up to 10^5-5x10^5, O(N^2) to 2000-5000, O(2^N) to 20-22. Set bounds so the intended solution passes comfortably while the next-slower complexity class fails.

What makes a competitive programming problem statement unambiguous?▼

An unambiguous statement defines every term on first use, specifies indexing (0-based or 1-based), states edge case behavior, gives exact output format, and bounds every variable. All 8 checklist items must pass before the draft is finalized.

How many sample tests should a problem statement include?▼

Include 2-5 samples, each with a distinct purpose: basic mechanics, non-obvious behavior, and an edge case such as N=1. Every sample needs input, output, and an explanation, and must be small enough to trace by hand.

What happens when the architect spec is incomplete or contradictory?▼

The Skill does not guess missing information. It outputs a NEEDS_CONTEXT JSON object describing what is missing or contradictory, since a partial draft with fabricated constraints is worse than no draft.