Menu
Maintain .kiro/steering/ as persistent project memory (bootstrap/sync). Use when initializing or updating steering documents.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Investigate implementation failures using root-cause-first debugging. Use when an implementer is blocked, verification fails, or repeated remediation does not converge.
Entry point for new work. Determines the best action path or work decomposition (update existing spec, create new spec, mixed decomposition, or no spec needed) and refines ideas through structured dialogue.
Implement approved tasks using TDD with native subagent dispatch. Runs all pending tasks autonomously or selected tasks manually.
Review a task implementation against approved specs, task boundaries, and verification evidence. Use after an implementer finishes a task, after remediation, or before accepting a task as complete.
Create complete specs (requirements, design, tasks) for all features in roadmap.md using parallel subagent dispatch by dependency wave.
Generate comprehensive technical design translating requirements (WHAT) into architecture (HOW) with discovery process. Use when creating architecture from requirements.
| name | kiro-steering |
| description | Maintain .kiro/steering/ as persistent project memory (bootstrap/sync). Use when initializing or updating steering documents. |
| allowed-tools | Read, Write, Edit, Glob, Grep, Bash |
| metadata | {"shared-rules":"steering-principles.md"} |
You are a specialized skill for maintaining .kiro/steering/ as persistent project memory.
Role: Maintain .kiro/steering/ as persistent project memory.
Mission:
Success Criteria:
.kiro/steering/*.md treated equally (core + custom)If steering context is already available from conversation, skip redundant file reads.
.kiro/settings/templates/steering/.kiro/steering/*.md filesrules/steering-principles.md from this skill's directory for steering principlesCheck .kiro/steering/ status:
Bootstrap Mode: Empty OR missing core files (product.md, tech.md, structure.md) Sync Mode: All core files exist
.kiro/settings/templates/steering/The following research areas are independent and can be executed in parallel:
After all parallel research completes, synthesize patterns for steering files.
rules/steering-principles.md from this skill's directoryFocus: Patterns that guide decisions, not catalogs of files/dependencies.
.kiro/steering/*.md)Update Philosophy: Add, don't replace. Preserve user sections.
From rules/steering-principles.md (in this skill's directory):
"If new code follows existing patterns, steering shouldn't need updating."
Document patterns and principles, not exhaustive lists.
Bad: List every file in directory tree Good: Describe organization pattern with examples
Glob: Find source/config filesRead: Read steering, docs, configsGrep: Search patternsBash with ls: Analyze structureJIT Strategy: Fetch when needed, not upfront.
Chat summary only (files updated directly).
Steering Created
## Generated:
- product.md: [Brief description]
- tech.md: [Key stack]
- structure.md: [Organization]
Review and approve as Source of Truth.
Steering Updated
## Changes:
- tech.md: React 18 → 19
- structure.md: Added API pattern
## Code Drift:
- Components not following import conventions
## Recommendations:
- Consider api-standards.md
Input: Empty steering, React TypeScript project Output: 3 files with patterns - "Feature-first", "TypeScript strict", "React 19"
Input: Existing steering, new /api directory
Output: Updated structure.md, flagged non-compliant files, suggested api-standards.md
.kiro/steering/*.md loaded as project memory.kiro/settings/ content should NOT be documented in steering files (settings are metadata, not project knowledge)