microsoft/hve-core

Public

mirrored fromhttps://github.com/microsoft/hve-coreAvailable

CodeCommitsIssuesPull requestsActionsInsightsSecurity
docs/improve-installation-language

Branches

Tags

  • No tags available.
0Branches0Tags
Go to file
Add file
Code

Clone

HTTPS

Download ZIP

docs/rpi/task-planner.md

160lines ยท modepreview

---
title: Task Planner Guide
description: Use the Task Planner chat mode to create actionable implementation plans from research findings
author: Microsoft
ms.date: 2025-01-28
ms.topic: tutorial
keywords:
  - task planner
  - rpi workflow
  - planning phase
  - github copilot
estimated_reading_time: 4
---

The Task Planner chat mode transforms research findings into actionable implementation plans. It creates coordinated planning files with checkboxes, detailed specifications, and line number references for precise execution.

## When to Use Task Planner

Use Task Planner after completing research when you need:

* ๐Ÿ“‹ **Structured implementation steps** with clear checkboxes
* ๐Ÿ“ **Detailed specifications** for each task
* ๐Ÿ”— **Cross-references** to research findings
* โฑ๏ธ **Phased execution** with dependencies

## What Task Planner Does

1. **Validates** that research exists (MANDATORY first step)
2. **Creates** three coordinated planning files
3. **Links** specifications to research with line numbers
4. **Organizes** tasks into logical phases with dependencies
5. **Generates** an implementation prompt for Task Implementor

## Output Artifacts

Task Planner creates three files:

```text
.copilot-tracking/
โ”œโ”€โ”€ plans/
โ”‚   โ””โ”€โ”€ YYYYMMDD-<topic>-plan.instructions.md   # Checklist with phases
โ”œโ”€โ”€ details/
โ”‚   โ””โ”€โ”€ YYYYMMDD-<topic>-details.md             # Specifications for each task
โ””โ”€โ”€ prompts/
    โ””โ”€โ”€ implement-<topic>.prompt.md              # Execution instructions
```

### Plan File

Contains checkboxes for phases and tasks, references to details with line numbers.

### Details File

Contains specifications for each task: files to modify, success criteria, research references.

### Implementation Prompt

Contains step-by-step instructions for Task Implementor, including stop controls.

## How to Use Task Planner

### Step 1: Clear Context

๐Ÿ”ด **Start with `/clear` or a new chat** after Task Researcher completes.

### Step 2: Select the Chat Mode

1. Open GitHub Copilot Chat (`Ctrl+Alt+I`)
2. Click the chat mode dropdown
3. Select **Task Planner**

### Step 3: Reference Your Research

Provide the path to your research document and any additional context.

### Step 4: Review the Plan

Task Planner will create all three files. Review:

* Are phases in logical order?
* Do tasks have clear success criteria?
* Are dependencies correctly identified?

## Example Prompt

```text
Using the research from .copilot-tracking/research/20250128-blob-storage-research.md,
create an implementation plan for adding Azure Blob Storage integration.

Focus on:
- The streaming upload approach recommended in the research
- Phased rollout: storage client first, then writer class, then tests
- Include error handling and retry logic in each phase
```

## Tips for Better Plans

โœ… **Do:**

* Reference specific research document
* Mention which recommended approach to use
* Suggest logical phases if you have preferences
* Include any additional constraints

โŒ **Don't:**

* Skip the research phase
* Ask for implementation (that's next step)
* Ignore the planning files once created

## Understanding the Plan Structure

### Phases

High-level groupings of related work:

```markdown
### [ ] Phase 1: Storage Client Setup
### [ ] Phase 2: Writer Implementation
### [ ] Phase 3: Integration Testing
```

### Tasks

Specific work items within phases:

```markdown
* [ ] Task 1.1: Create BlobStorageClient class
  * Details: .copilot-tracking/details/20250128-blob-storage-details.md (Lines 10-25)
```

### Line References

Every task references exact lines in the details file, which in turn references research:

```text
Plan โ†’ Details (Lines X-Y) โ†’ Research (Lines A-B)
```

## Common Pitfalls

| Pitfall              | Solution                             |
|----------------------|--------------------------------------|
| Research not found   | Complete Task Researcher first       |
| Phases too large     | Break into smaller, verifiable tasks |
| Missing dependencies | Review task order and prerequisites  |

## Next Steps

After Task Planner completes:

1. **Review** all three planning files
2. **Clear context** using `/clear` or starting a new chat
3. **Proceed to implementation** with [Task Implementor](task-implementor.md)

Use the generated implementation prompt (`.copilot-tracking/prompts/implement-*.prompt.md`) with Task Implementor.

---

๐Ÿค– *Crafted with precision by โœจCopilot using the RPI workflow*