claude-workflow

Automate planning and task execution with RFC 2119 conformance.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured, RFC-2119 conformant workflow framework for Claude-driven planning tasks. It helps teams encode WHY/WHAT decisions and WHEN/HOW execution steps, reducing ambiguity and enabling consistent AI-assisted feature development.

Core Features & Use Cases

  • Plan Document and Tasklist: Plan documents capture architectural context and design rationale; Tasklists provide step-by-step execution guidance.
  • Conformance and Tailoring: RFC 2119 keywords drive explicit requirements; tailoring guidance for different conformance levels.
  • Checkpoints and Phase Workflow: Stage-based workflow with checkpoints and human reviews to maintain quality and traceability.
  • Lifecycle Guidance: Brainstorm, write-plan, implement-plan, and amend-plan commands guide AI-assisted development.

Use Case: A team defines a feature and produces a Plan + Tasklist, then uses /implement-plan to incrementally implement across phases with checkpoints.

Quick Start

Load the Claude Workflow skill and begin with creating a Plan + Tasklist for a feature, then start implementation by running /brainstorm (optional) → /write-plan to generate a Plan and Tasklist → /implement-plan to begin Phase 1.

Frequently Asked Questions about claude-workflow

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

FAQPage Schema
How do I create a structured plan and tasklist for feature development?

A plan document captures architectural context and design rationale while a tasklist provides step-by-step execution guidance. Start with /write-plan to generate both documents from your feature definition, encoding WHY/WHAT decisions and WHEN/HOW execution steps to reduce ambiguity and enable consistent AI-assisted development.

What does RFC 2119 conformance mean in workflow planning?

RFC 2119 keywords (MUST, SHOULD, MAY, etc.) drive explicit requirements in planning documents. This Skill enforces conformance with these keywords to create unambiguous specifications, ensuring team members and AI systems interpret requirements consistently across planning and execution phases.

How do I implement a feature incrementally across phases with checkpoints?

Use /implement-plan to begin Phase 1 after your Plan and Tasklist are ready. The workflow stages execution with built-in checkpoints and human review points to maintain quality and traceability, enabling you to advance through phases while enforcing conformance rules and amendment safety.

Can I use this workflow to amend plans mid-project?

Yes. The Skill provides amendment safety rules and an amend-plan command for mid-cycle modifications. This lets you adjust plans while maintaining RFC 2119 conformance, phase integrity, and traceability across multi-phase feature cycles without compromising prior checkpoint decisions.

What's the entry point for teams new to plan-driven AI workflows?

Begin with /brainstorm (optional) to explore feature space, then /write-plan to generate a Plan and Tasklist. These outputs encode architectural decisions and execution steps in a conformant structure, giving your team an explicit blueprint before moving to /implement-plan and staged execution.

Does this workflow enforce specific file-tree markers and structure requirements?

Yes. The Skill enforces file-tree markers, plan-spec and tasklist-spec adherence, and phase-based workflow markers. This standardization ensures consistency across projects, enables tooling to validate compliance, and maintains traceability for complex multi-phase feature development.