Reusable steering files for Kiro CLI — spec-driven development workflow prompts reverse-engineered from Kiro IDE.
| File | Purpose |
|---|---|
global/spec-workflow.md |
Full spec workflow reference: 3-phase process (requirements → design → tasks), templates, task format, bugfix methodology, session handling |
global/spec-creation-guide.md |
Step-by-step guide for creating specs from scratch with templates and quality rules |
cp global/*.md ~/.kiro/steering/These steering files teach the Kiro CLI agent how to do structured spec-driven development — the same workflow that Kiro IDE uses with its built-in spec feature:
- Requirements — User stories + acceptance criteria using EARS syntax
- Design — Architecture, correctness properties, error handling, testing strategy
- Tasks — Ordered implementation plan with checkboxes and requirement traceability
Supports feature specs (requirements-first or design-first) and bugfix specs (bug condition methodology).
Once installed, ask the CLI agent to create a spec:
> create a spec for user authentication
> spec out a caching layer
> plan the API redesign
The agent will follow the workflow, creating requirements.md → design.md → tasks.md under .kiro/specs/{feature-name}/.
Both files use inclusion: manual front-matter — they're loaded into the knowledge base but don't bloat every conversation. The agent finds them via semantic search when spec-related requests come in.
Tested with Kiro CLI. The steering files follow the standard .kiro/steering/ convention and should work with any version that supports steering file loading.
Issues and PRs are welcome! If you have improvements to the workflow templates or want to add new steering files, feel free to open a PR.