iikit-01-specify

Use specification templating to convert natural language descriptions into governance-aligned specs. The Skill generates a draft with branch names, user scenarios, requirements, success criteria, and a quality checklist—reducing scope ambiguity before development.

Feature specifications should contain user scenarios, requirements, success criteria, and a quality checklist. This Skill assembles those sections into a templated structure and validates alignment with your project constitution to ensure governance compliance.

Yes. The Skill generates concise feature branch names directly from your natural language description, ensuring naming consistency with your governance framework without manual formatting.

The Skill loads your project constitution during specification creation and validates your draft against it. Phase validation guides you to next steps like clarification or planning when governance gaps are detected.

After drafting, the Skill provides a quality checklist and recommends next actions: use /iikit-02-clarify to resolve ambiguities or /iikit-03-plan to move forward with detailed planning based on your specifications.

Use specification templating when coordinating across product teams or enforcing governance standards. Templated structures reduce misalignment, ensure consistent coverage of scenarios and success criteria, and streamline review cycles.