This one walks you through turning fuzzy feature requests into concrete, testable requirements using the EARS format (Easy Approach to Requirements Syntax). You get patterns like "WHEN user uploads file over 10MB THEN system SHALL display error" instead of vague stuff like "uploads should work well." It covers the full loop: capture user stories, write acceptance criteria, identify edge cases, validate completeness. The examples are solid, real-world scenarios like file uploads and search features. Use it at the start of any project when stakeholders are hand-waving about what they want. It won't make requirements gathering fun, but it'll keep you from building the wrong thing.
npx -y skills add jasonkneen/kiro --skill requirements-engineering --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
juliusbrussee/caveman
mattpocock/skills
shadcn/improve
obra/superpowers
forrestchang/andrej-karpathy-skills
vercel-labs/skills