Create and maintain project reference documents from the codebase, covering product purpose, technology choices, and organization patterns. Detect differences between documentation and code while preserving user additions during updates.
Maintain {{KIRO_DIR}}/steering/ as persistent project memory (bootstrap/sync). Use when initializing or updating steering documents.
Review the instructions the agent will receive before you install.
You are a specialized skill for maintaining {{KIRO_DIR}}/steering/ as persistent project memory.
Role: Maintain {{KIRO_DIR}}/steering/ as persistent project memory.
Mission:
Success Criteria:
{{KIRO_DIR}}/steering/*.md treated equally (core + custom)If steering context is already available from conversation, skip redundant file reads.
{{KIRO_DIR}}/settings/templates/steering/{{KIRO_DIR}}/steering/*.md filesrules/steering-principles.md from this skill's directory for steering principlesCheck {{KIRO_DIR}}/steering/ status:
Bootstrap Mode: Empty OR missing core files (product.md, tech.md, structure.md) Sync Mode: All core files exist
{{KIRO_DIR}}/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_DIR}}/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_DIR}}/steering/*.md loaded as project memory{{KIRO_DIR}}/settings/ content should NOT be documented in steering files (settings are metadata, not project knowledge)No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Add coding-agent support to cc-sdd through a documented workflow. Research the agent’s official formats, prepare an integration plan, implement registry entries and templates, and verify generated files, including Japanese and English output.
Investigate blocked implementation work and recurring failures using error output, code changes, configuration, and dependency evidence. Get a root cause report with a focused repair plan, verification steps, and a recommendation to retry, block, or seek human input.
Clarify a development request through structured questions and choose a practical next step: update an existing specification, create new ones, or implement directly. For new specifications, record scope, approach, and dependencies in planning files.
Implement approved development tasks one at a time using test-driven development, which starts with a failing test. Process all pending tasks or selected ones, check changes against requirements and design, and update progress after review and completion verification.
Implement approved tasks using test-driven development, writing tests before code. Run all pending tasks one at a time or select specific tasks, with configurable review and verification before updating completion status.
Implement approved tasks through test-driven development, writing tests before code. Run all pending tasks sequentially with subagents or select tasks for direct execution, then track completion using reviews and verification evidence.