add-adr
Create a new Architecture Decision Record in .context/decisions/. Use when documenting an architectural decision.
Best use case
add-adr is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Create a new Architecture Decision Record in .context/decisions/. Use when documenting an architectural decision.
Teams using add-adr should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/add-adr/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How add-adr Compares
| Feature / Agent | add-adr | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Create a new Architecture Decision Record in .context/decisions/. Use when documenting an architectural decision.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
Create a new ADR in `.context/decisions/`. ## Steps 1. Read `.context/decisions/README.md` for the template and existing ADR numbering 2. Determine the next ADR number (check existing files in `.context/decisions/`) 3. Create `.context/decisions/[NNN]-[kebab-case-title].md` using the template from README.md 4. Fill in: Title, Status (Proposed), Context, Decision, Consequences, Alternatives Considered 5. Update `.context/decisions/README.md` index with the new ADR ## Content from user The user's input describing the decision: $ARGUMENTS ## Rules - Status should be "Proposed" for new ADRs - Always document alternatives considered and why they were rejected - Include concrete consequences (both positive and negative) - Link to related ADRs if they exist - Keep the context section focused on the problem, not the solution
Related Skills
validate-context
Validate .context/ files for quality, staleness, and conformance to the Substrate methodology. Run after making changes to documentation.
new-domain
Create a new .context domain folder with overview and patterns files following the Substrate methodology. Use when adding a new documentation domain to the project.
generate-tool-config
Generate tool-specific configuration files (Cursor rules, Copilot instructions, Windsurf rules) from the .context/ documentation. Use when setting up a project for a specific AI coding tool.
workspace-surface-audit
Audit the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommend the highest-value ECC-native skills, hooks, agents, and operator workflows. Use when the user wants help setting up Claude Code or understanding what capabilities are actually available in their environment.
ui-demo
Record polished UI demo videos using Playwright. Use when the user asks to create a demo, walkthrough, screen recording, or tutorial video of a web application. Produces WebM videos with visible cursor, natural pacing, and professional feel.
token-budget-advisor
Offers the user an informed choice about how much response depth to consume before answering. Use this skill when the user explicitly wants to control response length, depth, or token budget. TRIGGER when: "token budget", "token count", "token usage", "token limit", "response length", "answer depth", "short version", "brief answer", "detailed answer", "exhaustive answer", "respuesta corta vs larga", "cuántos tokens", "ahorrar tokens", "responde al 50%", "dame la versión corta", "quiero controlar cuánto usas", or clear variants where the user is explicitly asking to control answer size or depth. DO NOT TRIGGER when: user has already specified a level in the current session (maintain it), the request is clearly a one-word answer, or "token" refers to auth/session/payment tokens rather than response size.
skill-comply
Visualize whether skills, rules, and agent definitions are actually followed — auto-generates scenarios at 3 prompt strictness levels, runs agents, classifies behavioral sequences, and reports compliance rates with full tool call timelines
santa-method
Multi-agent adversarial verification with convergence loop. Two independent review agents must both pass before output ships.
safety-guard
Use this skill to prevent destructive operations when working on production systems or running agents autonomously.
repo-scan
Cross-stack source code asset audit — classifies every file, detects embedded third-party libraries, and delivers actionable four-level verdicts per module with interactive HTML reports.
project-flow-ops
Operate execution flow across GitHub and Linear by triaging issues and pull requests, linking active work, and keeping GitHub public-facing while Linear remains the internal execution layer. Use when the user wants backlog control, PR triage, or GitHub-to-Linear coordination.
product-lens
Use this skill to validate the "why" before building, run product diagnostics, and pressure-test product direction before the request becomes an implementation contract.