kiro-steering

Generate and sync steering documents that capture project patterns as persistent memory.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/scapia-oss/compass --skill kiro-steering-scapia-oss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kiro-steering
Source: https://github.com/scapia-oss/compass/tree/main/tools/cc-sdd/templates/agents/claude-code-skills/skills/kiro-steering
Command: npx skills add https://github.com/scapia-oss/compass --skill kiro-steering-scapia-oss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? AI coding sessions lose project context when chats end, forcing teams to re-explain architecture, conventions, and product intent every session. This Skill maintains a steering directory as durable, version-controlled project memory that any agent or teammate can load. ## Core Features & Use Cases - Bootstrap Mode: Analyzes README, configs, dependencies, and directory structure in parallel to generate core steering files (product.md, tech.md, structure.md) from templates. - Sync Mode: Detects drift between steering documents and the actual codebase, proposing additive updates while preserving user customizations. - Pattern-First Granularity: Documents principles and conventions rather than exhaustive file lists, so steering stays stable as code evolves. - Use Case: After adding a new /api layer to a React TypeScript app, run a steering sync to update structure.md, flag files violating import conventions, and get a recommendation for an api-standards.md document. ## Quick Start Ask the agent to bootstrap steering documents for this repository so its product, tech stack, and structure are captured as persistent project memory.

Frequently Asked Questions about kiro-steering

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

FAQPage Schema
How do I create project memory files for an AI coding assistant?

Run the steering bootstrap flow, which analyzes your README, package configs, and directory structure in parallel, then generates product.md, tech.md, and structure.md from templates. These files capture patterns and conventions rather than exhaustive file listings.

How to keep architecture documentation in sync with code changes?

Use the sync mode, which loads all existing steering files, analyzes the codebase for changes, and detects drift in both directions. It proposes additive updates and reports warnings without overwriting your custom sections.

Will steering sync overwrite my custom documentation?

No. The update philosophy is additive: user customizations are treated as sacred and preserved. When uncertain, the skill reports both states and asks rather than replacing content.

What is the difference between bootstrap and sync mode?

Bootstrap runs when the steering directory is empty or missing core files, generating them from codebase analysis. Sync runs when all core files exist, focusing on drift detection and incremental updates.

When should steering documents not be updated?

When new code follows already-documented patterns, steering should not change. The granularity principle favors documenting conventions over catalogs, so routine additions that match existing patterns require no update.