Menu
ADR management skill. Auto-invoked for generating architecture decisions, documenting design rationale, and maintaining the decision record log. Uses native read/write tools to scaffold and update ADR markdown files.
| name | adr-management |
| description | ADR management skill. Auto-invoked for generating architecture decisions, documenting design rationale, and maintaining the decision record log. Uses native read/write tools to scaffold and update ADR markdown files. |
| allowed-tools | Bash, Read, Write |
You manage Architecture Decision Records — the project's institutional memory for technical choices.
Document, Decide, and Distribute. Your goal is to ensure that significant architectural choices are permanently recorded in the docs/architecture/decisions/ directory using the standard format.
../../scripts/adr_manager.py (create, list, get, search)../../scripts/next_number.pyWhen asked to create an Architecture Decision Record (ADR):
ADRs/ directory at the project root.create subcommand. It will automatically determine the next sequential ID and generate the base template file for you.python3 ./scripts/adr_manager.py create "Use Python 3.12" --context "..." --decision "..." --consequences "...".md file to stdout.Proposed or Accepted.Superseded and add a note linking to the new ADR.python3 ./scripts/adr_manager.py list
python3 ./scripts/adr_manager.py list --limit 10
python3 ./scripts/adr_manager.py get 42
python3 ./scripts/adr_manager.py search "ChromaDB"
Use next_number.py to identify the next sequential ID across various artifact domains.
python3 ./scripts/next_number.py --type adrNNN-short-descriptive-title.md.(Industry standard: Parallel Agent) Primary Use Case: Work that can be partitioned into independent sub-tasks running concurrently across multiple agents. Parallel multi-agent execution pattern. Use when: work can be partitioned into independent tasks that N agents can execute simultaneously across worktrees. Includes routing (sequential vs parallel), merge verification, and correction loops.
Systematically analyze agent plugins and skills to extract design patterns, architectural decisions, and reusable techniques. Trigger with "analyze this plugin", "mine patterns from", "review plugin structure", "extract learnings from", "what patterns does this plugin use", or when examining any plugin or skill collection to understand its design.
Triggers the L5 Red Team Sub-Agent to rigorously audit a plugin against the 39-point L4 pattern matrix.
Audits a local plugin directory to ensure it perfectly matches the Agent Skills and Claude Plugin Open Standards.
Bridge plugin capabilities (commands, skills, agents, hooks, MCP) to specific agent environments (Claude Code, GitHub Copilot, Gemini, Antigravity). Use this skill when converting or installing a plugin to a target runtime.
Claude CLI sub-agent system for persona-based analysis. Use when piping large contexts to Anthropic models for security audits, architecture reviews, QA analysis, or any specialized analysis requiring a fresh model context.