What problem does it solve? Engineering tasks often stall or go wrong because key behavioral, data-integrity, rollout, or test decisions were never explicitly made. This Skill surfaces the minimum set of high-value decision questions before planning, and persists approved answers as canonical, auditable decisions on disk. ## Core Features & Use Cases - Decision-focused interviewing: Separates genuine decisions (multiple viable alternatives) from facts, and asks only questions that affect correctness, runtime behavior, data integrity, test strategy, or rollout safety. - Canonical decision persistence: Records locked decisions in DECISIONS.md using EARS requirement templates with SHA-256 verification logging, and updates TASK_STATE.md accordingly. - Lock-signal handling: Recognizes explicit user lock signals (e.g. "D2 [LOCK]", "approved") to persist decisions in the same turn, and stalls safely in unattended runs. - Use Case: Before planning a payment retry feature, run the interview to confirm how refunds, retries, and chargebacks behave across flows, then lock the answers as EARS-shaped decisions that planning and implementation must follow. ## Quick Start Run the decision-interview skill on my active task to identify and lock the open behavioral decisions before implementation planning.
