plan-product

Turn an accepted SPEC.md into PLAN.md — capabilities grouped into epics in build order, the module split (default: exactly one domain module), a per-module tool inventory carrying permission strings and approval flags, the tab list, the connector surface, background jobs, the refined role model, and the open questions the design loop must settle. Epic 1 is the thinnest real slice of the domain that proves module loads + tool runs + approval gate fires + tab renders; there is no Foundations epic, because the platform already is the foundation. USE FOR: sequencing capabilities into epics, deciding how many modules, naming every tool and its permission before any code exists, turning spec roles into concrete grants, listing what the design loop still has to decide. DO NOT USE FOR: writing the spec itself (../synthesize-spec/SKILL.md), publishing epics as GitHub issues on a board (../sync-backlog/SKILL.md), or pinning versions, schemas, solution layout and ADRs (/shape:design-product).

License

MIT