jira-driven-planning
This Jira-driven planning skill transforms Jira ticket requirements and Confluence documentation into structured implementation roadmaps organized across Frontend, Backend, and Infrastructure domains. Use it when you need to break down project requirements into actionable task divisions, establish technical approaches with architectural justification, identify dependencies and blockers, and surface risks with mitigation strategies. The skill assumes Jira ticket metadata and relevant Confluence documents have already been retrieved upstream.
git clone --depth 1 https://github.com/breaking-brake/cc-wf-studio /tmp/jira-driven-planning && cp -r /tmp/jira-driven-planning/.claude/skills/jira-driven-planning ~/.claude/skills/jira-driven-planningSKILL.md
# Jira Driven Planning Jiraチケットの要件とConfluenceの関連ドキュメントを入力として、Frontend / Backend / Infrastructure に分割した実装計画を策定する。 ## Workflow 1. 前段で取得されたJiraチケット情報（タイトル、説明、受け入れ基準、優先度）を確認 2. 前段で取得されたConfluenceドキュメント（設計書、仕様書、アーキテクチャ図）を確認 3. [planning-template.md](references/planning-template.md) に従って実装計画を策定 4. 計画をユーザーに提示し、レビューを依頼 ## Output Requirements - 要件サマリーは箇条書きで簡潔に - 技術的アプローチはアーキテクチャ判断の根拠を含める - タスク分割は Frontend / Backend / Infrastructure の3軸で整理 - 依存関係はブロッカーを明示 - リスクは重大度と対策をセットで記載 ## Constraints - 既存のコードベースやアーキテクチャパターンを尊重する - 不明確な要件がある場合はユーザーに確認を求める - 過度に詳細な実装レベルまで踏み込まず、計画レベルに留める
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.
AI workflow editor for CC Workflow Studio. Create and edit visual AI agent workflows through interactive conversation using MCP tools (get_workflow_schema, get_current_workflow, apply_workflow, update_nodes). Use when the user wants to create a new workflow, modify an existing workflow, or edit the workflow canvas in CC Workflow Studio via the built-in MCP server.
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.