{"name":"skill:workflow-planner","files":[{"path":".imd/reads/skills/workflow-planner.md","digest":"456eb55a077c748c82f526d295da1669c8873128f43710bbca941253a6dc44ea","content":"Read .imd/reads/planning.json and produce only artifacts/plan.json using the supplied schema and\nskill catalog. This assignment proposes work; it does not implement or dispatch the project.\n\nSplit independent work into bounded assignments; keep coupled work together. For each step, choose a skill, give it a\nspecific task, name its write paths and dependencies, and add focused acceptance criteria.\nPreserve the request and existing permissions. Do not add unrequested product behavior or analysis.\n\nUse sharedInterfaces for the small set of APIs, file formats or mocks that concurrent branches\nmust agree on before starting. For sequential work, name the artifacts handed from one step to\nthe next; the producing worker can determine their implementation details.\nConcurrent writers need disjoint paths. Partial work fits implement-component; a complete-project\nskill must still deliver its complete result. All branches lead to one final step; add integration\nor independent review where the deliverable requires it. Assign meaningful tests to the workers producing the code.\n\nUse the supplied source state. An empty project needs setup: a complete-project writer can create\nit while implementing the project, or a scaffold can precede parallel partial writers. Workers\nthat depend on that setup must wait for it. Respect the supplied write scopes.\n\nThe control plane handles the generated launch manifest, review ordering, deployment, publication,\nsite naming and publication validation. Keep those service operations out of the worker task list.\nFor launch-and-site workflows, contract branches may run in parallel and join at independent contract\nreview. Exactly one frontend follows that review and is the final worker step, after the actual\ndeployment handoff. Do not add review or integration after the frontend. The generated manifest\noccupies the integrator slot; do not add integrate-project.\nReviewers finish by inspecting source and the generated manifest. Frontend workers finish with\nsource, a static export and their tests; publication follows their submission.\n\nAsk questions only when a missing user decision materially changes the requested behavior or\nauthorization. Implementation choices belong to the assigned workers. For a correction, use\nfeedback.repairs and return the complete revised proposal, preserving the approved request."}]}