decide

Provide the problem or question plus any evidence artifacts, and the Skill frames the decision, compares two or three distinct options, challenges its own recommendation, and waits for your approval before writing anything. The approved choice is recorded as a decision file with rollback and falsification signals.

A decision record should include the chosen approach, supporting evidence, accepted tradeoffs, edge cases, a falsification signal, and a rollback path. This Skill writes it as a lowercase decisions/<slug>.md file with status accepted and causal fields like supersedes, affects, and invalidates.

Use discovery when a material option, constraint, or acceptance criterion is still unknown, since forcing a recommendation from sparse evidence produces unreliable decisions. The Skill detects this gap during its readiness check and routes to essential:discover, stopping the decision pass until results return.

No, it never creates, executes, or modifies files before explicit user approval. It presents a recommendation report and stops, only writing the decision record and handing off to an implementing skill after you approve.

The old accepted decision is never edited; the new decision supersedes it and names the replaced record by id and exact revision. The handoff includes a blast-radius sweep over the affects and invalidates fields so dependent work is flagged as stale.