Jiraチケットの要件とConfluenceの関連ドキュメントを基に、Frontend/Backend/Infrastructureに分割した実装計画を策定するプランニングスキル。Jiraチケット情報とConfluence検索結果が前段で取得済みであることを前提とし、構造化された実装計画を出力する。「プランニング」「実装計画策定」「タスク分割」などの文脈で使用。
ccwf-cli
ccwf-cli is an open-source workflow skill for Claude Code, published by breaking-brake. Its author describes it as: “Use the `ccwf` CLI (from @cc-wf-studio/cli) to render, validate, preview, export, or run cc-wf-studio workflow JSON files from the terminal. Apply whenever the user mentions viewing, visualizing, checking, executing,…”. The project has 5.4k stars on GitHub and ships custom license terms, so review them before reuse. Add it to your setup with `git clone https://github.com/breaking-brake/cc-wf-studio ~/.claude/skills/ccwf-cli`.
What ccwf-cli does
`ccwf` is the command-line entry into cc-wf-studio — a visual AI-agent workflow tool. It treats `.vscode/workflows/*.json` workflow files as inputs and lets you render them as Markdown, validate the schema, open them in a browser-based viewer, convert them into Agent Skills, or execute them. The same workflow JSON also drives the VSCode extension and an MCP server, so you can pick whichever interface fits the situation.
Installation
Add ccwf-cli to your agent with:
git clone https://github.com/breaking-brake/cc-wf-studio ~/.claude/skills/ccwf-cliAlways review a skill's source before installing it. This command comes from the skill's public repository; the linked repo is the source of truth for exact setup steps.
What's inside
The SKILL.md for ccwf-cli is organised into these sections:
- Prerequisites
- Core workflow
- Subcommand reference
- ccwf render <file>
- Mapping user phrasing to subcommands
- Tips & gotchas
- Related interfaces
When to use it
Reach for ccwf-cli when you want workflow help from Claude Code without writing the same instructions every session. Load the skill and the agent picks it up automatically for relevant tasks.
Strengths
- Ships in breaking-brake/cc-wf-studio, an established project with 5,354 GitHub stars
- Declares compatibility with Claude Code
- Actively maintained (recent commits)
Things to check
- No license declared — confirm terms with the author before reuse
Topics
Frequently asked questions
- What does ccwf-cli do?
- Use the `ccwf` CLI (from @cc-wf-studio/cli) to render, validate, preview, export, or run cc-wf-studio workflow JSON files from the terminal. Apply whenever the user mentions viewing, visualizing, checking, executing, or converting a workflow under `.vscode/workflows/` (or any `*workflow*.json`), wants a Mermaid diagram of a workflow, asks to "see" / "preview" / "open" a workflow, or wants to run a workflow as a Claude Code Skill without opening VSCode.
- How do I install ccwf-cli?
- Run git clone https://github.com/breaking-brake/cc-wf-studio ~/.claude/skills/ccwf-cli in your agent, then reload your skills. Review the source at https://github.com/breaking-brake/cc-wf-studio before installing.
- Is ccwf-cli free to use?
- ccwf-cli is publicly available on GitHub, but breaking-brake has not declared a standard open-source license (Other). Confirm the terms with the author before reusing it.
- Which agents does ccwf-cli work with?
- ccwf-cli declares compatibility with Claude Code. Agent Skills use a portable SKILL.md format, so other compatible clients can usually load it too.
- Where does ccwf-cli come from?
- ccwf-cli ships inside breaking-brake/cc-wf-studio, a repository that contains 11 catalogued skills in total. The repository's 5,354 GitHub stars apply to that whole collection, not to this skill on its own.
Related skills
More Workflow →Run one unattended IDEATION iteration of the autonomous value-creation loop — invent improvements a user of cc-wf-studio would notice, judge them against the value bar, and file the winners as locked `idea` issues. Never implements anything; the next-task skill builds from the queue this skill fills. Use when the user says "アイデア出して", "next idea", or wants proposals without implementation.
Run one unattended IDEATION iteration of the quality-assurance loop — find the highest-value untested behavior in the codebase, judge it against the QA value bar, and file ONE locked `qa` issue specifying the test to write. Never writes code or tests; the next-qa skill builds from the queue this skill fills. Use when the user says "QAアイデア", "next qa idea", or wants the QA backlog refilled without implementation.
Run one unattended iteration of the QUALITY-ASSURANCE loop — steward any in-flight QA PR, then build ONE queued `qa` issue (test infrastructure, unit tests, regression tests for known bugs) on a branch off auto-qa and open a PR that squash-merges on green CI. Adds tests and tooling only; never edits product source. Use when the user says "QAタスク", "next qa", "テストを進めて", or wants autonomous progress on the quality track.
Run one unattended IMPLEMENTATION iteration of the autonomous value-creation loop — steward any in-flight PR, fix interrupts (red CI / security / human bugs), or else build ONE queued `idea` issue on a branch off auto-dev and open a PR that squash-merges on green CI. Ideation lives in the next-idea skill; this skill consumes its queue. Use when the user says "次のタスク", "next task", "続きをやって", or wants autonomous progress without specifying what to do.