complete-plan

Generate docs/progress.json from dev-plan.md and optional frontend and backend plans.

2|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/potenlab/marketplace-potenlab --skill complete-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: complete-plan
Source: https://github.com/potenlab/marketplace-potenlab/tree/main/plugins/potenlab-workflow/skills/complete-plan
Command: npx skills add https://github.com/potenlab/marketplace-potenlab --skill complete-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Finalizes the planning phase by producing a centralized progress.json that tracks tasks, complexity, and agent assignments from plan documents.

Core Features & Use Cases

  • Generates progress.json from dev-plan.md and optional frontend-plan.md and backend-plan.md.
  • Orchestrates task tracking by classifying complexity and mapping dependencies for downstream agents.
  • Use Case: After a /plan run creates dev-plan.md, frontend-plan.md, and backend-plan.md, run /complete-plan to prepare a production-ready task tracker for execution.

Quick Start

Run the complete-plan skill after planning completes to synthesize the progress.json used by coder agents.

Frequently Asked Questions about complete-plan

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

FAQPage Schema
How do I generate a progress.json file from dev-plan.md for project management?

To generate progress.json from dev-plan.md, run the complete-plan command to read existing plan files and output a structured task tracker with complexity classifications, dependencies, and agent assignments.

What is the best way to track tasks and dependencies after creating project plan documents?

Tracking tasks and dependencies after creating plan documents requires finalizing the planning phase by synthesizing dev-plan.md, frontend-plan.md, and backend-plan.md into a centralized progress.json file for downstream execution.

Do I need frontend-plan.md and backend-plan.md to generate a progress.json task tracker?

You do not need frontend-plan.md and backend-plan.md to generate progress.json; dev-plan.md is the only required file, while frontend and backend plans are optionally read for task enrichment and complexity mapping.

Can I use complete-plan to classify task complexity and map agent assignments for team coordination?

Yes, you can use complete-plan to classify task complexity and map agent assignments for team coordination by reading plan documents and orchestrating task tracking into a production-ready progress.json file.

Why does complete-plan fail to write docs/progress.json during project planning automation?

Complete-plan fails to write docs/progress.json if the required docs/dev-plan.md file does not exist, as it depends on this file to synthesize task details and generate the structured progress tracker.

How to prepare plan files for automated task tracking and progress.json generation?

To prepare plan files for automated task tracking and progress.json generation, run a planning command to produce docs/dev-plan.md, docs/frontend-plan.md, and docs/backend-plan.md before invoking the complete-plan skill.