Agent skill

Workflow Plan

by catlog22 in catlog22/Claude-Code-Workflow

Unified planning skill - 4-phase planning workflow, plan verification, and interactive replanning.

MITAuto-check: notesAgent Workflows

Install Workflow Plan

skills CLI
$ npx skills add catlog22/Claude-Code-Workflow --skill workflow-plan -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install catlog22/Claude-Code-Workflow workflow-plan --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/catlog22/Claude-Code-Workflow.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/workflow-plan .claude/skills/workflow-plan && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
workflow-plan
GitHub stars
2.1k
Token cost
~4.8k tokens
SKILL.md length
1,334 words
Files
7
Skills in repo
82
Repo updated
First seen
Licence
MIT

At a glance

Unified planning skill - 4-phase planning workflow, plan verification, and interactive replanning.

  • Works in 12 steps: Architecture Overview → Key Design Principles → Interactive Preference Collection → …
  • Workflow-plan-verify
  • SKILL.md covers 1. Architecture Overview, 2. Key Design Principles, 3. Interactive Preference… and 4. Mode Detection, plus 11 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Workflow Plan is an agent skill from catlog22/Claude-Code-Workflow. Unified planning skill - 4-phase planning workflow, plan verification, and interactive replanning. Triggers on "workflow-plan", "workflow-plan-verify", "workflow:replan".

Its SKILL.md is about 4.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 7 other files (for example `phases/01-session-discovery.md`, `phases/02-context-gathering.md` and `phases/03-conflict-resolution.md`).

It sits in Agent Workflows. The repository describes itself as: JSON-driven multi-agent cadence-team development framework with intelligent CLI orchestration (Gemini/Qwen/Codex), context-first architecture, and automated workflow execution. The licence is MIT.

When your agent uses it

  • Workflow-plan-verify
  • Workflow:replan

Example prompts

  • “workflow-plan”
  • “workflow-plan-verify”
  • “workflow:replan”
  • “/workflow-plan”

Requirements

  • Pre-approved tools (allowed-tools): Skill, Agent, AskUserQuestion, TodoWrite, Read, Write, Edit, Bash, Glob, Grep

Workflow steps

12 steps, taken from the step headings in SKILL.md.

  1. Architecture Overview
  2. Key Design Principles
  3. Interactive Preference Collection
  4. Mode Detection
  5. Compact Recovery (Phase Persistence)
  6. Execution Flow
  7. Core Rules
  8. Input Processing
  9. Data Flow
  10. TodoWrite Pattern
  11. Post-Phase Updates
  12. Error Handling

What it can do on your machine

Read from SKILL.md and the folder at commit 07491b0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Skill
    • Agent
    • AskUserQuestion
    • TodoWrite
    • Read
    • Write
    • Edit
    • Bash
    • Glob
    • Grep

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are json and javascript).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Workflow Plan loads about 4.8k tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 1,334 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~46
When it runs · the whole SKILL.md, loaded when a task matches
~4.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Skill, Agent, AskUserQuestion, TodoWrite, Read, Write, Edit, Bash, Glob, Grep

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from catlog22/Claude-Code-Workflow at commit 07491b0, republished under its MIT licence (© catlog22). 1,334 words, ~4,812 tokens.

