What problem does it solve? Fuzzy requirements, vague tickets, and cross-team migrations often turn into plans that only make sense to their author, leaving implementers to reconstruct context, rediscover unknowns, and improvise rollback paths mid-incident. This Skill structures planning so the plan itself carries the context a cold reader needs. ## Core Features & Use Cases - Done Contract Template: Produces a structured plan with acceptance criteria, non-goals, assumptions, owners, sequencing, rollback, and failure modes. - Planning Checks: Enforces rules like bounding unknowns before estimating, anchoring facts to a single source of truth, and sequencing for reversibility (expand, backfill, dual-write, switch, contract). - Red Flag Detection: Flags one-shot cutovers, unverifiable acceptance criteria, unrehearsed fallbacks, and artifacts with no owner or expiry. - Use Case: When scoping a database migration with cross-team dependencies, use this Skill to produce a plan that names the spike questions, defines reversible steps, and assigns every flag and scaffold an owner and expiry date. ## Quick Start Use the structural-planning skill to turn this migration ticket into an executable plan with acceptance criteria, sequencing, and rollback steps.
