steering

Architecture steering generates and maintains persistent steering documents describing your codebase's patterns, technology stack, and business context. It analyzes directory structure, package files, and framework signatures to create structure.md, tech.md, and product.md artifacts stored in a memories/ directory for cross-session collaboration and unified agent understanding.

Yes, steering applies to both monorepo and multi-repository projects. It analyzes directory hierarchies, package dependencies, and framework signatures across repositories to detect architecture patterns and extract the complete technology stack regardless of repository structure.

Run steering from your repository root to analyze the codebase and auto-generate steering documents. It extracts architecture patterns, technology stack, and business context from your code structure and documentation, then stores ADR-style decisions and workflows in memories/ for immediate team onboarding and alignment.

Steering detects architecture patterns, documents directory structures, identifies frameworks and technologies in use, captures business context, and generates steering artifacts. It produces structure.md for architecture layout, tech.md for technology decisions, and product.md for business goals in both English and Japanese.

Steering stores ADR-style architectural decisions and workflows in a persistent memories/ directory. Agents access this shared memory across sessions to make consistent decisions aligned with documented patterns, reducing conflicts and maintaining cohesive collaboration.

No. Steering analyzes your codebase directly—directory structure, package files, framework signatures—to generate steering documents. Existing documentation accelerates context extraction, but steering produces artifacts from code structure alone.