microsoft/hve-core
Publicmirrored from https://github.com/microsoft/hve-coreAvailable
docs/rpi/task-planner.md
177lines · modecode
| 1 | --- |
| 2 | title: Task Planner Guide |
| 3 | description: Use the Task Planner custom agent to create actionable implementation plans from research findings |
| 4 | sidebar_position: 5 |
| 5 | author: Microsoft |
| 6 | ms.date: 2026-01-24 |
| 7 | ms.topic: tutorial |
| 8 | keywords: |
| 9 | - task planner |
| 10 | - rpi workflow |
| 11 | - planning phase |
| 12 | - github copilot |
| 13 | estimated_reading_time: 4 |
| 14 | --- |
| 15 | |
| 16 | The Task Planner custom agent transforms research findings into actionable implementation plans. It creates coordinated planning files with checkboxes, detailed specifications, and line number references for precise execution. |
| 17 | |
| 18 | ## When to Use Task Planner |
| 19 | |
| 20 | Use Task Planner after completing research when you need: |
| 21 | |
| 22 | * 📋 **Structured implementation steps** with clear checkboxes |
| 23 | * 📐 **Detailed specifications** for each task |
| 24 | * 🔗 **Cross-references** to research findings |
| 25 | * ⏱️ **Phased execution** with dependencies |
| 26 | |
| 27 | ## What Task Planner Does |
| 28 | |
| 29 | 1. **Validates** that research exists (MANDATORY first step) |
| 30 | 2. **Creates** two coordinated planning files |
| 31 | 3. **Links** specifications to research with line numbers |
| 32 | 4. **Organizes** tasks into logical phases with dependencies |
| 33 | |
| 34 | > [!NOTE] |
| 35 | > **Why the constraint matters:** Task Planner receives verified research and transforms it into actionable steps. Because it can't implement, it focuses entirely on sequencing, dependencies, and success criteria. The plan becomes a contract that prevents improvisation during implementation. |
| 36 | |
| 37 | ## Output Artifacts |
| 38 | |
| 39 | Task Planner creates two files: |
| 40 | |
| 41 | ```text |
| 42 | .copilot-tracking/ |
| 43 | ├── plans/ |
| 44 | │ └── {{YYYY-MM-DD}}-<topic>-plan.instructions.md # Checklist with phases |
| 45 | └── details/ |
| 46 | └── {{YYYY-MM-DD}}-<topic>-details.md # Specifications for each task |
| 47 | ``` |
| 48 | |
| 49 | ### Plan File |
| 50 | |
| 51 | Contains checkboxes for phases and tasks, references to details with line numbers. |
| 52 | |
| 53 | ### Details File |
| 54 | |
| 55 | Contains specifications for each task: files to modify, success criteria, research references. |
| 56 | |
| 57 | ## How to Use Task Planner |
| 58 | |
| 59 | ### Step 1: Clear Context |
| 60 | |
| 61 | 🔴 **Start with `/clear` or a new chat** after Task Researcher completes. |
| 62 | |
| 63 | ### Step 2: Invoke Task Planner |
| 64 | |
| 65 | #### Option 1: Use the Prompt Shortcut (Recommended) |
| 66 | |
| 67 | Type `/task-plan` in GitHub Copilot Chat with the research document opened in the editor. This automatically switches to Task Planner and begins the planning protocol. You can optionally provide the research file path: |
| 68 | |
| 69 | ```text |
| 70 | /task-plan |
| 71 | ``` |
| 72 | |
| 73 | If you don't specify a file, Task Planner will search for recent research documents in `.copilot-tracking/research/` and ask you to confirm which one to use. |
| 74 | |
| 75 | #### Option 2: Select the Custom Agent Manually |
| 76 | |
| 77 | 1. Open GitHub Copilot Chat (`Ctrl+Alt+I`) |
| 78 | 2. Click the agent picker dropdown |
| 79 | 3. Select **Task Planner** |
| 80 | |
| 81 | ### Step 3: Reference Your Research |
| 82 | |
| 83 | Provide the path to your research document and any additional context. |
| 84 | |
| 85 | ### Step 4: Review the Plan |
| 86 | |
| 87 | Task Planner will create all three files. Review: |
| 88 | |
| 89 | * Are phases in logical order? |
| 90 | * Do tasks have clear success criteria? |
| 91 | * Are dependencies correctly identified? |
| 92 | |
| 93 | ## Example Prompt |
| 94 | |
| 95 | With `.copilot-tracking/research/2025-01-28-blob-storage-research.md` opened in the editor |
| 96 | |
| 97 | ```text |
| 98 | /task-plan |
| 99 | Focus on: |
| 100 | - The streaming upload approach recommended in the research |
| 101 | - Phased rollout: storage client first, then writer class, then tests |
| 102 | - Include error handling and retry logic in each phase |
| 103 | ``` |
| 104 | |
| 105 | ## Tips for Better Plans |
| 106 | |
| 107 | ✅ **Do:** |
| 108 | |
| 109 | * Reference specific research document |
| 110 | * Mention which recommended approach to use |
| 111 | * Suggest logical phases if you have preferences |
| 112 | * Include any additional constraints |
| 113 | |
| 114 | ❌ **Don't:** |
| 115 | |
| 116 | * Skip the research phase |
| 117 | * Ask for implementation (that's next step) |
| 118 | * Ignore the planning files once created |
| 119 | |
| 120 | ## Understanding the Plan Structure |
| 121 | |
| 122 | ### Phases |
| 123 | |
| 124 | High-level groupings of related work: |
| 125 | |
| 126 | ```markdown |
| 127 | ### [ ] Phase 1: Storage Client Setup |
| 128 | ### [ ] Phase 2: Writer Implementation |
| 129 | ### [ ] Phase 3: Integration Testing |
| 130 | ``` |
| 131 | |
| 132 | ### Tasks |
| 133 | |
| 134 | Specific work items within phases: |
| 135 | |
| 136 | ```markdown |
| 137 | * [ ] Task 1.1: Create BlobStorageClient class |
| 138 | * Details: .copilot-tracking/details/2025-01-28-blob-storage-details.md (Lines 10-25) |
| 139 | ``` |
| 140 | |
| 141 | ### Line References |
| 142 | |
| 143 | Every task references exact lines in the details file, which in turn references research: |
| 144 | |
| 145 | ```text |
| 146 | Plan → Details (Lines X-Y) → Research (Lines A-B) |
| 147 | ``` |
| 148 | |
| 149 | ## Common Pitfalls |
| 150 | |
| 151 | | Pitfall | Solution | |
| 152 | |----------------------|--------------------------------------| |
| 153 | | Research not found | Complete Task Researcher first | |
| 154 | | Phases too large | Break into smaller, verifiable tasks | |
| 155 | | Missing dependencies | Review task order and prerequisites | |
| 156 | |
| 157 | ## Next Steps |
| 158 | |
| 159 | After Task Planner completes: |
| 160 | |
| 161 | 1. **Review** all three planning files |
| 162 | 2. **Clear context** using `/clear` or starting a new chat |
| 163 | 3. **Proceed to implementation** using `/task-implement` to switch to [Task Implementor](task-implementor.md) |
| 164 | |
| 165 | The `/task-implement` prompt automatically locates the plan and switches to Task Implementor. |
| 166 | |
| 167 | > [!TIP] |
| 168 | > Use the **⚡ Implement** handoff button when available to transition directly to Task Implementor with context. |
| 169 | |
| 170 | After implementation, continue to [Task Reviewer](task-reviewer.md) to validate against specifications. |
| 171 | |
| 172 | --- |
| 173 | |
| 174 | <!-- markdownlint-disable MD036 --> |
| 175 | *🤖 Crafted with precision by ✨Copilot following brilliant human instruction, |
| 176 | then carefully refined by our team of discerning human reviewers.* |
| 177 | <!-- markdownlint-enable MD036 --> |
| 178 | |