Create numbered architectural decision documents under a decisions directory.
npx skills add https://github.com/remix-run/remix --skill make-decision-doc
Please help me install this Agent Skill. Skill: make-decision-doc Source: https://github.com/remix-run/remix/tree/main/.agents/skills/make-decision-doc Command: npx skills add https://github.com/remix-run/remix --skill make-decision-doc
Engineering teams make non-obvious architectural choices whose rationale gets lost over time, leaving future contributors guessing why one approach was chosen over alternatives. This Skill captures that reasoning in a consistent, numbered decision document format.
decisions/NNN-kebab-slug.md files with zero-padded sequential numbering derived from existing files.decisions/004-single-matcher.md with the tradeoffs, alternatives considered, and revisit conditions.Write a decision doc explaining why we chose a single matcher over supporting multiple matchers.
High-intent search queries and answers about installing and using this skill.
Create a markdown file under a decisions directory with a sequential number and kebab-case slug, such as decisions/004-single-matcher.md. Include the choice made, the alternatives actually considered, the tradeoffs, and conditions that would revisit the decision.
Write a decision doc when a non-obvious architectural choice has tradeoffs future contributors would second-guess, or when you diverged from an industry default. Skip it when the choice is obvious or the rationale already lives in code comments or PR descriptions.
Use NNN-kebab-slug.md with a three-digit zero-padded prefix, where the number is the count of existing decision files plus one. The slug should name the thing being decided, not the verb, such as single-matcher rather than pick-single-matcher.
Ground every claim in cited evidence such as benchmarks, blog posts, or code references, and list only alternatives that were genuinely deliberated. Include a when-to-revisit section with numbered conditions that would flip the decision.
Skip it when the choice is obvious, the alternatives were never seriously considered, or the reasoning already exists in code comments, change files, or PR descriptions. Inventing weak alternatives to knock down undermines the document.
Clyra-AITriage pull request comments into Implement, Defer, or Reject decisions with risk scores.
ChegginGenerate API references, user guides, and changelogs from code and git history.
DecentralizedGeoEnforce evidence-based verification before claiming task completion.
abhinavEnforce comment formatting rules for Go and general programming projects.