Jiraチケットの要件とConfluenceの関連ドキュメントを基に、Frontend/Backend/Infrastructureに分割した実装計画を策定するプランニングスキル。Jiraチケット情報とConfluence検索結果が前段で取得済みであることを前提とし、構造化された実装計画を出力する。「プランニング」「実装計画策定」「タスク分割」などの文脈で使用。
next-qa-idea
next-qa-idea is an open-source workflow skill for Claude Code and compatible agents, published by breaking-brake. Its author describes it as: “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…”. 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/next-qa-idea`.
What next-qa-idea does
One invocation = one ideation iteration: **orient → find gaps → judge → file ONE issue**. This skill NEVER writes code, tests, or configuration — it only fills the `qa` queue that the `next-qa` skill consumes. The split mirrors the feature track (`next-idea` / `next-task`) so ideation and implementation can run on separate schedules.
Installation
Add next-qa-idea to your agent with:
git clone https://github.com/breaking-brake/cc-wf-studio ~/.claude/skills/next-qa-ideaAlways 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 next-qa-idea is organised into these sections:
- 1. Orient (read-only)
- 2. Find the gap
- 3. Judge — the QA value bar (ALL must hold)
- 4. File ONE issue
- Boundaries
When to use it
Reach for next-qa-idea when you want workflow help from your agent 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
- Actively maintained (recent commits)
Things to check
- No license declared — confirm terms with the author before reuse
Topics
Frequently asked questions
- What does next-qa-idea do?
- 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.
- How do I install next-qa-idea?
- Run git clone https://github.com/breaking-brake/cc-wf-studio ~/.claude/skills/next-qa-idea in your agent, then reload your skills. Review the source at https://github.com/breaking-brake/cc-wf-studio before installing.
- Is next-qa-idea free to use?
- next-qa-idea 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.
- Where does next-qa-idea come from?
- next-qa-idea 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 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.
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.