woostack-plan

Write a comprehensive implementation plan from one approved spec, structured as PR-sized increments. This is woostack's own planning phase — woostack-build step 4. It keeps the discipline that makes plans worth executing (file-structure first, bite-sized TDD tasks, no placeholders, a self-review pass) and adds the woostack conventions: markdown plans under .woostack/plans/, an opening **Source:** line that joins the plan 1:1 to its spec, backed by YAML frontmatter, decomposed into independently shippable increments, and a status: planning transition on the plan. It writes the plan and hands back; it owns no approval gate and never executes, commits, or merges.

It internalizes the plan-writing discipline as a native phase — the same move woostack-ideate, woostack-harden, and woostack-execute made on the phases around it. With this skill the build loop has no external skill dependencies. It pairs with woostack-execute as produce-plan / consume-plan: /woostack-plan <spec> writes the plan, /woostack-execute <plan> runs it.