Skip to content

breaking-brake/cc-wf-studio / .claude/skills/jira-driven-planning

jira-driven-planning

Verified

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

FileKindSize
SKILL.mdskill md1.6 KB
references/planning-template.mdmarkdown1.4 KB

references/planning-template.md

View on GitHub
# Planning Template

## Input Context

The planner receives:
- **Jira ticket**: Title, description, acceptance criteria, priority, labels, linked issues
- **Confluence docs**: Related design documents, architecture specs, API docs, existing patterns

## Planning Output Structure

### 1. Requirements Summary
- Restate ticket requirements in clear, actionable terms
- Identify acceptance criteria
- Note any ambiguities requiring clarification

### 2. Technical Approach
- Architecture decisions and rationale
- Technology/library selections
- Integration points with existing systems
- Data model changes (if any)

### 3. Task Breakdown

#### Frontend Tasks
- UI components to create/modify
- State management changes
- API integration points
- Responsive/accessibility considerations

#### Backend Tasks
- API endpoints to create/modify
- Business logic implementation
- Database schema/migration changes
- Validation and error handling

#### Infrastructure Tasks
- IaC definitions (Terraform, CDK, etc.)
- CI/CD pipeline changes
- Environment configuration
- Monitoring and alerting setup

### 4. Dependencies
- Inter-task dependencies (what blocks what)
- External dependencies (APIs, services, teams)
- Execution order recommendations

### 5. Risks and Mitigations
- Technical risks with severity assessment
- Mitigation strategies for each risk
- Fallback plans if primary approach fails
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall