scope-it

Coordinate scope and delivery planning. The selected skills own their complete outputs, reviews and publication; this coordinator connects the published artifacts in a Delivery Map. Finish with verified publication so another session can continue from the parent alone. Implementation belongs to the executor's workflow.

Workflow

Orient. Read repository guidance, artifacts and approvals. Resolve the roles and placement below; reuse confirmed work. Find repository facts, recommend answers and ask unresolved questions in dependency order.
Scope. Give the Scope skill the settled context and agreed placement. Let it complete its native content checks and reviews, then publish under the authority below. Keep the complete output and read back its actual location before Tickets.
Tickets. Pass the complete published Scope and real reference to the Tickets skill. Resolve choices affecting shape, responsibilities or readiness before publication. Let the source propose, review and publish complete tickets in the agreed placement; retain their verified identities.
Assemble. Reconcile this planning session's repository artifacts, changes and created worktrees, including work from invoked skills, with current status/diffs, worktree ownership evidence and confirmed delivery obligations before deciding Planning Carry and cleanup. Build the Map from the published artifacts and verified relationships. Retain every agreed delivery obligation with its owner, trigger and required evidence. Requirements and acceptance stay complete in the source artifacts; return gaps or conflicts to the responsible source for approved revision.
Publish. Show the Map, remaining planning-file and preference writes, and any remaining worktrees to remove. Use approval covering those concrete changes, then perform only them. Preserve the source artifacts and record the canonical Map identity.
Verify and finish. Freshly compare the complete sources, Map and remaining writes with their approvals, including links, metadata, attachments and both relationship axes. Check unchanged Scope/Ticket bytes and one canonical Map. Report the parent, Map and applicable delivery evidence, then stop. Planning approval does not authorize implementation or its activation, merging, deployment, ticket closure or commits/pushes to the default branch.

Conditional references

Read the applicable reference before the affected work, including when reusing completed artifacts: