pm-do

To execute unassigned project tasks, this workflow guides you through claiming the task, retrieving parent story context, implementing the code, and verifying completion against defined criteria. It manages status transitions from todo to in-progress, review, and done automatically.

Task execution retrieves parent story context by automatically fetching the associated user story details. This provides contextual awareness so you understand the broader feature requirements before implementing code and verifying against acceptance criteria.

Yes, managing task status updates requires integration with ProjectMan's MCP server. This connection is necessary to handle task status transitions, claim unassigned tasks, and update completion states throughout the development workflow.

Yes, you can update task status transitions including todo, in-progress, review, and done. The guided workflow manages these status updates automatically as you claim tasks, implement features, and verify completion against acceptance criteria.

The best way to verify task completion is using a guided workflow that retrieves parent story context, checks implementation against acceptance criteria, and suggests next steps upon completion. This ensures tasks meet defined standards before marking them done.

Task execution requires fetching parent user story details to provide contextual awareness for implementation. Without this context, developers risk building features that don't align with the broader story requirements and acceptance criteria defined in the project.