Skip to main content

decision

The developer wants to capture a discussion that reached decisions. Invoke the decision-record skill.

If the developer included a one-line topic in $ARGUMENTS, use it as the seed for the title and slug — but still confirm the decisions, participants, options, and action items before drafting.

If $ARGUMENTS is empty, derive the record from the recent conversation: identify the discussion that reached decisions, restate the decision(s) and participants back to the developer in two or three sentences, and only proceed after they confirm or correct.

Disambiguate from siblings:

  • Nothing was actually decided yet — it's an idea to triage → invoke /propose (the draft-proposal skill) instead.
  • It's a generic team convention or coding rule → invoke /share-rule (the propose-team-rule skill) instead.

The skill handles the rest — routing ADR (technical) vs decision log (product/business/process), git worktree isolation, drafting from the existing template, index update, branch, push, and PR. When done, it offers to hand the record's action items to /breakdown. Surface the resulting PR URL to the developer.