decision

Decision

Use this skill whenever continuation is non-trivial. Use it to make one route judgment from durable evidence and then get the quest moving again.

Match signals

Use decision when:

• the next stage is not obvious
• the evidence is mixed
• the current line may need to stop
• the quest needs a branch, reset, or reuse-baseline judgment
• a user preference-sensitive choice remains
• a blocker needs an explicit route

Do not use decision when:

• the active mainline is still too ambiguous for a real route judgment and should first be reconciled through intake-audit
• the next move is already obvious from durable evidence and can proceed directly
• the task is really baseline recovery, scouting, ideation, or execution rather than a route judgment

One-sentence summary

Make one route judgment from durable evidence, record the verdict and smallest valid action, then keep the quest moving.

Control workflow

1. Check whether the board is decision-ready. If the current mainline, latest decisive result, or stale-route state is unclear, route through intake-audit first.
2. State the real question and gather only decision-relevant evidence. Compress the strongest support, strongest contradiction, main risk, main cost, and what is genuinely new.
3. Choose the smallest canonical action that resolves the current state. Make the winner, main rejected alternatives, and the decisive reason explicit.
4. Record the decision durably. Include verdict, action, reason, evidence paths, and next stage or next direction.
5. Ask the user only when local evidence cannot safely resolve a real preference, scope, or cost choice.

AVOID / pitfalls

• Do not repeat the same decision without new evidence.
• Do not decide from vibe, momentum, or optimism.
• Do not hide a blocked state behind a vague “continue”.
• Do not launch analysis campaigns casually when the expected information gain is weak.
• Do not choose among candidate packages without naming why the alternatives lost.
• Do not imply baseline reuse is resolved unless the concrete attachment and confirmation path is clear.
• Do not choose finalize for a paper line unless manuscript coverage reports submission_ready=true; a draft checkpoint routes back to write, and a review package routes to review.
• Do not keep a paper route alive after a publishability stop-loss finding. If durable evidence shows that novelty, evidence sufficiency, or reader value has collapsed beyond reasonable narrowing, recommend stop or branch, and record any narrowed non-paper objective as the next direction rather than as a new action. Do not execute stop for a low-quality paper judgment without asking the user to confirm that route.