cc-workflow-ai-editor
The cc-workflow-ai-editor skill creates and modifies visual AI agent workflows in CC Workflow Studio through conversational interaction. Use it when you need to build new workflows, edit existing ones, organize nodes into groups, or adjust workflow canvas elements via the integrated MCP server tools that handle schema retrieval, workflow application, and node updates.
git clone --depth 1 https://github.com/breaking-brake/cc-wf-studio /tmp/cc-workflow-ai-editor && cp -r /tmp/cc-workflow-ai-editor/.roo/skills/cc-workflow-ai-editor ~/.claude/skills/cc-workflow-ai-editorSKILL.md
1. Call `get_workflow_schema` via `cc-workflow-studio` MCP server
2. Call `get_current_workflow` via `cc-workflow-studio` MCP server
3. Ask the user what to create or modify
4. Generate workflow JSON: use built-in sub-agents (builtInType: explore/plan/general-purpose) by default. Only call `list_available_agents` when the user explicitly asks to use an existing custom sub-agent.
5. Apply changes via `cc-workflow-studio` MCP server:
- **New workflow or structural changes** (add/remove nodes/connections): use `apply_workflow`
- **Partial updates to existing nodes** (change name, position, or data): use `update_nodes` (more token-efficient)
- Fix errors if any
6. Ask for feedback, repeat from step 4
## Group Node
Group nodes are visual containers for organizing related nodes on the canvas. They do NOT affect workflow execution.
### Rules
- Group nodes have `type: "group"` and require `data.label` (display name)
- Group nodes must have `style: { width, height }` to define their visual area
- Group nodes CANNOT have connections (no edges to/from group nodes)
- To place a node inside a group, set the child node's `parentId` to the group's `id`
- Child node `position` is relative to the group's top-left corner (not the canvas origin)
- The `name` field on group nodes is not validated (can be empty or omitted)
### Example
```json
{
"nodes": [
{
"id": "group-1",
"type": "group",
"name": "",
"position": { "x": 100, "y": 100 },
"style": { "width": 400, "height": 300 },
"data": { "label": "Data Processing" }
},
{
"id": "node-1",
"type": "subAgent",
"name": "fetch-data",
"parentId": "group-1",
"position": { "x": 50, "y": 50 },
"data": { "description": "Fetch data from API", "outputPorts": 1 }
}
]
}
```Jiraチケットの要件とConfluenceの関連ドキュメントを基に、Frontend/Backend/Infrastructureに分割した実装計画を策定するプランニングスキル。Jiraチケット情報とConfluence検索結果が前段で取得済みであることを前提とし、構造化された実装計画を出力する。「プランニング」「実装計画策定」「タスク分割」などの文脈で使用。
Analyze PR review comments from a GitHub PR URL. Fetch review comments, verify each finding against the actual codebase, assess validity (correct/incorrect/partial), present a structured summary with recommended actions, and optionally reply to each comment on GitHub. Use when given a PR review URL or when asked to check/analyze PR feedback.
Clean up merged feature branches after PR to main is merged. Use when the user says "ブランチ削除", "cleanup", "マージ後の片付け", or wants to delete a merged branch.
Create a PR to the main branch for feature/fix changes in this pnpm + Changesets monorepo. Use when the user says "PRを作成", "mainにPR", or wants to submit changes for review. Always run this in the monorepo-aware way — identify the affected package(s) and make sure a changeset exists, because the release pipeline is Changesets-driven.
Use when modifying `resources/workflow-schema.json` in cc-wf-studio to influence how AI agents generate workflows via the cc-workflow-ai-editor skill. Triggers include "AIが特定のノードタイプを選んでくれない", "ワークフロー生成のバイアスを調整したい", "スキーマの description を変えたい", "新しいノードタイプを追加したい", "嘘の制約がスキーマに混じっていないか確認したい". Covers what the schema actually does (instructions to AI, not runtime constraints), the design philosophy (align direction, do not prescribe rules), the build pipeline (.json → .toon auto-generated), and known bias sources to audit.
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.