PM — Sprint Dev

Interactive skill that reads ready items from GitHub Issues (or local backlog), proposes how they should be grouped into PRs, and — with your approval — dispatches parallel sub-agents to implement, review, test, and PR each batch. Updates the issue tracker when work completes.

Manual only. You decide when to run this and what to build.

Note on GitHub Project sync. If github.project_sync.enabled is set in .pm/config.yml, sprint-dev relies on the project's built-in workflows to handle Status transitions when PRs are linked or merged (Ready → In Progress when a PR draft is linked, In Progress → In Review when the PR is opened for review, In Review → Done when merged). No MCP calls are made from this skill — the GitHub-side workflows do the work. Status field bootstrapping for items spawned during sprint execution happens later, via /pm:triage or /pm:reconcile.

Ground Rules

• Never auto-build. Always present the proposal and wait for user approval.
• Parallel when safe. Dispatch independent PRs in parallel when they don't touch the same files.
• Every PR must pass. Sub-agents run self-review + full test suite before PRing.
• Trust the check, not the worker. A sub-agent's self-review and "tests pass" are its opening claim, not proof. Phase 2C independently re-executes verification and loops findings back until the check actually passes — no code merges on a worker's own say-so, the orchestrator's included.
• Backlog is sacred. Only the orchestrator edits the backlog, never sub-agents.
• Report live. Tell the user about each PR as it completes, don't batch results.
• Discovered work stays out of scope. Sub-agents do NOT fix things they find along the way — they file issues tagged spawned-during-sprint.