Menu
Re-perform a root cause analysis after receiving feedback from the engineering team. Use when the team has reviewed an RCA and requested changes.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | regenerate-rca |
| description | Re-perform a root cause analysis after receiving feedback from the engineering team. Use when the team has reviewed an RCA and requested changes. |
You have previously investigated this bug and produced an RCA. The engineering team has reviewed it and provided feedback. Your job is to address every point in the feedback, then write an updated RCA.
Re-examine the code in light of the feedback. If the feedback identifies a missed hypothesis, investigate it. If it flags a wrong file location, find the correct one. If it questions your confidence level, gather more evidence.
Do not discard valid findings from your original RCA that the feedback did not challenge. Carry those forward.
Update introduced_in if the feedback suggests the commit attribution was wrong or uncertain. Use git blame and git log to confirm.
Revise your fix options if the feedback identifies missing alternatives or options that are too similar.
Write the updated output to .forge/rca.json using exactly the same schema as the original. All top-level keys are required.
The schema:
{
"summary": "...",
"code_location": {"file": "...", "function": "...", "line_range": "..."},
"mechanism": "...",
"trigger_to_symptom": "...",
"hypothesis_log": [{"candidate": "...", "evidence": "...", "verdict": "accepted|rejected", "reason": "..."}],
"introduced_in": {"commit": "...", "pr": "...", "date": "..."},
"confidence": {"level": "High|Medium|Low", "percentage": 0, "rationale": "..."},
"options": [{"title": "...", "description": "...", "tradeoffs": "..."}],
"reproducibility": {"feasible": true, "test_source": "...", "conditions": "..."}
}
Do not write any other files. Do not make any commits.
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.