What problem does it solve?
This Skill automates creating a consistent specification directory and initial files from a short project description or discovery brief, removing manual setup, naming conflicts, and template lookup friction so teams can move faster from discovery to planning.
Core Features & Use Cases
- Feature name generation: derive a unique, filesystem-safe feature-name from the project description and resolve naming conflicts automatically.
- Template-driven initialization: read templates from .kiro/settings/templates/specs and generate spec.json and requirements.md with placeholders replaced and timestamp and language detection applied.
- Brief-aware clarification: read .kiro/specs/{feature}/brief.md when present to pre-fill project description or interactively ask clarifying questions to ensure who/what/why are specified.
- Use case: a product manager converting discovery output into a standardized spec directory without manual file editing.
Quick Start
Initialize a new specification from the project description "social sign-in for mobile app".