From claudient
Drafts an architectural or technical decision record (ADR) from a brief topic description, outputting a structured document with context, decision, options, consequences, and revisit conditions.
How this command is triggered — by the user, by Claude, or both
Slash command
/claudient:decision-doc [decision topic and context]productivity/The summary Claude sees in its command listing — used to decide when to auto-load this command
Draft a decision document for the following: $ARGUMENTS Use this structure: **Status:** Proposed | Accepted | Deprecated | Superseded (Default to "Proposed" unless $ARGUMENTS specifies otherwise.) **Context** What situation forces a decision now. Include constraints, prior art, and why the status quo is insufficient. 3–6 sentences. **Decision** One paragraph. State the decision directly in the first sentence. Do not bury the lede. **Options Considered** For each option (2–4 total, including the chosen one): - **Option N: [Name]** — one sentence description - Pro: ... - Pro: ...
Draft a decision document for the following: $ARGUMENTS
Use this structure:
Status: Proposed | Accepted | Deprecated | Superseded
(Default to "Proposed" unless $ARGUMENTS specifies otherwise.)
Context
What situation forces a decision now. Include constraints, prior art, and why the status quo is insufficient. 3–6 sentences.
Decision
One paragraph. State the decision directly in the first sentence. Do not bury the lede.
Options Considered
For each option (2–4 total, including the chosen one):
Consequences
Positive consequences (what improves or becomes possible).
Negative consequences / trade-offs (what gets harder, what is lost).
Risks (what could go wrong, and mitigation if known).
Revisit Conditions
Bullet list: specific conditions under which this decision should be revisited. Be concrete — not "if requirements change" but "if request volume exceeds 10k/s" or "if vendor X deprecates API Y."
Rules:
Output the document only.
npx claudepluginhub claudient/claudient --plugin claudient-personas