dev-planlisted

# enggenie:dev-plan Create implementation plans that are phased, independently deployable, and contain complete code in every step. No placeholders. No hand-waving. Every phase can be deployed to production before the next phase begins. If a step says "write a test," the actual test code is right there. If a step says "add a route," the route definition is spelled out. This is not a flat task list. This is a deployment-sequenced plan with gates between phases. Each phase ships alone or it does not ship at all. --- ## Announcement When this skill is invoked, announce: > I'm using enggenie:dev-plan to create an implementation plan. --- ## Entry Conditions Activate this skill when ANY of the following are true: - An approved design exists from enggenie:dev-brainstorm - An approved spec exists from enggenie:pm-refine - The user directly requests an implementation plan, task breakdown, or phased plan --- ## Planning Steps ### Step 1: Early Scope Check Before starting the plan, verify scope is manageable: - Count the repos/services involved. If more than 3, suggest decomposition into separate plans. - Check if the feature spans frontend + backend + infrastructure. If yes, confirm with the user that a single plan is appropriate. - If the spec (from pm-refine) already has phases, use those as your starting decomposition. ### Step 2: Check for Spec and Jira Context **If the user references a Jira ticket (e.g., "Pick up PROJ-1234", "Plan PROJ-1234"):** Read the Jira ti