Akb Ingest
dnotitia/akb
Ingest whatever you point at into an AKB vault — a local file, a web URL, a GitHub PR/release/commit, a Confluence page, or a Jira issue.
Jiraチケットの要件とConfluenceの関連ドキュメントを基に、Frontend/Backend/Infrastructureに分割した実装計画を策定するプランニングスキル。Jiraチケット情報とConfluence検索結果が前段で取得済みであることを前提とし、構造化された実装計画を出力する。「プランニング」「実装計画策定」「タスク分割」などの文脈で使用。
Install Jira Driven Planning
$ npx skills add breaking-brake/cc-wf-studio --skill jira-driven-planning -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install breaking-brake/cc-wf-studio jira-driven-planning --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/breaking-brake/cc-wf-studio.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/jira-driven-planning .claude/skills/jira-driven-planning && rm -rf skills-srcUse ~/.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/
Install the "jira-driven-planning" agent skill from https://github.com/breaking-brake/cc-wf-studio/tree/main/.claude/skills/jira-driven-planning into .claude/skills/jira-driven-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jira-driven-planning", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/breaking-brake/cc-wf-studio/tree/main/.claude/skills/jira-driven-planningType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add breaking-brake/cc-wf-studio --skill jira-driven-planning -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install breaking-brake/cc-wf-studio jira-driven-planning --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/breaking-brake/cc-wf-studio.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/jira-driven-planning .agents/skills/jira-driven-planning && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "jira-driven-planning" agent skill from https://github.com/breaking-brake/cc-wf-studio/tree/main/.claude/skills/jira-driven-planning into .agents/skills/jira-driven-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jira-driven-planning", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add breaking-brake/cc-wf-studio --skill jira-driven-planning -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install breaking-brake/cc-wf-studio jira-driven-planning --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/breaking-brake/cc-wf-studio.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/jira-driven-planning .cursor/skills/jira-driven-planning && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "jira-driven-planning" agent skill from https://github.com/breaking-brake/cc-wf-studio/tree/main/.claude/skills/jira-driven-planning into .cursor/skills/jira-driven-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jira-driven-planning", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/breaking-brake/cc-wf-studio.git --path .claude/skills/jira-driven-planning--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add breaking-brake/cc-wf-studio --skill jira-driven-planning -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install breaking-brake/cc-wf-studio jira-driven-planning --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/breaking-brake/cc-wf-studio.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/jira-driven-planning .gemini/skills/jira-driven-planning && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "jira-driven-planning" agent skill from https://github.com/breaking-brake/cc-wf-studio/tree/main/.claude/skills/jira-driven-planning into .gemini/skills/jira-driven-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jira-driven-planning", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install breaking-brake/cc-wf-studio jira-driven-planningInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add breaking-brake/cc-wf-studio --skill jira-driven-planning -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/breaking-brake/cc-wf-studio.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/jira-driven-planning .github/skills/jira-driven-planning && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "jira-driven-planning" agent skill from https://github.com/breaking-brake/cc-wf-studio/tree/main/.claude/skills/jira-driven-planning into .github/skills/jira-driven-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jira-driven-planning", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add breaking-brake/cc-wf-studio --skill jira-driven-planning -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install breaking-brake/cc-wf-studio jira-driven-planning --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/breaking-brake/cc-wf-studio.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/jira-driven-planning .opencode/skills/jira-driven-planning && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "jira-driven-planning" agent skill from https://github.com/breaking-brake/cc-wf-studio/tree/main/.claude/skills/jira-driven-planning into .opencode/skills/jira-driven-planning/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "jira-driven-planning", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
jira-driven-planning- GitHub stars
- 5.4k
- Token cost
- ~203 tokens
- SKILL.md length
- 32 words
- Files
- 2 (incl. references)
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Jiraチケットの要件とConfluenceの関連ドキュメントを基に、Frontend/Backend/Infrastructureに分割した実装計画を策定するプランニングスキル。Jiraチケット情報とConfluence検索結果が前段で取得済みであることを前提とし、構造化された実装計画を出力する。「プランニング」「実装計画策定」「タスク分割」などの文脈で使用。
- Works in 4 steps: 前段で取得されたJiraチケット情報（タイトル、説明、受け入れ基準、優先度）を確認 → 前段で取得されたConfluenceドキュメント（設計書、仕様書、アーキテクチャ図… → planning-template.md に従って実装計画を策定 → …
- Agent Workflows work in your project
- SKILL.md covers Workflow, Output Requirements and Constraints
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Jira Driven Planning is an agent skill from breaking-brake/cc-wf-studio. Jiraチケットの要件とConfluenceの関連ドキュメントを基に、Frontend/Backend/Infrastructureに分割した実装計画を策定するプランニングスキル。Jiraチケット情報とConfluence検索結果が前段で取得済みであることを前提とし、構造化された実装計画を出力する。「プランニング」「実装計画策定」「タスク分割」などの文脈で使用。
Its SKILL.md is about 200 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/planning-template.md`).
It sits in Agent Workflows. It works with Jira and Confluence.
When your agent uses it
- Agent Workflows work in your project
Example prompts
- “/jira-driven-planning”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- 前段で取得されたJiraチケット情報（タイトル、説明、受け入れ基準、優先度）を確認
- 前段で取得されたConfluenceドキュメント（設計書、仕様書、アーキテクチャ図）を確認
- planning-template.md に従って実装計画を策定
- 計画をユーザーに提示し、レビューを依頼
What it can do on your machine
Read from SKILL.md and the folder at commit a7bf24a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
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
Jira Driven Planning loads about 203 tokens when it runs, and up to ~552 if it reads all its reference files. Until then it costs about 51 tokens; SKILL.md has 32 words of instructions outside code blocks.
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 passed
The automated check found no risky patterns in SKILL.md.
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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 32 words (~203 tokens).
“Jiraチケットの要件とConfluenceの関連ドキュメントを入力として、Frontend / Backend / Infrastructure に分割した実装計画を策定する。”
- name
- jira-driven-planning
Files
SKILL.md and 1 other file (references) in .claude/skills/jira-driven-planning of breaking-brake/cc-wf-studio.
- SKILL.md
- references/planning-template.md
Open the folder on GitHubat commit a7bf24a
Compare with similar skills
Jira Driven Planning 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Jira Driven Planning this skillbreaking-brake/cc-wf-studio | 5.4k | — | ~203 | Automated safety check: Pass | Custom licence | |
| Akb Ingestdnotitia/akb | 162 | — | ~2k | Automated safety check: Pass | Custom licence | |
| Jira Assistanttech-leads-club/agent-skills | 7k | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| Plan Architecturecoleam00/skills | 674 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Prime Frontendcoleam00/skills | 674 | — | ~1k | Automated safety check: Pass | MIT | |
| Investigate To Confluencetestdouble/han | 279 | — | ~2.3k | Automated safety check: Pass | MIT |
Similar skills
Jira Assistant
tech-leads-club/agent-skills
Manage Jira issues via Atlassian MCP — search, create, update, transition status, and handle sprint tasks.
Plan Architecture
coleam00/skills
Interactively explore HOW to approach an intent (a PRD, epic, brief, or free-form idea) and decide the high-level architecture — the approach, stack, libraries, data shape, and risks the intent left…
Prime Frontend
coleam00/skills
Primes the agent with focused understanding of the frontend portion of the codebase — components, routing, state management, and styling — without loading unrelated backend code.
Investigate To Confluence
testdouble/han
Runs an evidence-based investigation of a bug, failure, or unexpected behavior with investigate and publishes the resulting investigation report to a user-specified Confluence location.
Atlassian Setup
davekilleen/Dex
Connect Jira and Confluence for project tracking and knowledge search.
More from breaking-brake/cc-wf-studio
All 11 skills in this repoCC Workflow Studio AI Editor
breaking-brake/cc-wf-studio
Creates and edits visual agent workflows in CC Workflow Studio through conversation, with the agent reading and writing the canvas over MCP.
PR Review Analysis
breaking-brake/cc-wf-studio
Fetches review comments from a GitHub pull request, checks each one against the real code, rates it valid, invalid or partial, and can reply on GitHub.
Workflow Schema Tuning
breaking-brake/cc-wf-studio
Guides edits to cc-wf-studio's workflow schema so AI agents generate better workflows, treating schema text as prompt engineering rather than validation.
Changesets Pull Request to Main
breaking-brake/cc-wf-studio
Opens a pull request to main in a pnpm and Changesets monorepo, after working out which packages changed and making sure a changeset file exists.
PR Merge Branch Cleanup
breaking-brake/cc-wf-studio
Clean up merged feature branches after PR to main is merged. Use when the user says "ブランチ削除", "cleanup", "マージ後の片付け", or wants to delete a merged branch.
ccwf Workflow CLI
breaking-brake/cc-wf-studio
Teaches the agent to use the ccwf command line tool to validate, preview, render, export and run cc-wf-studio workflow JSON files without opening VS Code.
Related
Works with
Categories
Questions about Jira Driven Planning
What does Jira Driven Planning do?
Jiraチケットの要件とConfluenceの関連ドキュメントを基に、Frontend/Backend/Infrastructureに分割した実装計画を策定するプランニングスキル。Jiraチケット情報とConfluence検索結果が前段で取得済みであることを前提とし、構造化された実装計画を出力する。「プランニング」「実装計画策定」「タスク分割」などの文脈で使用。. Jira Driven Planning is an agent skill from breaking-brake/cc-wf-studio.
When should I use Jira Driven Planning?
Jira Driven Planning fits situations like: agent Workflows work in your project.
How do I install Jira Driven Planning in Claude Code?
Run `npx skills add breaking-brake/cc-wf-studio --skill jira-driven-planning -a claude-code`. Or copy the skill folder (.claude/skills/jira-driven-planning in breaking-brake/cc-wf-studio) into .claude/skills/jira-driven-planning in your project. Claude Code loads it when a task matches its description.
How do I install Jira Driven Planning in Codex?
Run `npx skills add breaking-brake/cc-wf-studio --skill jira-driven-planning -a codex`. Or copy the skill folder (.claude/skills/jira-driven-planning in breaking-brake/cc-wf-studio) into .agents/skills/jira-driven-planning in your project. Codex loads it when a task matches its description.
Can I use Jira Driven Planning 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 breaking-brake/cc-wf-studio --skill jira-driven-planning -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/jira-driven-planning, .gemini/skills/jira-driven-planning, .github/skills/jira-driven-planning and .opencode/skills/jira-driven-planning in your project.
What does Jira Driven Planning need to run?
SKILL.md names no scripts, command-line tools or credentials: Jira Driven Planning is instructions for the agent only.
Does Jira Driven Planning 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 Jira Driven Planning safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Jira Driven Planning use?
Jira Driven Planning has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Jira Driven Planning use?
About 203 tokens (SKILL.md is roughly 812 characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 349 tokens, read only when the agent opens those files.
What are the alternatives to Jira Driven Planning?
Skills that share tags, products or a category with Jira Driven Planning: Akb Ingest (dnotitia/akb, 162 stars), Jira Assistant (tech-leads-club/agent-skills, 7k stars), Plan Architecture (coleam00/skills, 674 stars) and Prime Frontend (coleam00/skills, 674 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Jira Driven Planning?
breaking-brake (a GitHub user) maintains it in breaking-brake/cc-wf-studio, which has 5,394 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on October 7, 2026.
Source: breaking-brake/cc-wf-studio on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.