decision-record
FeaturedWrite a narrative decision record (ADR) for a design system choice: context, options, trade-offs, consequences, including declined proposals. Triggers: document this decision, ADR, why did we choose, capture the reasoning. Machine-checkable rules: governance-encoder.
Install
Quality Score: 90/100
Skill Content
Details
- Author
- murphytrueman
- Repository
- murphytrueman/design-system-ops
- Created
- 6 months ago
- Last Updated
- 2 days ago
- Language
- Python
- License
- MIT
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
design-record
Record a design decision as an ADR, or update the living architecture document, in a repo that keeps a record of how it is built and why. Drafts the ADR body from the conversation, allocates the next number, maintains the ADR index, and edits named sections of architecture.md. Stages file edits only; never produces its own commit. Trigger with: 'record an ADR', 'document this decision', 'we decided X — write it up', 'why did we choose Y — capture it', 'update the architecture doc'.
decision-record
Write or update a decision record (ADR) in docs/decision-records/ for this repo — eagerworks/skills. Use when a change makes a real judgment call with a defensible alternative that the code alone won't explain (a skill's output contract, where it writes, a naming/config convention, a workflow it deliberately deviates from a precedent on), when the user asks to "record this decision" or "write an ADR", or when landing a non-obvious choice in this collection. Repo-internal tooling — not shipped to skills.sh users.
principle-record-decisions
Apply when settling a non-obvious technical decision: a stack choice, a swap, an integration approach, an experiment outcome, a design-space pick. Write an ADR with the options considered and why the pick won, so a rejected option stays recoverable. Offer it proactively.