ao-cyber-systems/decide

<objective> Resolve a parked decision (or list pending decisions if no arguments given) and tell the user how to resume gated execution.

Decisions live in .planning/decisions/pending/ — they are created by decision-queue add when autonomous execution hits a checkpoint:decision it cannot auto-select. Resolving a decision moves it to .planning/decisions/resolved/ and unblocks the TRDs listed in its blocks field. </objective>

<process> **Step 1 — No arguments: list pending decisions**

If $ARGUMENTS is empty, run:

node ~/.claude/devflow/bin/df-tools.cjs decision-queue list --raw

Parse the JSON array. If empty, report "No pending decisions." and stop.

Otherwise format each decision for the user:

DECISION-NNN: <title>
  Recommendation: <recommendation>
  Options: <option names joined by " | ">
  Blocks: <blocks array or "none">
  Context: <context field>

To resolve: /devflow:decide DECISION-NNN <option>

Ask the user which decision they want to resolve and which option to pick.

Step 2 — With arguments: resolve and report

Parse $ARGUMENTS as <decision-id> <choice> (first word is id, remainder is choice).

Run:

node ~/.claude/devflow/bin/df-tools.cjs decision-queue resolve <decision-id> <choice>

If exit 0:

• Read the resolved decision file from .planning/decisions/resolved/<decision-id>.md
• Extract the blocks list from its frontmatter
• Report the resolution and list the newly-unblocked TRDs
• Suggest the next step:

Decision <id> resolved with: <choice>

Unblocked TRDs:
  - <trd-id>
  - ...

To resume execution:
  /devflow:execute-objective <objective>

If blocks is empty, report: "Decision resolved. No TRDs were blocked by this decision — execution was already able to continue independently."

If exit non-zero, show the error from stderr and suggest running /devflow:decide without arguments to list current pending decisions.

Step 3 — Context note

Decisions in .planning/decisions/resolved/ are the permanent archive. They are NOT gitignored — parked decisions are durable planning state, not runtime markers. </process>

<context> Decision files conform to the Pattern 3 format (TRD 10-03):

---
id: DECISION-001
objective: 10
wave: 2
trd: 10-03
type: checkpoint:decision
created: 2026-06-12T14:30:00Z
status: pending
blocks: [10-04, 10-05]
independent: [10-06]
recommendation: option-a
---

## Decision: [What's being decided]

**Context:** [Why this matters]

**Options:**

1. **option-a** — [Name]
   - Pros: [benefits]
   - Cons: [tradeoffs]

## To Resolve

Reply: `/devflow:decide DECISION-001 option-a`

The blocks array lists TRD ids gated on this decision (direct + transitive). independent lists TRDs that can proceed regardless. recommendation is the planner's suggested pick.

Subcommands available via df-tools decision-queue:

• add — park a new decision
• list [--raw] [--status resolved] — list decisions
• resolve <id> <choice> — resolve and move to resolved/
• notify <id> — re-fire OS notification for a pending decision </context>