iikit-01-specify

Generate feature specifications with user stories, functional requirements, and success criteria from natural language descriptions.

1|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/hafidzlvm/opencode --skill iikit-01-specify-hafidzlvm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: iikit-01-specify
Source: https://github.com/hafidzlvm/opencode/tree/main/.tessl/tiles/tessl-labs/intent-integrity-kit/skills/iikit-01-specify
Command: npx skills add https://github.com/hafidzlvm/opencode --skill iikit-01-specify-hafidzlvm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Turning a rough product idea into a structured, testable feature specification is slow and inconsistent. This Skill converts a natural language feature description into a complete spec.md with prioritized user stories, Given/When/Then acceptance scenarios, functional requirements (FR-XXX), measurable success criteria, and a quality checklist. ## Core Features & Use Cases - Structured Spec Generation: Creates a feature branch and directory, then writes a specification following a standard template with user stories (P1/P2/P3), edge cases, requirements, and success criteria. - Phase Separation Validation: Scans the draft for implementation details that belong in the planning phase and auto-fixes violations so specs stay technology-agnostic. - Bug-Fix Intent Detection: Analyzes the description to distinguish bug fixes from new features and suggests the appropriate workflow. - Use Case: A product manager types a feature idea like "add user authentication with OAuth" and receives a ready-to-review spec.md with acceptance scenarios, a requirements checklist, and the recommended next workflow step. ## Quick Start Ask the AI to run /iikit-01-specify followed by a plain-language description of the feature you want to specify.

Frequently Asked Questions about iikit-01-specify

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

FAQPage Schema
How do I create a feature specification from a natural language description?▼

Run /iikit-01-specify followed by your feature description. The skill generates a branch, creates a spec.md with prioritized user stories, functional requirements, success criteria, and a requirements quality checklist.

What should a good feature specification include?▼

A specification should include independently testable user stories with priorities, Given/When/Then acceptance scenarios, functional requirements (FR-XXX), measurable technology-agnostic success criteria, edge cases, and key entities when data is involved.

Does the specification skill work on Windows with PowerShell?▼

Yes, the skill ships both Bash and PowerShell scripts for feature creation and post-phase commits. Windows users run the pwsh variants with equivalent parameters like -Json and -ShortName.

Can I use this for bug fixes instead of new features?▼

The skill detects bug-fix intent through contextual analysis and suggests switching to /iikit-bugfix. You can confirm to proceed with a specification if the work is genuinely a new capability.

What happens when I re-run the specification on an existing spec?▼

The skill performs a semantic diff comparing stories, requirements, and criteria between the existing and new content. It shows downstream impact warnings and asks for confirmation before overwriting.

Why does my specification get flagged for implementation details?▼

Specifications must describe what users need, not how to build it. Framework references, database schemas, and architecture patterns belong in the planning phase, so the skill auto-fixes these violations and re-validates.