Results for “architecture-decision-record”
18 skills
majiayu000 adr
Manages Architecture Decision Records (ADRs) throughout their lifecycle, including reading, writing, and aligning development with documented decisions.
567 · bundle
alirezarezvani senior-architect
Design system architecture, evaluate microservices vs monolith, create architecture diagrams, analyze dependencies, choose databases, and make technical decisions with architecture decision records.
20.4k · bundle
tinh2 adr
Creates and manages Architecture Decision Records using the Michael Nygard format, including new ADR creation, retrospective analysis, superseding, deprecating, and index generation.
13
projectious-work decision-record
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.
0 · bundle
More results
richardnguyen0715 develop-adr
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.
0
concertonotes decide
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.
0 · bundle
dvy1987 memory-decision
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.
3 · bundle
lucassantana-dev adr-write
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.
1 · bundle
paramchordiya software-architecture
Enforces system design, project structure, dependency management, error handling, testing, and documentation standards at principal-engineer level.
0
theheavenlyd3mon adr-authoring
Write, review, and maintain architecture decision records with clear context, alternatives, consequences, and lifecycle governance. Use when a consequential technical decision must remain understandable.
28 · bundle
intense-visions adr-fleet
ADR Fleet
18 · bundle
fukukei23 record-decision
【非推奨 → ssot-record を使うこと】 ssot-record に統合済み。/record-decision が呼ばれた場合は ssot-record スキルに処理を委譲する。
0
lucassantana-dev memory
Persist decisions, preferences, and project state across sessions using structured memory types
1 · bundle
delorenj bmad-architecture
Produce the architecture: a lean spine of invariants that keeps everything built from it consistent, projected into whatever format the work needs. Use when the user says "create the architecture", "create technical architecture", "architecture spine", or "create a solution design".
1 · bundle
a5c-ai planning-design
Design technical architecture, select technology stack, and define implementation strategy from specifications and constitution constraints.
1.7k · bundle
jantoniofc decide
Decide
6
a5c-ai epic-generation
Epic Generation
1.7k · bundle
github salesforce-flow-design
Guides architecture decisions, flow type selection, bulk safety validation, and fault handling standards for Salesforce Flow design and review.
36.2k