Loading...
Loading...
Found 6 Skills
Use when a decision needs recording - an ADR, a decision log entry, or when someone asks to write down why something was chosen, rejected, or superseded. Encodes the ADR and decision-log formats. Use whenever a choice was made that would otherwise live only in chat, even if nobody says "ADR".
Grill the user relentlessly about a plan, decision, or idea via structured multiple-choice questions, recording decisions and rejection reasons as a side effect of choosing. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
Creates Architecture Decision Records (ADRs) to document significant architectural choices and their rationale for future team members. Use when the user says "write an ADR", "document this decision", "record why we chose X", "add an architecture decision record", "create an ADR for", or wants to capture the reasoning behind a technical choice so the team understands it later. Do NOT use when the decision hasn't been made yet (use create-rfc instead), for implementation planning (use technical-design-doc-creator), or for general documentation.
Write a new ADR whose body is the user's exact words, nothing added. Use when the user says "adr-verbatim", "document that as an ADR", "new ADR", "record this decision", or gives wording for an ADR. Differentiator: agent adds only title, number and status line; it never drafts, rewrites, or expands the body.
Stress-test a plan through questions while recording the resulting domain terms and decisions.
Create a new Architecture Decision Record with sequential numbering and AgentDB registration