Skip to content
cccskills
FreePublished on GitHub

jira-driven-planning

Turn previously retrieved Jira requirements and Confluence documents into a structured implementation plan. Tasks are grouped into frontend, backend, and infrastructure work, with architectural reasoning, blocking dependencies, and risks paired with mitigation measures.

OriginalShow the original description

Jiraチケットの要件とConfluenceの関連ドキュメントを基に、Frontend/Backend/Infrastructureに分割した実装計画を策定するプランニングスキル。Jiraチケット情報とConfluence検索結果が前段で取得済みであることを前提とし、構造化された実装計画を出力する。

「プランニング」「実装計画策定」「タスク分割」などの文脈で使用。

Works withConfluenceJira
See how to install

Good for

  • Creating an implementation plan from Jira requirements
  • Dividing work across frontend, backend, and infrastructure
  • Identifying blocking dependencies between tasks
  • Preparing risks and mitigations for plan review

Files included (2)

  • SKILL.md1.6 KB
  • references/planning-template.md1.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Jira Driven Planning

Jiraチケットの要件とConfluenceの関連ドキュメントを入力として、Frontend / Backend / Infrastructure に分割した実装計画を策定する。

Workflow

  1. 前段で取得されたJiraチケット情報(タイトル、説明、受け入れ基準、優先度)を確認
  2. 前段で取得されたConfluenceドキュメント(設計書、仕様書、アーキテクチャ図)を確認
  3. planning-template.md に従って実装計画を策定
  4. 計画をユーザーに提示し、レビューを依頼

Output Requirements

  • 要件サマリーは箇条書きで簡潔に
  • 技術的アプローチはアーキテクチャ判断の根拠を含める
  • タスク分割は Frontend / Backend / Infrastructure の3軸で整理
  • 依存関係はブロッカーを明示
  • リスクは重大度と対策をセットで記載

Constraints

  • 既存のコードベースやアーキテクチャパターンを尊重する
  • 不明確な要件がある場合はユーザーに確認を求める
  • 過度に詳細な実装レベルまで踏み込まず、計画レベルに留める

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Create and edit visual AI agent workflows in CC Workflow Studio through conversation. Add or remove steps and connections, update individual nodes, and organize related steps into visual groups on the canvas.

  • Creating a new AI agent workflow
  • Adding or removing steps and connections
  • Updating node names, settings, or positions
breaking-brake/cc-wf-studio5.4KUpdated Oct 7, 2026

ccwf-cli

FreeSummary

Use ccwf to validate workflow JSON files, preview their steps in a browser, and produce Mermaid flowcharts. Export workflows as skill files for supported agents, or generate the files and launch Claude Code to proceed with execution.

  • Previewing a workflow in a browser
  • Validating hand-edited or AI-generated workflow JSON
  • Sharing workflow steps as Markdown or Mermaid diagrams
breaking-brake/cc-wf-studio5.4KUpdated Oct 7, 2026

next-idea

FreeSummary

Develop user-visible improvements for cc-wf-studio, verify their basis in the code, and assess their value. Record qualifying proposals as locked GitHub issues, creating a queue of concrete ideas for later implementation without changing code.

  • Proposing improvements users would notice
  • Checking ideas against code and existing proposals
  • Preparing an implementation queue
breaking-brake/cc-wf-studio5.4KUpdated Oct 7, 2026

next-qa

FreeSummary

Advance one queued QA task by adding tests or test tooling, recording the work, and opening a pull request. The skill also manages its in-flight QA requests and merges into auto-qa after CI passes.

  • Implementing a queued unit or regression test
  • Setting up test infrastructure and CI checks
  • Checking and advancing an in-flight QA pull request
breaking-brake/cc-wf-studio5.4KUpdated Oct 7, 2026

next-qa-idea

FreeSummary

Find a valuable gap in test coverage by checking code, existing tests, and QA priorities. The skill creates at most one locked GitHub issue with concrete test cases, ready for later implementation.

  • Finding past bugs that lack regression tests
  • Reviewing recent changes for untested behavior
  • Preparing a QA backlog without implementing tests
breaking-brake/cc-wf-studio5.4KUpdated Oct 7, 2026

next-task

FreeSummary

Advance one development task by managing an existing pull request, fixing a build failure or bug, or implementing a queued idea. Record the work and integrate changes into auto-dev only after automated checks pass.

  • Implementing one queued idea
  • Continuing work on an open pull request
  • Fixing failed checks or reported bugs
breaking-brake/cc-wf-studio5.4KUpdated Oct 7, 2026

See all skills by breaking-brake

Report a problem with this skill