corca-plugins

CWF (Corca Workflow Framework)

Disclaimer (SoT)
README.ko.md is the single source of truth for CWF user-facing policy. If docs and implementation diverge, fix the plugin to match docs and report the mismatch via issue/PR.

한국어

A Claude Code plugin that turns structured development sessions into a repeatable workflow — from gathering context through retrospective analysis. Maintained by Corca for AI-Native Product Teams.

Installation

Quick start

# Add the marketplace
claude plugin marketplace add https://github.com/corca-ai/claude-plugins.git

# Install CWF
claude plugin install cwf@corca-plugins

# Restart Claude Code for hooks to take effect

After restart, run one-time bootstrap in Claude Code / Codex CLI:

cwf:setup

cwf:setup standardizes first-run behavior by handling:

• project config bootstrap (.cwf-config.yaml, .cwf-config.local.yaml)
• tool detection (Codex/Gemini/Tavily/Exa) and optional Codex integration
• local runtime dependency checks with install prompts (shellcheck, jq, gh, node, python3, lychee, markdownlint-cli2)
• optional index generation (improves agent routing and progressive-disclosure navigation)

For detailed flags, see setup.

Codex users (recommended)

If you also use Codex CLI, running only cwf:setup is enough to get guided defaults. Codex integration now follows the active plugin scope by default (local > project > user). Use the commands below when you want to re-apply Codex integration only:

cwf:setup --codex
cwf:setup --codex-wrapper

First workflow scenario

In Claude Code / Codex CLI, start with a plain prompt:

I need to solve <problem>. Please use CWF and drive the workflow.

The agent can invoke cwf:run and chain gather → clarify → plan → review(plan) → impl → review(code) → refactor → retro → ship. If automated review is not enough, switch to cwf:hitl to document key decision points and user concerns first, then continue chunk-by-chunk review.

You do not need to memorize every skill. The sections below explain why each skill exists and when to use it.

Update to latest version

claude plugin marketplace update corca-plugins
claude plugin update cwf@corca-plugins

Or from inside Claude Code / Codex CLI:

cwf:update               # Check + auto-update if newer version exists
cwf:update --check       # Version check only

Standalone plugins (legacy)

As of v3.0.0, legacy standalone plugins have been removed from the marketplace. If pre-v3.0 standalone plugins are installed, uninstall them and install cwf instead.

Operating Principles

What CWF Is

• A single workflow plugin (cwf) that integrates context gathering, requirement clarification, planning, implementation, review, retrospective, handoff, and shipping.
• A stateful workflow system where .cwf/cwf-state.yaml, session-log artifacts, and hooks preserve context across phase/session boundaries.
• A composable skill framework built on shared concepts (Expert Advisor, Tier Classification, Agent Orchestration, Decision Point, Handoff, Provenance Tracking, Adaptive Setup Contract).
• A cross-skill context-deficit resilience contract: after auto-compact/session restart, skills recover from persisted state/artifacts/handoff files instead of implicit chat memory.
• A roadmap toward lower user bottlenecks by chaining smaller approval units (for example, dark-factory-style operating patterns).

What CWF Is Not

• Not a replacement for project-specific engineering standards, CI gates, or human product ownership decisions.
• Not a guarantee that every decision can be fully automated; subjective decisions still require user confirmation.
• While each skill can be invoked independently, CWF is intentionally designed as a tightly coupled system and works best when skills are used together.

Assumptions

• Users work in repositories where session artifacts (.cwf/projects/, .cwf/cwf-state.yaml) are allowed and useful.
• Users accept progressive disclosure: start from AGENTS.md, then load deeper docs as needed.
• Users prefer deterministic validation scripts for recurring quality checks over relying on behavioral memory.
• Users expect missing prerequisites to trigger an install/configure prompt with retry, not a passive unavailable-only message.
• Users expect skills to remain operable when prior conversation context is missing, using persisted state/artifacts/handoff contracts.
• Users assume tokens are already cheap and likely to get cheaper (CWF targets heavy coding-agent usage patterns, including Claude Code/Codex $200 Max plan users).

Why CWF?

Problem