skills/adr/SKILL.md
Tracks Architecture Decision Records (ADRs) in docs/adrs/. Creates, lists, and updates ADRs following project conventions. TRIGGER when: user wants to record, review, or update an architectural decision.
npx skillsauth add apocohq/skills adrInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Manage Architecture Decision Records in docs/adrs/. Interpret $ARGUMENTS as natural language.
Ask the user for any missing information. You need at minimum: title, context, decision, and owner (@github-username).
If the decision is made → create docs/adrs/NNN-short-title.md with status Accepted.
If the decision is open → create docs/adrs/DRAFT-short-title.md with status Proposed.
Assign the next number by reading docs/adrs/index.md. Always update the index after creating a file.
Valid status transitions: Accepted, Deprecated, Superseded by ADR-NNN.
When promoting a Draft to Accepted: rename DRAFT-title.md → NNN-title.md and move the row from Drafts to Accepted in the index.
NNN-short-title.md — numbered, zero-padded to 3 digits, never reusedDRAFT-short-title.md — no number until accepteddocs/adrs/index.md — always keep in sync# ADR-NNN: Title
**Date:** YYYY-MM-DD
**Status:** Proposed | Accepted | Deprecated | Superseded by ADR-NNN
**Owner:** @github-username
## Context
What is the issue motivating this decision?
## Decision
What we decided.
## Alternatives Considered
What else was evaluated and why rejected.
## Consequences
What becomes easier or more difficult.
development
Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue after user approval. Use when user wants to write a PRD, create a product requirements document, or plan a new feature. Always present the PRD for user approval before submitting.
development
Morning review and prioritization of Things todos. Use this skill every morning, or whenever the user asks to review, triage, categorize, or prioritize their Things tasks. Also trigger when the user says things like 'what should I work on today', 'organize my todos', 'morning routine', or 'daily review'.
testing
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
tools
Pick and implement the next user story from a PRD GitHub issue. Analyzes merged PRs for prior work and findings, proposes a plan, implements it, and creates a PR linking back to the PRD. Use when user says "ralph it", "ralph-it", or wants to work through PRD user stories.