kiro-skill

To turn a feature idea into requirements and design documents, describe the feature and a phase-driven workflow generates formal artifacts with explicit approval gates. It produces structured files for requirements, design, and tasks within a dedicated specs directory.

Generating actionable task lists from design documents requires an explicit approval gate to validate the design phase. Once approved, the workflow converts the validated design into a structured tasks.md file containing implementable actions.

A gated workflow for product team specifications enforces incremental reviews and approvals across requirements, design, and task phases. This approach maintains quality and alignment by blocking progression until each artifact is explicitly approved.

Create audit-friendly design documents by running a structured workflow that enforces artifact templates and YAML frontmatter-based discovery. This produces formal, traceable requirements and design files suitable for team audits.

The task-generation workflow requires no external dependencies to operate. You simply provide the feature description, and the built-in process generates the requirements, design, and tasks artifacts directly in your project.

Approval gates for requirements and design artifacts prevent misalignment by requiring explicit review before moving to the next phase. This gated progression ensures product teams validate the idea, formal requirements, and design before generating implementation tasks.