Micromanage

A tool for managing a development work plan for a ticket, organized by PRs and commits. Register or update the whole work plan for the current ticket you assigned to.

Before using this tool, you MUST:

• Understand requirements, goals, and specifications.
• Clarify the task scope and break it down into a hierarchy of PRs and commit plans.
• Analyze existing codebase and impact area.
• Include developer notes to document implementation considerations discovered during refinement.

Make sure PR and commit goals are clear enough to stand alone without their developer notes

This tool helps you monitor the current state of the implementation plan, view progress, and identify possible next steps. There is always exactly one task in either the in_progress or user_review state. IMPORTANT: There is always exactly one task in either the in_progress or user_review or needsRefinment state.

MANDATORY STATUS TRANSITION RULES: needsRefinment → in_progress:

• Requirements, implementation plan, and impact MUST be clearly explained. user_review → completed:
• A commit may not transition to "completed" without explicit user approval. No exceptions.

After receiving the tool response, you MUST::

• Monitor PRs, commits, and overall progress to spot blockers or items needing refinement.
• Review recommended actions to decide your next steps.
• Absolutely follow the content of "agentInstruction" in the response JSON!!.

A tool for updating the status and goals of development tasks. IMPORTANT:

• There is always exactly one task in either the in_progress or user_review or needsRefinment state.
• When setting status to "user_review", you MUST generate a review request message to the user.
• Always check and follow task-status-update-rule.mdc when updating task status.

After receiving the tool response, you MUST::

• 1. track the current whole status of the workplan.
• 2. check the detailed information including developer notes in the next task.