justify-decision
Provide evidence-based justification for architectural and design decisions
npx skills add majiayu000/claude-skill-registry --skill justify-decision --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Skill: justify-decision ## What I do I provide clear, structured rationale for technical choices. I focus on evidence, context, and consequences, ensuring that decisions are documented and defensible rather than based on mere opinion or habit. ## When to use me - When proposing a significant change to the architecture - When choosing between multiple competing libraries or frameworks - During the creation of Architectural Decision Records (ADRs) - When explaining a complex design choice to stakeholders ## Core principles 1. **Evidence over opinion** — Use benchmarks, documentation, or historical data to support claims. 2. **Context is king** — Explain the specific constraints and requirements that led to the decision. 3. **Consequence awareness** — Explicitly state what we are gaining AND what we are giving up (technical debt, complexity, etc.). 4. **Distinguish reversibility** — Identify if a decision is a "one-way door" (hard to undo) or a "two-way door" (easy to pivot). ## Patterns & examples **ADR-Style Justification:** - **Context:** We need to handle 10k concurrent WebSocket connections on a single node. - **Decision:** Use Elixir/Phoenix instead of Node.js. - **Evidence:**
- What I do
- When to use me
- Core principles
- Patterns & examples
- Anti-patterns to avoid
- KB Reference
- Related skills
What does the justify-decision skill do?
Provide evidence-based justification for architectural and design decisions
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill justify-decision --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.