decision-documentation
Create Architecture Decision Records (ADRs) documenting significant technical choices with context, options, consequences, and sequential numbering.
npx skills add a5c-ai/babysitter --skill decision-documentation --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.
- Choosing between competing approaches - Documenting a decision for future reference - Recording rationale that would otherwise be lost ## ADR Format - **Title**: Clear description of the decision - **Status**: Proposed, Accepted, Deprecated, Superseded - **Context**: Why this decision is needed - **Options**: Alternatives considered with pros/cons - **Decision**: The chosen option with rationale - **Consequences**: Expected positive and negative outcomes ## Output ADRs are written to `docs/decisions/` with sequential numbering (e.g., `0001-use-typescript.md`). ## Tool Use Invoke via babysitter process: `methodologies/rpikit/rpikit-decision`
- ADR Format
- Output
- Tool Use
What does the decision-documentation skill do?
Create Architecture Decision Records (ADRs) documenting significant technical choices with context, options, consequences, and sequential numbering.
How do I install it?
Run `npx skills add a5c-ai/babysitter --skill decision-documentation --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 a5c-ai/babysitter, a repository with 1,642 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.
