Results for “architecture-decision-records”

Creates an Architecture Decision Record following the Nygard format to document significant technical decisions, their context, and consequences. Use when making technical choices that affect system architecture, technology selection, or development patterns.

Record decisions with rationale, alternatives, and consequences — the ADR pattern as a primitive. Use when a consequential choice is made — architecture, tooling, process, scope, trade-off. Capture WHY, not just WHAT.

Record a decision: finalized → ADR (optionally rule + guide or spec + plan); open proposal → RFC. Use for 'we decided', 'record this decision', 'make it a standard', 'draft an RFC', 'should we switch to Y'. Not for feature planning or documenting existing code.

Design system architecture, evaluate microservices vs monolith, create architecture diagrams, analyze dependencies, choose databases, and make technical decisions with architecture decision records.

Enforces system design, project structure, dependency management, error handling, testing, and documentation standards at principal-engineer level.

Write, review, and maintain architecture decision records with clear context, alternatives, consequences, and lifecycle governance. Use when a consequential technical decision must remain understandable.

Record durable project decisions with rationale, alternatives, assumptions, status, and revisit triggers. Load when the user says record this decision, we decided, decision log, why did we choose, revisit this later, or capture architectural/process rationale.

Capture an Architecture Decision Record — what was decided, why, what alternatives were considered, and when to revisit. Writes a numbered ADR file to docs/adr/ in the active repo, with consistent formatting that downstream skills (improve-codebase-architecture, refactor-plan) can read. Use right after deciding something non-obvious so the reasoning isn't lost.

ADR Fleet

Convierte especificaciones aprobadas en un plan técnico detallado, documentando decisiones de arquitectura, flujo de datos y cambios de archivos.

Design technical architecture, select technology stack, and define implementation strategy from specifications and constitution constraints.

Persist decisions, preferences, and project state across sessions using structured memory types

【非推奨 → ssot-record を使うこと】 ssot-record に統合済み。/record-decision が呼ばれた場合は ssot-record スキルに処理を委譲する。

Decide

Stores verified cross-session facts, decisions, preferences, and open questions without secrets, speculation, or monitoring.

Persistent cross-session memory management. Enables agents to remember user preferences, project conventions, and past decisions across different sessions using a structured MEMORY.md index and topic files.

Epic Generation