Kiro Skill

This walks you through the full cycle of building a feature: writing requirements in EARS format, creating a design doc with architecture and data models, then generating a test-driven task list. Everything lives in a `.kiro/specs/` directory structure. What I like here is the forced approval gates between phases so you don't end up with a design that doesn't match your requirements or tasks that drift from the design. The tone guidelines are refreshingly opinionated about minimal code and cutting fluff, which mirrors how the workflow itself operates. Best for greenfield features where you want structured planning before touching code, less useful if you're already deep in implementation mode.