iikit-01-specify

Create structured feature specifications from natural language descriptions.

47|4|Updated Feb 3, 2026

Search Tags:#specification #requirements #governance #feature #branch #templating

Ready to run

npx skills add https://github.com/intent-integrity-chain/kit --skill iikit-01-specify

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: iikit-01-specify
Source: https://github.com/intent-integrity-chain/kit/tree/main/.claude/skills/iikit-01-specify
Command: npx skills add https://github.com/intent-integrity-chain/kit --skill iikit-01-specify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating clear, governance-compliant feature specifications from natural language descriptions to reduce scope ambiguity and misalignment.

Core Features & Use Cases

Generate a concise feature branch name from the description.
Assemble a complete draft specification using a templated structure (user scenarios, requirements, success criteria, and a quality checklist).
Validate alignment with project constitution before drafting and guide next steps (/iikit-02-clarify or /iikit-03-plan).

Quick Start

Use this skill to convert a feature idea into a draft spec. Example: /iikit-01-specify Add user authentication with passwordless login.

Frequently Asked Questions about iikit-01-specify

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

FAQPage Schema

How do I turn a feature idea into a structured specification?▼

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.

What should a feature specification include?▼

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.

Can I generate branch names automatically from feature descriptions?▼

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

How do I ensure my specifications align with project governance?▼

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.

What happens after I create a draft specification?▼

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.

When should I use specification templating instead of free-form requirements?▼

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.