/pm-do — Execute Task
Phase 1: Claim & Context
- •Call
pm_get(task_id)to read the task - •If the task is
todowith no assignee:- •Call
pm_grab(task_id)to claim it (validates readiness) - •If grab fails, stop and show the blockers
- •Call
- •If the task is
in-progresswith a different assignee:- •Warn: "This task is assigned to {assignee}. Proceed anyway?"
- •Only continue if explicitly confirmed
- •Read the parent story for broader context:
- •Call
pm_get(story_id)to understand acceptance criteria
- •Call
- •Review the task's Implementation section and DoD
Phase 2: Execute
- •Read project documentation if touching new areas:
- •Call
pm_docs("project")for architecture context
- •Call
- •Implement the work described in the task:
- •Follow the implementation instructions
- •Write/modify the specified files
- •Run tests as described
- •Verify ALL DoD criteria are met — check off each item
Phase 3: Complete
- •Call
pm_update(task_id, status="review")if the task needs human review, OR callpm_update(task_id, status="done")if all DoD criteria are met - •Check if all sibling tasks in the story are done:
- •Call
pm_activeor list tasks for the story - •If all done, suggest: "All tasks for {story_id} are complete — update story to done?"
- •Call
- •Summarize what was done, files changed, tests run
- •Suggest next action: "Check the board for more work:
/pm board"