Harness v3 integrated planning skill. Integrates the following three legacy skills:
planning(plan-with-agent) — Turning ideas into Plans.mdplans-management— Task state management and marker updatessync-status— Verifying synchronization between Plans.md and implementation
Quick Reference
| User input | Subcommand | Action |
|---|---|---|
| "計画を作って" / "create a plan" | create |
Interactive hearing → Generate Plans.md |
| "タスクを追加して" / "add a task" | add |
Add a new task to Plans.md |
| "完了にして" / "mark complete" | update |
Change the task marker to cc:complete |
| "今どこ?" / "check progress" | sync |
Cross-check and sync implementation with Plans.md |
harness-sync |
sync |
Check progress (equivalent to the standalone sync surface) |
harness-plan create |
create |
Create a plan |
Subcommand details
create — Create a plan
Hear out ideas and requirements, and generate an actionable Plans.md.
Flow:
- Check conversation context (extract from the preceding discussion or conduct a new hearing)
- Ask what to build (max 3 questions)
- Technical research (WebSearch)
- Extract feature list
- Priority matrix (Required / Recommended / Optional)
- Decide whether to adopt TDD (test design)
- Generate Plans.md (
cc:TODOwith markers) - Guide the next action
CI Mode (--ci):
No hearing. Use the existing Plans.md as-is and only perform task breakdown.
add — Add a task
Add a new task to Plans.md.
harness-plan add タスク名: 詳細説明 [--phase フェーズ番号]
Tasks are cc:TODO Added with the marker.
update — Update markers
Change a task's status marker.
harness-plan update [タスク名|タスク番号] [WIP|完了|blocked]
Marker correspondence table:
| Command | Marker |
|---|---|
WIP |
cc:WIP |
完了 / done |
cc:完了 |
blocked |
blocked |
TODO |
cc:TODO |
sync — Progress synchronization
Cross-check the implementation status with Plans.md, and detect and update differences.
Flow:
- Retrieve the current state of Plans.md
- Detect the Plans.md format (v1: 3 columns / v2: 5 columns)
- Retrieve implementation status from git status / git log
- Check agent traces (
.claude/state/agent-trace.jsonl) - Detect differences between Plans.md and the implementation
- Propose automatic corrections for unupdated markers
- Present the next action
Retrospective(Default ON):
cc:完了 If there is at least 1 task, automatically run a retrospective.
Analyze estimation accuracy, blocking cause patterns, and scope changes, and record the learnings.
sync --no-retro Can be explicitly skipped with
Plans.md format conventions
Format
# [プロジェクト名] Plans.md
作成日: YYYY-MM-DD
---
## Phase N: フェーズ名
| Task | 内容 | DoD | Depends | Status |
|------|------|-----|---------|--------|
| N.1 | 説明 | テスト通過 | - | cc:TODO |
| N.2 | 説明 | lint エラー 0 | N.1 | cc:WIP |
| N.3 | 説明 | マイグレーション実行可能 | N.1, N.2 | cc:完了 |
DoD(Definition of Done): Describe a verifiable completion condition in one line. "Looks good" and "works properly" are prohibited. Make it something that can be judged as Yes/No.
Depends: Dependencies between tasks.-(no dependencies), task number (N.1), comma-separated (N.1, N.2), phase dependency (Phase N)。
Marker list
| Marker | Meaning |
|---|---|
pm:依頼中 |
Requested by PM |
cc:TODO |
Not started |
cc:WIP |
In progress |
cc:完了 |
Worker work complete |
pm:確認済 |
PM review complete |
blocked |
Blocked (reason must always be stated) |
Related skills
harness-sync— Sync implementation and Plans.mdharness-work— Implement the planned tasksharness-review— Implementation reviewharness-setup— Project initialization