plan-management

Standardize devloop plan location, format, and update procedures.

9|2|Updated Dec 5, 2025
One-click install
npx skills add https://github.com/Zate/cc-plugins --skill plan-management-zate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-management
Source: https://github.com/Zate/cc-plugins/tree/main/plugins/devloop/skills/plan-management
Command: npx skills add https://github.com/Zate/cc-plugins --skill plan-management-zate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent or outdated development plans lead to confusion, missed steps, and project delays. This Skill ensures all agents and commands follow strict conventions to keep devloop plans accurate and synchronized.

Core Features & Use Cases

  • Canonical Plan Location: Standardize the location of .claude/devloop-plan.md for easy discovery and access.
  • Standardized Format: Define a clear Markdown structure for plans, including overview, requirements, architecture, tasks, and a progress log.
  • Task Status Markers: Use consistent markers ([ ], [x], [~], [-], [!]) to track task progress.
  • Update Rules & Responsibilities: Clear guidelines for when and how to update the plan, and which agents are responsible.
  • Enforcement Modes: Configure advisory or strict enforcement to ensure plan updates are not missed.
  • Use Case: Update a task's status in the devloop plan, add a progress log entry, or understand the enforcement rules for plan consistency.

Quick Start

Mark Task 2.3 as complete in the .claude/devloop-plan.md file and add a progress log entry: 'Implemented password hashing'.

Frequently Asked Questions about plan-management

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

FAQPage Schema
How do I keep development plans synchronized across multiple agents and commands?

Plan management standardizes plan location, format, and update procedures to ensure all agents follow consistent conventions. Store plans at `.devloop/plan.md` with metadata fields (Created, Updated, Status, Current Phase) and task markers (`[ ]`, `[x]`, `[~]`, `[-]`, `[!]`) so every tool reads and updates the same canonical source.

What's the best way to track task status in a development workflow?

Use standardized task status markers in your plan: `[ ]` for pending, `[x]` for complete, `[~]` for in progress, `[-]` for blocked, and `[!]` for flagged. This ensures consistent visibility across your devloop and enforces uniform progress tracking regardless of which agent updates the plan.

How do I enforce consistent plan updates across my team?

Configure enforcement modes as either `advisory` (recommendations) or `strict` (required). Strict mode ensures plan updates are not missed by all agents and commands, preventing outdated plans that lead to confusion and project delays.

When should I use a standardized plan format instead of ad-hoc documentation?

Standardized formats prevent inconsistent or outdated development plans that cause missed steps and delays. Define clear Markdown structure with overview, requirements, architecture, tasks, and progress logs so every team member knows where to look and what to expect.

Can I archive old development plans while keeping current ones active?

Plan management implements archival workflows alongside active plan management. This lets you maintain a history of completed plans while keeping your canonical `.devloop/plan.md` focused on current work.