PrizmKit ADR Manager
Manage Architecture Decision Records (ADRs) to document and track architectural decisions with full context, alternatives, and consequences.
Commands
prizmkit.adr.new <title>
Create a new Architecture Decision Record.
STEPS:
- Determine next ADR number from
docs/adr/directory (scan existing files, increment highest number) - Generate ADR from template (
${SKILL_DIR}/assets/adr-template.md):- Title: Provided by user
- Date: Current date
- Status: Proposed
- Context: Ask user what issue is motivating this decision
- Decision: Ask user what change is being proposed
- Consequences: Identify positive and negative consequences
- Alternatives considered: Ask user about alternatives and why they were rejected
- Write to
docs/adr/NNNN-title.md(zero-padded number, kebab-case title) - Also record in
.prizm-docs/DECISIONS section of relevant module doc
prizmkit.adr.list
Show all ADRs with their current status.
STEPS:
- Scan
docs/adr/directory for ADR files - Parse each file for number, title, and status
- Display table:
- Number | Title | Status | Date
- Status values: Proposed, Accepted, Deprecated, Superseded
- Highlight any ADRs in Proposed status that may need review
prizmkit.adr.supersede <number> <new-title>
Mark an existing ADR as superseded and create a replacement.
STEPS:
- Read the existing ADR with the given number from
docs/adr/ - Update its status to "Superseded by [ADR-NNNN]" (the new ADR number)
- Create a new ADR using the
prizmkit.adr.newflow:- Pre-populate context with reference to the superseded ADR
- Include "Supersedes [ADR-NNNN]" in the new ADR
- Write both updated files
Template
The ADR template is located at ${SKILL_DIR}/assets/adr-template.md and follows the standard ADR format with Context, Decision, Consequences, and Alternatives sections.
Path References
All internal asset paths MUST use ${SKILL_DIR} placeholder for cross-IDE compatibility.
Output
- ADR files in
docs/adr/directory - Updated DECISIONS section in relevant
.prizm-docs/module doc
Scan to join WeChat group