メニュー
Generate Root Cause Analysis (RCA) for bugs using TDD methodology. Use when analyzing bug reports.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Produce a concrete implementation plan for a standalone Task or Epic takeover ticket. Use when a Jira Task/Epic is approved for Task Takeover planning and needs target files, implementation steps, tests, and repository scope.
Read-only qualitative review for Task Takeover implementations before PR creation. Use after task takeover execution completes.
Decompose a Technical Specification into implementable Epics with technical plans. Use when asked to break down features, create epics, or plan implementation.
Break down Epic implementation plans into concrete, actionable Tasks. Use when decomposing Epics into implementation units.
Implement code changes according to Task specifications. Use when executing implementation Tasks.
Produce a concrete implementation plan for a bug fix from an approved RCA and selected fix approach. Use when the team has selected a fix option and needs a detailed plan before implementation.
| name | analyze-bug |
| description | Generate Root Cause Analysis (RCA) for bugs using TDD methodology. Use when analyzing bug reports. |
Analyze bugs and generate Root Cause Analysis with TDD fix approach.
## Summary
[One paragraph bug summary]
## Root Cause Analysis
### Symptoms
- [Observable symptom 1]
- [Observable symptom 2]
### Affected Components
- [Component 1]: [How affected]
- [Component 2]: [How affected]
### Root Cause
[Detailed explanation of what went wrong and why]
### Chain of Events
1. [Initial trigger]
2. [Subsequent effect]
3. [Eventual failure]
## Proposed Fix (TDD Approach)
### Test First
Write tests that:
1. [Test case 1 - reproduces the bug]
2. [Test case 2 - verifies correct behavior]
### Implementation
[Description of the fix approach]
### Verification
[How to verify the fix is complete]
## Prevention
[How to prevent similar bugs in the future]