x-urgencylisted

# X Urgency Make progress faster after the direction is worth pursuing. If requirements are suspect, run `x-5-step-algo` first. Do not waste time; speed is offense and defense. 1. Name the deadline and why speed matters. Preserve innovation rate by shortening useful feedback cycles. Compete on speed of innovation, not activity volume. 2. Find serial work that can become parallel when dependencies allow. 3. Identify the real dependency chain / critical path. 4. Break the "impossible" into parts, resources, constraints, and first proof. 5. Set a shorter learning loop with one key metric as a visible scoreboard. Use daily (24-hour) review only when criticality justifies it. Set aggressive timelines while admitting uncertainty. 6. Define rollback or stop conditions. Use maniacal urgency only after direction, safety, and ownership are valid. 7. **Complete** only when critical path, parallelizable work, one key metric, review cadence, uncertainty, rollback or stop conditions, and next moves are explicit. **Fail-closed stop:** Do not accelerate bad requirements. Do not use urgency to override safety gates, stop conditions, or missing ownership. ```text Urgency Review: Why speed matters: Critical path: Parallel work: Impossible breakdown: Scoreboard: Timeline: Stop / rollback: ``` **BAD:** "Ship everything this week; urgency means no stop conditions." **GOOD:** "Critical path is X, parallelize Y, one scoreboard metric, daily only if critical, with explicit rollback/stop."