技術ドキュメント
Kiro-style Feature Spec Generator
Produces exactly three files under docs/specs/<feature-slug>/: requirements.md (behavior and acceptance, EARS), design.md (normative technical contract: single source of truth for APIs, JSON payloads, HTTP status codes, and operational policies), tasks.md (ordered work and verification). MUST match the repository canonical example layout when docs/example/{requirements,design,tasks}.md exist—same section order and heading levels; do not invent top-level sections, rename stable headings, or rely on custom HTML id anchors for cross-links. Design states concrete values only: forbid "pick one", "either A or B", "before verification", and placeholder tables (e.g. "_e.g. 200_"). Cross-links use real Markdown headings so URL fragments match editor and GitHub slug rules. Use when the user asks for SDD, spec, PRD, Kiro-style feature specs, or separate requirements / design / tasks documents. Supports Requirements-First and Design-First workflows.