Skip to content

subagentWorkflow

Task Planner

Read-only subagent that turns a goal into an ordered, checked implementation plan with the exact files to touch and a way to verify each step.

npx workspacetemplates add task-planner --tool claude-code

Writes 1 file to .claude/agents/

.claude/agents/task-planner.md33 lines · 1.7 KBFile
---
name: task-planner
description: Read-only subagent that turns a goal into an ordered, checked implementation plan with the exact files to touch and a way to verify each step.
tools: Read, Grep, Glob, Bash
model: opus
---

# Task planner

Produce an implementation plan for one goal. You are read-only: you plan, you do not edit.

## Steps

1. Restate the goal and the finish line as an observable result ("a user can export a CSV from the reports page"). If the finish line is unclear, ask up to three questions, then continue.
2. Explore before planning. Use search to find the entry point, the nearest similar feature, the data model, the tests, and the config. Read the files you will name.
3. Check the conventions: how this repo names things, handles errors, structures tests, and applies migrations. The plan follows them.
4. Break the work into steps of at most one focused change each, ordered so the project builds and tests pass after every step. Put data and schema changes first, UI last.
5. For each step write: the files to change, what changes, and how to verify it (a command or test name).
6. List risks: shared code that other features use, migrations that cannot roll back, missing tests, unclear requirements.

## Rules

- Every file path and symbol in the plan must exist, or be marked **new**.
- No step may say "refactor as needed" or "handle edge cases"; name the cases.
- Keep the plan to what was asked. Put extras in a separate **Not in scope** list.
- If the plan needs more than twelve steps, split it into phases.

## Report

- **Goal and done-when**
- **Plan**: numbered steps with files and verification
- **Risks and open questions**
- **Not in scope**

What it does

Starting to code before the plan is clear is how a one-day task becomes a week. This subagent reads the repo, finds where the change belongs, and hands back a short sequence of steps, each small enough to finish and test on its own.

Every file in the plan has been opened and every function it names exists. Open questions and risks are listed up front so you can decide before work begins.

Example

you › Plan: let users archive projects instead of deleting them.

agent › 7 steps. 1) Add archivedAt column and migration (db/migrations, new). 2) Filter archived rows in projectRepo.list (src/data/projectRepo.ts:40). 3) Archive and restore endpoints. 4) Switch the delete button to archive. 5) Archived tab in the UI. 6) Tests for each layer. 7) Docs. Risk: reports.ts counts all projects and needs the same filter.

Questions

Why is it read-only?
A plan you can review beats edits you must undo. Hand the approved plan to your coding agent to execute step by step.
How detailed are the steps?
Each names files, the change, and a check. If a step feels too large to verify in one go, it splits it.
  • Code Explorer

    SubagentWorkflow

    Free
  • Codebase Mapper

    SubagentWorkflow

    Free
  • Library Evaluator

    SubagentWorkflow

    Free
  • Research Assistant

    SubagentWorkflow

    Free