How does CWF handle long-running tasks across sessions?

By storing the plan and tasklist in the .cwf/ directory, Claude can resume work exactly where it left off, even after the conversation history is cleared.

What is the primary purpose of the CWF skill?

CWF provides a structured framework for Claude Code to follow, using specific document formats to ensure complex features are planned, documented, and implemented in manageable phases.

Is CWF compatible with existing project structures?

Yes, CWF is designed to be non-intrusive, storing all its management files in a hidden .cwf/ directory to avoid cluttering your source code.

Can I modify a plan after I've started implementing it?

Yes, the CWF workflow includes an /amend-plan command that allows you to update architectural context or add new tasks safely while implementation is in progress.

What are 'Checkpoints' in the CWF workflow?

Checkpoints are validation steps performed at the end of each phase, such as linting, type-checking, or complexity analysis, to ensure code quality before proceeding.

Claude Workflow (CWF)

Name: Claude Workflow (CWF)
Author: tordks

bytordks

•

Productivity & Workflow

Implements a plan-driven development framework for Claude Code through structured architectural documentation and phase-based task execution.

About

Claude Workflow (CWF) is a specialized knowledge repository designed to bring discipline and structure to AI-driven development. It enables a rigorous planning lifecycle within Claude Code by separating architectural intent (the Plan) from implementation steps (the Tasklist). By utilizing RFC 2119 keywords for conformance and enforcing quality checkpoints at phase boundaries, CWF ensures that complex features are built methodically. This skill is essential for developers who need to maintain context across multiple sessions, document design rationale, and ensure that AI-generated code meets high quality and complexity standards.

Key Features

RFC 2119-compliant requirement definitions for rigorous documentation
Standardized Plan and Tasklist generation for architectural and execution context
2 GitHub stars
Organized directory structure that keeps project roots clean using .cwf/
Phase-by-phase implementation cycles with automated quality checkpoints
Structured plan amendment rules to handle changing requirements safely

Use Cases

Documenting design decisions and implementation steps for collaborative projects
Enforcing code quality and complexity checks at every phase of development
Managing complex, multi-day feature implementations with persistent context

About

Key Features

RFC 2119-compliant requirement definitions for rigorous documentation
Standardized Plan and Tasklist generation for architectural and execution context
2 GitHub stars
Organized directory structure that keeps project roots clean using .cwf/
Phase-by-phase implementation cycles with automated quality checkpoints
Structured plan amendment rules to handle changing requirements safely

Use Cases

Documenting design decisions and implementation steps for collaborative projects
Enforcing code quality and complexity checks at every phase of development
Managing complex, multi-day feature implementations with persistent context