Generate requirements, design, and task documents in the .kiro/specs workflow.
npx skills add https://github.com/PeterFile/my-common-skills --skill kiro-specs
Please help me install this Agent Skill. Skill: kiro-specs Source: https://github.com/PeterFile/my-common-skills/tree/main/kiro-specs Command: npx skills add https://github.com/PeterFile/my-common-skills --skill kiro-specs
Kiro specs provide a structured, repeatable way to capture ideas as formal, versioned artifacts (requirements, design, and task plans) that teams can review, approve, and execute.
Start a new spec by naming a feature (e.g., "user-authentication"). Kiro will scaffold the spec directory and generate the three core documents, ready for review and iterative refinement.
High-intent search queries and answers about installing and using this skill.
To turn ideas into structured requirements and design documents, you can generate Kiro spec artifacts. This process scaffolds requirements.md, design.md, and tasks.md files with user stories, architecture details, and test-driven implementation plans.
Creating traceable task lists from software requirements is best handled by generating a tasks.md document within a Kiro spec. This approach produces a clear, test-driven implementation plan that aligns directly with your approved requirements and design.
The EARS format for software acceptance criteria works by structuring user stories within a requirements.md document. It captures specific conditions and system responses to ensure formal, testable validation rules for feature design.
Yes, you can enforce approval steps before moving from design to task planning. The Kiro specs workflow enforces explicit phase approvals before advancing to the next stage, ensuring team alignment and artifact traceability.
You need a specific directory structure for software design and task documentation, specifically the .kiro/specs/{feature-name}/ path. This structure organizes your requirements.md, design.md, and tasks.md artifacts for iterative review.
jtsang4Guide structured conversations to define product ideas and create SPEC files.
daddiaImplement code from an approved design.md and backlog.md with tests.
stribusGenerate per-unit requirements.md, design.md, and tasks.md from legacy systems.
robertzengcnAutomate sequential CEO, design, engineering, and DX reviews for project plans.
