harness-plan

Generate and synchronize Plans.md task markers with implementation status.

2|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/fockus/claude-skill-build --skill harness-plan-fockus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-plan
Source: https://github.com/fockus/claude-skill-build/tree/main/skills/harness-plan
Command: npx skills add https://github.com/fockus/claude-skill-build --skill harness-plan-fockus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Harness v3 integrations previously required juggling planning, task management, and progress synchronization across separate skills. This unified skill consolidates planning, plans-management, and sync-status into a single flow that generates Plans.md, tracks tasks with status markers, and aligns implementation with plan state.

Core Features & Use Cases

  • Unified planning flow that merges three legacy capabilities into one cohesive process.
  • Generates and maintains a canonical Plans.md with cc markers (cc:TODO, cc:WIP, cc:完了) and optional Phase notes.
  • Provides synchronization between Plans.md and actual implementation status, with diffs and retroactive insights.
  • Supports CI mode to derive task breakdown from existing Plans.md without user interviews.
  • Supplies templates and references to guide plan creation, task updates, and progress sync.

Quick Start

Tell me what to plan and I will generate a Plans.md with tasks and markers.

Frequently Asked Questions about harness-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a Plans.md file for sprint planning and task management?

To generate a Plans.md for sprint planning, provide your requirements to automatically create a canonical plan with tasks and status markers like cc:TODO, cc:WIP, and cc:完了.

How does Plans.md synchronization work with actual implementation status?

Plans.md synchronization aligns task management state with actual implementation progress by generating diffs and retroactive insights, ensuring development plans match current codebase status.

Can I derive task breakdown from an existing Plans.md without user interviews?

Yes, you can derive task breakdown from an existing Plans.md without user interviews by enabling CI mode, which automatically parses the canonical plan source to synchronize status.

What is the best way to consolidate planning and sync-status into a single workflow?

The best way to consolidate planning and sync-status is using a unified flow that merges separate capabilities into one process, managing task updates and progress synchronization via Plans.md.

Does Harness v3 planning support cross-team execution and retroactive insights?

Yes, Harness v3 planning supports cross-team execution by providing synchronization between Plans.md and implementation state, including optional Phase notes and retroactive insights for development tracking.