cfw-planning

Guide Claude Workflow planning with structured plan and tasklist documents.

4|Updated Oct 29, 2025
One-click install
npx skills add https://github.com/tordks/claude-workflow --skill cfw-planning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cfw-planning
Source: https://github.com/tordks/claude-workflow/tree/main/skills/cfw-planning
Command: npx skills add https://github.com/tordks/claude-workflow --skill cfw-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

AI-assisted software development often struggles with lost context, inconsistent structure, outdated plans, and loss of control. This skill provides a structured, plan-driven workflow to maintain context, ensure consistency, and enable safe amendments across complex, multi-session development efforts.

Core Features & Use Cases

  • Context Preservation: Stores planning and progress in structured documents (feature-plan.md, feature-tasklist.md) to prevent context loss between sessions, ensuring the AI remembers architectural rationale and design decisions.
  • Structured Development: Enforces a phase-based implementation with clear goals, deliverables, and checkpoints, ensuring consistent quality, review opportunities, and human control over the process.
  • Safe Plan Amendment: Provides a controlled process to update plans and tasklists when requirements change, preventing erroneous implementations and ensuring the AI's knowledge of the project remains accurate.
  • Use Case: When building a complex feature that spans multiple days or requires careful review, use this skill to guide Claude through planning, phased implementation, and safe adjustments, ensuring a high-quality, reviewable outcome.

Quick Start

Explain the Claude Workflow (CWF) planning system and how it helps manage complex features.

Frequently Asked Questions about cfw-planning

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

FAQPage Schema
How do I maintain context and structure across multiple AI-assisted development sessions?

Plan-driven development preserves context by storing structured planning and progress in feature-plan and tasklist documents across sessions, ensuring the AI remembers architectural decisions and design rationale instead of losing information between conversations.

What's the best way to organize complex feature development with AI assistance?

Phase-based implementation with clear goals, deliverables, and checkpoints enforces consistent quality and review opportunities. Structured planning documents guide the AI through multi-phase execution while maintaining human control over the process.

How do I safely update plans when requirements change during development?

A controlled amendment process lets you update plans and tasklists with safety rules that prevent erroneous implementations and keep the AI's project knowledge accurate as requirements evolve.

Can I use structured planning to prevent losing track of architectural decisions?

Yes. Conformant plan-specs and tasklist-specs document architectural rationale and design decisions in standardized formats, making them retrievable across sessions and preventing context loss in multi-day feature work.

When should I apply plan-driven workflow to AI-assisted development?

Use this approach for complex features spanning multiple days or requiring careful review. It's essential when you need checkpoint integration, phase orchestration, and the ability to amend plans safely without losing project context.