From pi-dev
Use when documenting an architectural or product decision. Creates an Architecture Decision Record (ADR) capturing context, options, and rationale. Writes to docs/06_decisions/.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pi-dev:decision-docsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Interview the user to document one decision using Architecture Decision Record format. Write to `docs/06_decisions/`.
Interview the user to document one decision using Architecture Decision Record format. Write to docs/06_decisions/.
An ADR captures: the context (why a decision was needed), the options considered, the decision made, and why. Written once, referenced forever. Prevents re-litigating the same decision.
One decision per ADR → Context → Options → Decision → Consequences → Write
Run:
find . -maxdepth 3 -type d -name "docs" | grep -v node_modules | grep -v ".git" | sort
./docs)docs/ and create it if missingQ1: "What decision needs to be documented? Phrase it as a question." (free text) Example: "What database should we use?", "Should we use a monolith or microservices?"
Q2: "What is the context? Why does this decision need to be made now?" (free text)
Q3: "What options were considered? List 2-4." (free text) For each option, ask: "What are the pros and cons of [option]?" (free text)
Q4: "What was the decision?" (free text)
Q5: "Why was this option chosen over the others?" (free text)
Q6: "What are the consequences? What becomes easier and what becomes harder because of this decision?" (free text)
Q7: "Is this decision reversible? If yes, what would trigger revisiting it?" (free text)
ADR file name: docs/06_decisions/adr-[number]-[short-slug].md
Number increments from existing ADRs in folder.
# ADR [number]: [Q1 — decision question as title]
**Status:** Accepted
**Date:** [today]
## Context
[Q2]
## Options Considered
### Option 1: [name]
**Pros:** [...]
**Cons:** [...]
### Option 2: [name]
**Pros:** [...]
**Cons:** [...]
[Repeat for each option]
## Decision
**[Q4]**
[Q5 — rationale]
## Consequences
**Easier:** [Q6 — what improves]
**Harder:** [Q6 — what becomes more difficult or constrained]
## Revisit Trigger
[Q7 — condition that would reopen this decision, or "This decision is irreversible"]
docs/06_decisions/ with find docs/06_decisions -name "adr-*.md" | wc -ldocs/06_decisions/adr-[N+1]-[slug].mdIf the user needs to document multiple decisions, run the full interview for each one sequentially. Each gets its own ADR file.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Applies a firm's KYC/AML rules grid to parsed onboarding records: assigns risk rating, checks required documents, outputs rule outcomes with citations, and routes for escalation.
Generates daily or weekly digests of activity from connected sources (chat, email, docs, tasks, CRM), highlighting action items, decisions, mentions, and project updates.
npx claudepluginhub pirras-torres/pirras-marketplace --plugin pi-dev