Create and manage Architecture Decision Records with Mermaid diagrams.
npx skills add https://github.com/managedcode/MCPGateway --skill mcaf-adr-writing
Please help me install this Agent Skill. Skill: mcaf-adr-writing Source: https://github.com/managedcode/MCPGateway/tree/main/.codex/skills/mcaf-adr-writing Command: npx skills add https://github.com/managedcode/MCPGateway --skill mcaf-adr-writing
This Skill provides a structured and auditable way to document significant architectural decisions, ensuring clarity, consistency, and maintainability within a project.
Use the mcaf-adr-writing skill to write an ADR for a new data model change.
High-intent search queries and answers about installing and using this skill.
An Architecture Decision Record (ADR) documents significant architectural changes, design decisions, and policy shifts. You should write an ADR whenever a team makes a structural change, such as switching from a monolithic architecture to microservices, to preserve project knowledge.
You document architectural decisions by creating an ADR that captures the context, alternatives considered, trade-offs, and consequences. This Skill scaffolds the record and uses Mermaid diagrams to visually map the decision rationale and verification steps.
To create an ADR for a data model change, you scaffold a new record and fill in the structured sections for context, alternatives, and consequences. This ensures the design decision and its impact are formally documented within your repository standards.
Yes, ADR creation integrates directly with repository documentation standards. This ensures that architectural decisions, policy shifts, and technical debt considerations are preserved and accessible alongside your existing project documentation.
The best way to capture rationale for a microservices migration is using a structured ADR. It records the context, evaluates alternatives, and documents the consequences of moving away from a monolithic architecture, ensuring an auditable trail.
To manage technical debt from policy shifts, an ADR should include the context driving the change, alternatives considered, the final decision, and the resulting consequences. Adding verification steps ensures the policy shift is properly validated.
telum-aiCreate a Speck project structure with a skeleton project.md file.
patricio0312revGenerate Mermaid diagrams for flows, sequences, ERDs, and architecture in Markdown.
jeremyaryCreate structured Markdown Architecture Decision Records in the plans/adr/ directory.
iyakiDocument architectural decisions with ADR templates capturing context, decision, and consequences.
