Task Master

Turn a project roadmap into work that humans and agents can execute, verify, and resume without reconstructing the plan from chat history.

Keep the board small, current, and based on observable outcomes. Treat Task Master as the coordination layer; let specialized skills own planning, implementation, review, and pull-request mechanics.

Do not start implementation unless the user's request authorizes it. For an explicit read-only or no-change request, inspect and report board discrepancies in chat without updating the board, memory, or knowledge records. Existing user authorization and current corrections take precedence over workflow defaults.

Operations

Support these operations: