Captures architectural decisions and proposals from the current session into a decisions.md markdown file, organizing by topic with status, context, options considered, rationale, and trade-offs.
From releasenpx claudepluginhub scarrillo/release --plugin release/decisionsBrowse architectural decisions detected in past conversations — what was chosen, why, and when
/decisionsDecision tracking is built into EriRPG to prevent "why did we choose X?" amnesia.
Capture decisions and proposals from the current session for future reference. Includes both implemented decisions and proposals still under consideration.
Model: Uses the model configured in release-plugin.model (see /release:changelog for model selection).
/decisions directly at any point to capture decisions from the current sessionReview current session for:
Capture regardless of implementation status:
Organize by topic for easy future reference
If decisions.md doesn't exist, ask the user: "Where should I create the decisions document?"
./decisions.md)./docs/decisions.md)If decisions.md already exists, use its current location.
If file exists: Prepend new entries after the # Decisions & Proposals header (newest entries at top). Read existing content first to avoid duplicates.
Structure:
# Decisions & Proposals
## [Topic/Feature Area] - YYYY-MM-DD
### Status: [Implemented | Proposed | Rejected | Deferred]
### Context
[What problem or question prompted this decision/proposal?]
### Proposal
[What was proposed or decided?]
### Options Considered
1. **[Option A]**: [Brief description]
- Pros: [advantages]
- Cons: [disadvantages]
2. **[Option B]**: [Brief description]
- Pros: [advantages]
- Cons: [disadvantages]
### Decision
[What was decided, or "Pending review" if still a proposal]
### Rationale
[Why this approach was chosen/proposed]
### Trade-offs Accepted
[What compromises come with this decision]
### References
- [Links to docs, samples, related PRs]
---
If a specific topic is provided, scope to that area: $ARGUMENTS