planlisted

# Implementation Planning ## Overview Transform specifications into executable plans. Planning bridges the gap between WHAT (spec) and HOW (code). **Core principle:** A plan without dependencies is a wishlist. **Violating the letter of the rules is violating the spirit of the rules.** ## AI-DLC Phase: CONSTRUCTION This skill is part of the **Construction Phase** in AI-DLC (AI-Driven Development Lifecycle). **Construction Goal:** Using validated context from Inception, propose architecture and implementation through collaborative mob construction. **Construction Flow:** ``` Spec + Context → Mob Construction → Architecture → Implementation Plan → Code ``` **Previous Phase:** Inception (requirements elaboration) **Next Phase:** Operations (deployment and monitoring) ## When to Use **Always:** - Spec is complete and approved - Before writing implementation code - When estimating work - When multiple components interact **Never start implementation:** - Without understanding dependencies - Without knowing the sequence - Without identifying risks ## The Iron Law ``` NO CODE WITHOUT A PLAN ``` Start coding from a spec alone? Stop. Plan first. **No exceptions:** - Don't "just start" and figure it out - Don't assume the path is obvious - Don't skip planning for "simple" features ## The Planning Cycle ```dot digraph plan_cycle { rankdir=LR; analyze [label="ANALYZE\nStudy spec", shape=box, style=filled, fillcolor="#ffcccc"]; decompose [label="DECOMPOSE\nBr