nikiforovall/adr-plan
plugins/handbook-team-stack/skills/adr-plan/SKILL.md
Analyze a task and produce an Architecture Decision Record with implementation steps.
$ install --global
skillsauthnpx skillsauth add nikiforovall/claude-code-rules adr-planInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 7, 2026, 8:19 PM4.5s1 file scanned
SKILL.md
- name:
- adr-plan
- description:
- Analyze a task and produce an Architecture Decision Record with implementation steps.
- allowed-tools:
- Agent, AskUserQuestion, Bash(npx adr *), Bash(git diff *), Bash(git log *), Bash(git status *), Bash(ls *), Bash(cat *), Read, Grep, Glob
ADR Plan: Task Analysis → Architecture Decision Record
Analyze a task, explore the codebase, and produce an ADR with concrete implementation steps.
Phase 1: Analyze
- Read the task description, active plan, or task list
- Explore affected areas of the codebase — do it concurrently for independent modules
- Map blast radius — search for consumers of functions/types/routes being changed
- Identify alternatives worth considering (at least 2)
Do this silently.
Phase 2: Detect ADR Setup
Check if the project has an ADR directory:
ls docs/adr/ || ls adr/ || ls doc/adr/
- Found → use existing directory, detect next number from existing files
- Not found → run
npx adr init en, then proceed
Phase 3: Produce ADR Content
Write the ADR using npx adr new "<title>", then edit the generated file with the following structure:
# ADR-NNNN: [Title]
## Status
Proposed
## Context
[What problem are we solving? What constraints exist?]
## Decision
[What we chose and why]
## Alternatives Considered
| Option | Pros | Cons |
|--------|------|------|
| ... | ... | ... |
## Implementation Steps
### Step 1: [Description]
- **Files:** [files to create/modify]
- **Depends on:** [previous step or "none"]
- **Done when:** [concrete acceptance criteria]
### Step 2: [Description]
...
## Consequences
- [Positive and negative outcomes, tradeoffs accepted]
Guidelines
- Steps are ordered by dependency — each step lists what it depends on
- Steps are parallelizable when independent — note which steps can run concurrently
- Each step has concrete "done when" criteria — no vague outcomes
- Alternatives table is honest — include the option you chose and why others lost
- Keep it short. 1-2 pages max. No padding.
Phase 4: Present to User
Show the ADR content and the file path. The user may:
- Approve → ADR stays as-is
- Adjust → edit and re-present
- Cancel → delete the file
Important
- The ADR is a planning artifact, not documentation for posterity
- Steps should map naturally to work units (a team member could own one or more steps)
- If the task is too simple for an ADR (single file, obvious fix), say so and skip
- Do not write implementation code — this is planning only
Related Skills
nikiforovall/visual-explainer
development
VerifiedTrustedCommunity
Generate beautiful, self-contained HTML pages that visually explain systems, code changes, plans, and data. Use when the user asks for a diagram, architecture overview, diff review, plan review, project recap, comparison table, or any visual explanation of technical concepts. Also use proactively when you are about to render a complex ASCII table (4+ rows or 3+ columns) — present it as a styled HTML page instead.
123SKILL.mdUpdated May 16, 2026
nikiforovall/glab
tools
VerifiedTrustedCommunity
Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to interact with GitLab resources or perform GitLab workflows.
123SKILL.mdUpdated May 16, 2026
nikiforovall/plugins/handbook-reflect/skills/reflect
tools
VerifiedTrustedCommunity
--- name: reflect description: Analyze a Claude Code session for "wrong-turn" moments (corrections, retries, waste, reversals, dead-ends) and produce an interactive HTML dashboard with copy-able recommendations (CLAUDE.md rules, docs, scripts, hooks, memory entries, sub-skills, etc.) that would help future agents reach the goal faster. Defaults to reflecting on the current in-context session; optionally accepts a session ID or JSONL path. Use when the user invokes /reflect or asks to learn from
119SKILL.mdUpdated Apr 26, 2026
nikiforovall/plugins/handbook-reflect/skills/reflect-tree
tools
VerifiedTrustedCommunity
--- name: reflect-tree description: Visualize a Claude Code session as a quest/skill tree — a navigable SVG graph where nodes are turns and edges show flow, with distinct visual encoding for normal flow, dead-ends, corrections, retries, reversals, and backtracking. Sibling to /reflect (which produces an incidents+recommendations dashboard); this one shows the journey itself. Defaults to the current in-context session; optionally accepts a session ID or JSONL path. Use when the user invokes /refl
119SKILL.mdUpdated Apr 26, 2026