kiro-steering

Bootstrap and synchronize .kiro/steering files with template-based generation and drift detection.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/notta50/korenani --skill kiro-steering-notta50
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-steering
Source: https://github.com/notta50/korenani/tree/main/.claude/skills/kiro-steering
Command: npx skills add https://github.com/notta50/korenani --skill kiro-steering-notta50

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintain a project's steering documentation as persistent project memory by bootstrapping missing core steering files and keeping existing steering aligned with code changes, reducing drift and preserving user customizations.

Core Features & Use Cases

  • Bootstrap from templates and code: Generate product.md, tech.md, and structure.md using repository analysis and steering templates when core files are missing.
  • Continuous sync and drift detection: Analyze the codebase JIT, detect divergences between steering and code, and propose additive updates while preserving user content.
  • Preservation-first updates: Respect custom steering files and user sections, add timestamps and rationale for changes, and avoid documenting sensitive settings.
  • Use Cases: First-time project initialization, periodic maintenance after new features or architectural changes, and onboarding where a canonical source of project patterns is required.

Quick Start

Use the kiro-steering skill to bootstrap or sync the .kiro/steering directory using repository analysis and templates.

Frequently Asked Questions about kiro-steering

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I bootstrap project steering documents for a new codebase?

To bootstrap project steering documents, the skill analyzes your repository and uses templates to generate core files like product.md, tech.md, and structure.md when they are missing.

What is the best way to keep project documentation aligned with code changes?

Keeping project documentation aligned with code changes requires continuous sync and drift detection. The skill analyzes the codebase just-in-time to detect divergences and propose additive updates to steering files.

How does drift detection work for persistent project memory?

Drift detection for persistent project memory works by performing JIT code analysis to compare the current codebase against existing .kiro/steering files, identifying divergences, and proposing additive updates to resolve them.

Will syncing steering files overwrite my custom sections?

Syncing steering files will not overwrite your custom sections. The skill uses preservation-first updates to respect user content, add timestamps and rationale, and avoid documenting sensitive settings.