kiro-steering

Generate project steering by bootstrapping .kiro/steering Markdown files from templates using just-in-time codebase analysis across product, tech, and structure domains. It creates product.md, tech.md, and structure.md to establish pattern-focused project memory when steering is missing or incomplete.

Detect code drift by synchronizing existing .kiro/steering files against the current codebase. The sync compares documented patterns with actual implementation to surface inconsistencies, propose additive updates, and flag areas where architecture or APIs have changed.

Sync steering files while preserving custom content by applying additive updates only. The process detects drift between existing steering and codebase state, then proposes targeted additions without overwriting user-defined sections or custom guidance.

Update project memory after introducing major API or architecture changes by running a steering sync. This analyzes the codebase, flags inconsistencies between documented patterns and current code, and proposes additive updates to keep guidance aligned.

kiro-steering works with software repositories using spec-driven development where agents must bootstrap or sync .kiro/steering project memory. It requires no external dependencies and performs codebase analysis across product, technology, and structure domains.

Steering files should document organizational, technology, and structure patterns rather than exhaustive file lists. The skill extracts pattern-focused guidance from codebase analysis, following explicit steering principles to maintain concise, actionable project memory.