| name | Feature Spec Definition |
| description | Generate structured specification documents in docs/plan/<feature>/ from ambiguous requirements. |
| user_invocable | true |
Overview
A skill for defining feature development specifications.
Interviews ambiguous requirements and generates specification documents in docs/plan/<feature>/ aligned with Clean Architecture layers.
Execution Steps
Step 1: Requirements Interview
Confirm the following in a single set of questions:
- Feature name (English kebab-case, e.g.,
user-profile)
- Purpose and background of the feature (why build it)
- Target users and usage scenarios
- In Scope / Out of Scope
- Affected entities (new or existing changes)
- Key use cases (1-5)
- API endpoints (expected)
- Frontend screen layout (expected)
- Open items
Step 2: Specification Document Generation
Based on the answers, create the following files in docs/plan/<feature>/.
Refer to the specification file overview in docs/plan/README.md for the items to include in each file.
00_OVERVIEW.md - Feature overview, purpose, scope01_DOMAIN_MODEL.md - Entity changes, business rules02_DATA_ACCESS.md - Repository and DB changes03_USECASE.md - UseCase layer changes04_API_INTERFACE.md - API endpoint specifications05_FRONTEND.md - Frontend UI specifications
For backend-only or frontend-only features, omit unnecessary files.
Mark undecided parts as TBD.
Step 3: Spec Review Summary
After generation, present the following:
- List of generated files
- Summary of confirmed items
- Open items and next discussion points to resolve
- Guidance on reflecting changes to
docs/domain/ if needed
Rules
- Specifications are consolidated in
docs/plan/<feature>/ (do not scatter them elsewhere)
- Entity definitions follow Zod Schema First (per
docs/web-frontend/typescript.md)
- Guide important decisions to also be recorded in
docs/domain/decisions.md
Reference Documents
docs/plan/README.mddocs/domain/README.mddocs/backend/server-architecture.mddocs/web-frontend/architecture.md