Download SKILL.mdSave it as .claude/skills/workflow-plan/SKILL.md (or your agent's skills folder). This skill also uses 6 other files; get the full folder from GitHub.
name
workflow-plan
description
Unified planning skill - 4-phase planning workflow, plan verification, and interactive replanning. Triggers on "workflow-plan", "workflow-plan-verify", "workflow:replan".
allowed-tools
Skill, Agent, AskUserQuestion, TodoWrite, Read, Write, Edit, Bash, Glob, Grep
<purpose>
Unified planning skill combining 4-phase planning workflow, plan quality verification, and interactive replanning. Produces IMPL_PLAN.md, task JSONs, verification reports, and manages plan lifecycle through session-level artifact updates. Routes by mode (plan | verify | replan) and acts as a pure orchestrator: executes phases, parses outputs, and passes context.
</purpose>
<process>

1. Architecture Overview

┌──────────────────────────────────────────────────────────────────┐
│  Workflow Plan Orchestrator (SKILL.md)                            │
│  → Route by mode: plan | verify | replan                         │
│  → Pure coordinator: Execute phases, parse outputs, pass context │
└──────────────────────────────────┬───────────────────────────────┘
                                │
        ┌───────────────────────┼───────────────────────┐
        ↓                       ↓                       ↓
  ┌───────────┐          ┌───────────┐           ┌───────────┐
  │ Plan Mode │          │  Verify   │           │  Replan   │
  │ (default) │          │   Mode    │           │   Mode    │
  │ Phase 1-4 │          │  Phase 5  │           │  Phase 6  │
  └─────┬─────┘          └───────────┘           └───────────┘
        │
    ┌───┼───┬───┐
    ↓   ↓   ↓   ↓
  ┌───┐┌───┐┌───┐┌───┐
  │ 1 ││ 2 ││ 3 ││ 4 │
  │Ses││Ctx││Con││Gen│
  └───┘└───┘└───┘└─┬─┘
                    ↓
              ┌───────────┐
              │ Confirm   │─── Verify ──→ Phase 5
              │ (choice)  │─── Execute ─→ Skill("workflow-execute")
              └───────────┘─── Review ──→ Display session status inline

2. Key Design Principles

  1. Pure Orchestrator: SKILL.md routes and coordinates only; execution detail lives in phase files
  2. Progressive Phase Loading: Read phase docs ONLY when that phase is about to execute
  3. Multi-Mode Routing: Single skill handles plan/verify/replan via mode detection
  4. Task Attachment Model: Sub-command tasks are ATTACHED, executed sequentially, then COLLAPSED
  5. Auto-Continue: After each phase completes, automatically execute next pending phase
  6. Accumulated State: planning-notes.md carries context across phases for N+1 decisions

3. Interactive Preference Collection

Before dispatching to phase execution, collect workflow preferences via AskUserQuestion:

javascript
// ★ 统一 auto mode 检测:-y/--yes 从 $ARGUMENTS 或 ccw 传播
const autoYes = /\b(-y|--yes)\b/.test($ARGUMENTS)

if (autoYes) {
  // 自动模式:跳过所有询问,使用默认值
  workflowPreferences = { autoYes: true, interactive: false }
} else {
  const prefResponse = AskUserQuestion({
    questions: [
      {
        question: "是否跳过所有确认步骤(自动模式)?",
        header: "Auto Mode",
        multiSelect: false,
        options: [
          { label: "Interactive (Recommended)", description: "交互模式,包含确认步骤" },
          { label: "Auto", description: "跳过所有确认,自动执行" }
        ]
      }
    ]
  })

  workflowPreferences = {
    autoYes: prefResponse.autoMode === 'Auto'
  }

  // For replan mode, also collect interactive preference
  if (mode === 'replan') {
    const replanPref = AskUserQuestion({
      questions: [
        {
          question: "是否使用交互式澄清模式?",
          header: "Replan Mode",
          multiSelect: false,
          options: [
            { label: "Standard (Recommended)", description: "使用安全默认值" },
            { label: "Interactive", description: "通过提问交互式澄清修改范围" }
          ]
        }
      ]
    })
    workflowPreferences.interactive = replanPref.replanMode === 'Interactive'
  }
}

workflowPreferences is passed to phase execution as context variable, referenced as workflowPreferences.autoYes, workflowPreferences.interactive within phases.

4. Mode Detection

javascript
const args = $ARGUMENTS
const mode = detectMode(args)

function detectMode(args) {
  // Skill trigger determines mode
  if (skillName === 'workflow-plan-verify') return 'verify'
  if (skillName === 'workflow:replan') return 'replan'
  return 'plan'  // default: workflow-plan
}

5. Compact Recovery (Phase Persistence)

Multi-phase planning (Phase 1-4/5/6) spans long conversations. Uses 双重保险: TodoWrite 跟踪 active phase 保护其不被压缩,sentinel 作为兜底。

⚠️ COMPACT DIRECTIVE: Context compression MUST check TodoWrite phase status. The phase currently marked in_progress is the active execution phase — preserve its FULL content. Only compress phases marked completed or pending.

6. Execution Flow

Plan Mode (default)
Input Parsing:
   └─ Convert user input to structured format (GOAL/SCOPE/CONTEXT)

Phase 1: Session Discovery
   └─ Ref: Read("phases/01-session-discovery.md")
      └─ Output: sessionId (WFS-xxx), planning-notes.md

Phase 2: Context Gathering
   └─ Ref: Read("phases/02-context-gathering.md")
      ├─ Tasks attached: Analyze structure → Identify integration → Generate package
      └─ Output: contextPath + conflictRisk

Phase 3: Conflict Resolution (conditional: conflictRisk ≥ medium)
   └─ Decision (conflictRisk check):
      ├─ conflictRisk ≥ medium → Ref: Read("phases/03-conflict-resolution.md")
      │   ├─ Tasks attached: Detect conflicts → Present to user → Apply strategies
      │   └─ Output: Modified brainstorm artifacts
      └─ conflictRisk < medium → Skip to Phase 4

Phase 4: Task Generation
   └─ Ref: Read("phases/04-task-generation.md")
      └─ Output: IMPL_PLAN.md, task JSONs, TODO_LIST.md

Plan Confirmation (User Decision Gate):
   └─ Decision (user choice):
      ├─ "Verify Plan Quality" (Recommended) → Route to Phase 5 (plan-verify)
      ├─ "Start Execution" → Skill(skill="workflow-execute")
      └─ "Review Status Only" → Display session status inline
Verify Mode
Phase 5: Plan Verification
   └─ Ref: Read("phases/05-plan-verify.md")
      └─ Output: PLAN_VERIFICATION.md with quality gate recommendation
Replan Mode
Phase 6: Interactive Replan
   └─ Ref: Read("phases/06-replan.md")
      └─ Output: Updated IMPL_PLAN.md, task JSONs, TODO_LIST.md

Phase Reference Documents (read on-demand when phase executes):

PhaseDocumentPurposeModeCompact
1phases/01-session-discovery.mdCreate or discover workflow sessionplanTodoWrite 驱动
2phases/02-context-gathering.mdGather project context and analyze codebaseplanTodoWrite 驱动
3phases/03-conflict-resolution.mdDetect and resolve conflicts (conditional)planTodoWrite 驱动
4phases/04-task-generation.mdGenerate implementation plan and task JSONsplanTodoWrite 驱动 + 🔄 sentinel
5phases/05-plan-verify.mdRead-only verification with quality gateverifyTodoWrite 驱动
6phases/06-replan.mdInteractive replanning with boundary clarificationreplanTodoWrite 驱动

Compact Rules:

  1. TodoWrite in_progress → 保留完整内容,禁止压缩
  2. TodoWrite completed → 可压缩为摘要
  3. 🔄 sentinel fallback → Phase 4 包含 compact sentinel;若 compact 后仅存 sentinel 而无完整 Step 协议,必须立即 Read("phases/04-task-generation.md") 恢复

7. Core Rules

  1. Start Immediately: First action is mode detection + TodoWrite initialization, second action is phase execution
  2. No Preliminary Analysis: Do not read files, analyze structure, or gather context before Phase 1
  3. Parse Every Output: Extract required data from each phase output for next phase
  4. Auto-Continue via TodoList: Check TodoList status to execute next pending phase automatically
  5. Track Progress: Update TodoWrite dynamically with task attachment/collapse pattern
  6. Task Attachment Model: Skill execute attaches sub-tasks to current workflow. Orchestrator executes these attached tasks itself, then collapses them after completion
  7. Progressive Phase Loading: Read phase docs ONLY when that phase is about to execute
  8. DO NOT STOP: Continuous multi-phase workflow. After executing all attached tasks, immediately collapse them and execute next phase

8. Input Processing

Convert User Input to Structured Format:

  1. Simple Text → Structure it:

    User: "Build authentication system"
    
    Structured:
    GOAL: Build authentication system
    SCOPE: Core authentication features
    CONTEXT: New implementation
  2. Detailed Text → Extract components:

    User: "Add JWT authentication with email/password login and token refresh"
    
    Structured:
    GOAL: Implement JWT-based authentication
    SCOPE: Email/password login, token generation, token refresh endpoints
    CONTEXT: JWT token-based security, refresh token rotation
  3. File Reference (e.g., requirements.md) → Read and structure:

    • Read file content
    • Extract goal, scope, requirements
    • Format into structured description

9. Data Flow

Plan Mode
User Input (task description)
    ↓
[Convert to Structured Format]
    ↓ Structured Description:
    ↓   GOAL: [objective]
    ↓   SCOPE: [boundaries]
    ↓   CONTEXT: [background]
    ↓
Phase 1: session:start --auto "structured-description"
    ↓ Output: sessionId
    ↓ Write: planning-notes.md (User Intent section)
    ↓
Phase 2: context-gather --session sessionId "structured-description"
    ↓ Input: sessionId + structured description
    ↓ Output: contextPath (context-package.json) + conflictRisk
    ↓ Update: planning-notes.md (Context Findings + Consolidated Constraints)
    ↓
Phase 3: conflict-resolution [conditional: conflictRisk ≥ medium]
    ↓ Input: sessionId + contextPath + conflictRisk
    ↓ Output: Modified brainstorm artifacts
    ↓ Update: planning-notes.md (Conflict Decisions + Consolidated Constraints)
    ↓ Skip if conflictRisk is none/low → proceed directly to Phase 4
    ↓
Phase 4: task-generate-agent --session sessionId
    ↓ Input: sessionId + planning-notes.md + context-package.json + brainstorm artifacts
    ↓ Output: IMPL_PLAN.md, task JSONs, TODO_LIST.md
    ↓
Plan Confirmation (User Decision Gate):
    ├─ "Verify Plan Quality" (Recommended) → Route to Phase 5
    ├─ "Start Execution" → Skill(skill="workflow-execute")
    └─ "Review Status Only" → Display session status inline

Session Memory Flow: Each phase receives session ID, which provides access to:

  • Previous task summaries
  • Existing context and analysis
  • Brainstorming artifacts (potentially modified by Phase 3)
  • Session-specific configuration
Verify Mode
Input: --session sessionId (or auto-detect)
    ↓
Phase 5: Load artifacts → Agent-driven verification → Generate report
    ↓ Output: PLAN_VERIFICATION.md with quality gate
Replan Mode
Input: [--session sessionId] [task-id] "requirements"
    ↓
Phase 6: Mode detection → Clarification → Impact analysis → Backup → Apply → Verify
    ↓ Output: Updated artifacts + change summary

10. TodoWrite Pattern

Core Concept: Dynamic task attachment and collapse for real-time visibility into workflow execution.

Key Principles
  1. Task Attachment (when phase executed):

    • Sub-tasks are attached to orchestrator's TodoWrite
    • Phase 2, 3: Multiple sub-tasks attached
    • Phase 1, 4: Single task (atomic)
    • First attached task marked as in_progress, others as pending
    • Orchestrator executes these attached tasks sequentially
  2. Task Collapse (after sub-tasks complete):

    • Applies to Phase 2, 3: Remove detailed sub-tasks from TodoWrite
    • Collapse to high-level phase summary
    • Phase 1, 4: No collapse needed (single task, just mark completed)
    • Maintains clean orchestrator-level view
  3. Continuous Execution: After completion, automatically proceed to next pending phase

Lifecycle: Initial pending → Phase executed (tasks ATTACHED) → Sub-tasks executed → Phase completed (tasks COLLAPSED for 2/3, marked completed for 1/4) → Next phase → Repeat

Phase 2 (Tasks Attached):
json
[
  {"content": "Phase 1: Session Discovery", "status": "completed"},
  {"content": "Phase 2: Context Gathering", "status": "in_progress"},
  {"content": "  → Analyze codebase structure", "status": "in_progress"},
  {"content": "  → Identify integration points", "status": "pending"},
  {"content": "  → Generate context package", "status": "pending"},
  {"content": "Phase 4: Task Generation", "status": "pending"}
]
Phase 2 (Collapsed):
json
[
  {"content": "Phase 1: Session Discovery", "status": "completed"},
  {"content": "Phase 2: Context Gathering", "status": "completed"},
  {"content": "Phase 4: Task Generation", "status": "pending"}
]
Phase 3 (Tasks Attached, conditional):
json
[
  {"content": "Phase 1: Session Discovery", "status": "completed"},
  {"content": "Phase 2: Context Gathering", "status": "completed"},
  {"content": "Phase 3: Conflict Resolution", "status": "in_progress"},
  {"content": "  → Detect conflicts with CLI analysis", "status": "in_progress"},
  {"content": "  → Present conflicts to user", "status": "pending"},
  {"content": "  → Apply resolution strategies", "status": "pending"},
  {"content": "Phase 4: Task Generation", "status": "pending"}
]

Note: See individual Phase descriptions for detailed TodoWrite Update examples.

11. Post-Phase Updates

After each phase completes, update planning-notes.md:

  • After Phase 1: Initialize with user intent (GOAL, KEY_CONSTRAINTS)
  • After Phase 2: Add context findings (CRITICAL_FILES, ARCHITECTURE, CONFLICT_RISK, CONSTRAINTS)
  • After Phase 3: Add conflict decisions (RESOLVED, MODIFIED_ARTIFACTS, CONSTRAINTS) if executed
  • Memory State Check: After heavy phases (Phase 2-3), evaluate context window usage; if high (>120K tokens), trigger compact

See phase files for detailed update code.

12. Error Handling

  • Parsing Failure: If output parsing fails, retry command once, then report error
  • Validation Failure: If validation fails, report which file/data is missing
  • Command Failure: Keep phase in_progress, report error to user, do not proceed to next phase
  • Session Not Found (verify/replan): Report error with available sessions list
  • Task Not Found (replan): Report error with available tasks list
Show full SKILL.md (537 more words)Show less

13. Coordinator Checklist

Plan Mode
  • Pre-Phase: Convert user input to structured format (GOAL/SCOPE/CONTEXT)
  • Initialize TodoWrite before any command (Phase 3 added dynamically after Phase 2)
  • Execute Phase 1 immediately with structured description
  • Parse session ID from Phase 1 output, store in memory
  • Session Integrity: If reusing existing session, verify sessionIntegrity from Step 1.2.5; log warnings for incomplete brainstorm artifacts
  • Pass session ID and structured description to Phase 2 command
  • Parse context path from Phase 2 output, store in memory
  • Extract conflictRisk from context-package.json: Determine Phase 3 execution
  • If conflictRisk ≥ medium: Launch Phase 3 conflict-resolution with sessionId and contextPath
  • Wait for Phase 3 to finish executing (if executed), verify conflict-resolution.json created
  • If conflictRisk is none/low: Skip Phase 3, proceed directly to Phase 4
  • Pass session ID to Phase 4 command
  • Verify all Phase 4 outputs
  • Plan Confirmation Gate: Present user with choice (Verify → Phase 5 / Execute / Review Status)
  • If user selects Verify: Read phases/05-plan-verify.md, execute Phase 5 in-process
  • If user selects Execute: Skill(skill="workflow-execute")
  • If user selects Review: Display session status inline
  • Auto mode (workflowPreferences.autoYes): Auto-select "Verify Plan Quality", then auto-continue to execute if PROCEED
  • Update TodoWrite after each phase
  • After each phase, automatically continue to next phase based on TodoList status
Verify Mode
  • Detect/validate session (auto-detect from active sessions)
  • Initialize TodoWrite with single verification task
  • Execute Phase 5 verification agent
  • Present quality gate result and next step options
Replan Mode
  • Parse task ID from $ARGUMENTS (IMPL-N format, if present)
  • Detect operation mode (task vs session)
  • Initialize TodoWrite with replan-specific tasks
  • Execute Phase 6 through all sub-phases (clarification → impact → backup → apply → verify)

14. Structure Template Reference

Minimal Structure:

GOAL: [What to achieve]
SCOPE: [What's included]
CONTEXT: [Relevant info]

Detailed Structure (optional, when more context available):

GOAL: [Primary objective]
SCOPE: [Included features/components]
CONTEXT: [Existing system, constraints, dependencies]
REQUIREMENTS: [Specific technical requirements]
CONSTRAINTS: [Limitations or boundaries]

Prerequisite Skills:

  • brainstorm skill - Optional: Generate role-based analyses before planning
  • brainstorm skill - Optional: Refine brainstorm analyses with clarifications

Called by Plan Mode (4 phases):

  • /workflow:session:start - Phase 1: Create or discover workflow session
  • phases/02-context-gathering.md - Phase 2: Gather project context and analyze codebase (inline)
  • phases/03-conflict-resolution.md - Phase 3: Detect and resolve conflicts (inline, conditional)
  • memory-capture skill - Phase 3: Memory optimization (if context approaching limits)
  • phases/04-task-generation.md - Phase 4: Generate task JSON files (inline)

Follow-up Skills:

  • workflow-plan skill (plan-verify phase) - Verify plan quality (can also invoke via verify mode)
  • Display session status inline - Review task breakdown and current progress
  • Skill(skill="workflow-execute") - Begin implementation of generated tasks (skill: workflow-execute)
  • workflow-plan skill (replan phase) - Modify plan (can also invoke via replan mode)
</process>

<auto_mode> When workflowPreferences.autoYes is true (triggered by -y or --yes flag, or user selecting "Auto" mode):

  • Skip all confirmation prompts, use default values
  • Auto-select "Verify Plan Quality" at Plan Confirmation Gate
  • Auto-continue to execution if verification returns PROCEED
  • Skip interactive clarification in replan mode (use safe defaults) </auto_mode>

<success_criteria>

  • Mode correctly detected from skill trigger (plan / verify / replan)
  • TodoWrite initialized and updated after each phase with attachment/collapse pattern
  • All phases executed in sequence with proper data passing between phases
  • Phase documents loaded progressively via Read() only when phase is about to execute
  • planning-notes.md updated after each phase with accumulated context
  • Phase 3 conditionally executed based on conflictRisk assessment
  • Plan Confirmation Gate presented with correct options after Phase 4
  • All output artifacts generated: IMPL_PLAN.md, task JSONs, TODO_LIST.md
  • Compact recovery works: in_progress phases preserved, completed phases compressible
  • Error handling covers parsing failures, validation failures, and missing sessions/tasks </success_criteria>

© catlog22, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 6 other files in .claude/skills/workflow-plan of catlog22/Claude-Code-Workflow.

  • SKILL.md
  • phases/01-session-discovery.md
  • phases/02-context-gathering.md
  • phases/03-conflict-resolution.md
  • phases/04-task-generation.md
  • phases/05-plan-verify.md
  • phases/06-replan.md

Open the folder on GitHubat commit 07491b0

Compare with similar skills

Workflow Plan next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Workflow Plan compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Workflow Plan this skillcatlog22/Claude-Code-Workflow2.1k—~4.8kAutomated safety check: NotesMIT
MCP Server Builderanthropics/skills180k62 repos~2.3kAutomated safety check: PassApache-2.0
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official37k11 repos~4.1kAutomated safety check: NotesApache-2.0
Using Superpowersfarm-fe/farm5.6k34 repos~1.4kAutomated safety check: PassMIT
Executing Plans Inlineobra/superpowers296k2 repos~5.1kAutomated safety check: PassMIT
Claude Code Agent Developmentanthropics/claude-plugins-official37k8 repos~2.8kAutomated safety check: PassApache-2.0

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 62 repos~2.3k tokens
    Agent WorkflowsAuto-check passed
  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    37k GitHub starsUsed in 11 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes
  • Using Superpowers

    farm-fe/farm

    A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

    5.6k GitHub starsUsed in 34 repos~1.4k tokens
    Agent WorkflowsAuto-check passed
  • Executing Plans Inline

    obra/superpowers

    Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.

    296k GitHub starsUsed in 2 repos~5.1k tokens
    Agent WorkflowsAuto-check passed
  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    37k GitHub starsUsed in 8 repos~2.8k tokens
    Agent WorkflowsAuto-check passed
  • Skill Creator

    Azure/azqr

    Official

    Create new skills, modify and improve existing skills, and measure skill performance.

    794 GitHub starsUsed in 89 repos~8.2k tokens
    Agent WorkflowsAuto-check passed

More from catlog22/Claude-Code-Workflow

All 82 skills in this repo
  • Prompt Generator

    catlog22/Claude-Code-Workflow

    Generate or convert Claude Code prompt files — command orchestrators, skill files, agent role definitions, or style conversion of existing files.

    2.1k GitHub starsUsed in 1 repo~4.7k tokens
    Auto-check: notes
  • Ccw Help

    catlog22/Claude-Code-Workflow

    CCW command help system. An agent skill from catlog22/Claude-Code-Workflow.

    2.1k GitHub stars~2.5k tokensUpdated 3 mo ago
    Auto-check passed
  • Team Ultra Analyze

    catlog22/Claude-Code-Workflow

    Deep collaborative analysis team skill. An agent skill from catlog22/Claude-Code-Workflow.

    2.1k GitHub starsUsed in 1 repo~2.4k tokens
    Auto-check: notes
  • Brainstorm

    catlog22/Claude-Code-Workflow

    Unified brainstorming skill with dual-mode operation — auto mode (framework generation, parallel multi-role analysis, cross-role synthesis) and single role analysis.

    2.1k GitHub stars~4.8k tokensUpdated 3 mo ago
    Auto-check: notes
  • Ccw Chain

    catlog22/Claude-Code-Workflow

    Chain-based CCW workflow orchestrator. An agent skill from catlog22/Claude-Code-Workflow.

    2.1k GitHub stars~1.1k tokensUpdated 3 mo ago
    Auto-check: notes
  • Delegation Check

    catlog22/Claude-Code-Workflow

    Check workflow delegation prompts against agent role definitions for content separation violations.

    2.1k GitHub stars~2.8k tokensUpdated 3 mo ago
    Auto-check: notes

Categories

Questions about Workflow Plan

What does Workflow Plan do?

Unified planning skill - 4-phase planning workflow, plan verification, and interactive replanning. Workflow Plan is an agent skill from catlog22/Claude-Code-Workflow. Unified planning skill - 4-phase planning workflow, plan verification, and interactive replanning.

When should I use Workflow Plan?

Workflow Plan fits situations like: workflow-plan-verify; workflow:replan.

How do I install Workflow Plan in Claude Code?

Run `npx skills add catlog22/Claude-Code-Workflow --skill workflow-plan -a claude-code`. Or copy the skill folder (.claude/skills/workflow-plan in catlog22/Claude-Code-Workflow) into .claude/skills/workflow-plan in your project. Claude Code loads it when a task matches its description.

How do I install Workflow Plan in Codex?

Run `npx skills add catlog22/Claude-Code-Workflow --skill workflow-plan -a codex`. Or copy the skill folder (.claude/skills/workflow-plan in catlog22/Claude-Code-Workflow) into .agents/skills/workflow-plan in your project. Codex loads it when a task matches its description.

Can I use Workflow Plan in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add catlog22/Claude-Code-Workflow --skill workflow-plan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/workflow-plan, .gemini/skills/workflow-plan, .github/skills/workflow-plan and .opencode/skills/workflow-plan in your project.

What does Workflow Plan need to run?

SKILL.md names no scripts, command-line tools or credentials: Workflow Plan is instructions for the agent only. Its frontmatter pre-approves these tools: Skill, Agent, AskUserQuestion, TodoWrite, Read, Write, Edit, Bash, Glob, Grep.

Does Workflow Plan access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Workflow Plan safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Workflow Plan use?

Workflow Plan is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Workflow Plan use?

About 4.8k tokens (SKILL.md is roughly 19k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Workflow Plan?

Skills that share tags, products or a category with Workflow Plan: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 37k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 296k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Workflow Plan?

catlog22 (a GitHub user) maintains it in catlog22/Claude-Code-Workflow, which has 2,130 GitHub stars. The repository holds 82 skills in this directory. The repository was last updated on June 18, 2026.

Source: catlog22/Claude-Code-Workflow on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.