rccafp
/rccafp
Root Cause, Corrective Action, and Future Proofing - incident management protocol for multi-agent AI systems. Triggers on incidents, system failures, constraint violations, LLM overreach, or post-mortem analysis.
- Author
- elevanaltd ↗
- Repository
- HestAI-MCP ↗
- Licence
- Apache-2.0
- Last repository change
- 30.09.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 30.09.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Root Cause, Corrective Action, and Future Proofing - incident management protocol for multi-agent AI systems. Triggers on incidents, system failures, constraint violations, LLM overreach, or post-mortem analysis.
Original author description
Root Cause, Corrective Action, and Future Proofing - incident management protocol for multi-agent AI systems. Triggers on incidents, system failures, constraint violations, LLM overreach, or post-mortem analysis.
How it works
- When to Use
- Five-Phase Process
- Agent Roles in RCCAFP
- Synthesis Gate
- Anti-Patterns
- Success Metrics
SKILL.md preview
--- name: rccafp description: Root Cause, Corrective Action, and Future Proofing - incident management protocol for multi-agent AI systems. Triggers on incidents, system failures, constraint violations, LLM overreach, or post-mortem analysis. allowed-tools: [Read, Write, Edit, Grep, Glob, Bash, Task, TodoWrite, AskUserQuestion] --- # RCCAFP - Root Cause, Corrective Action, and Future Proofing Structured 5-phase incident management protocol for multi-agent AI systems with human orchestration oversight. ## When to Use Trigger RCCAFP when: - A system constraint violation is detected - An agent operates outside its role boundaries (overreach) - A production failure or regression occurs - A constitutional principle (I1-I6) is violated - An assumption cascade causes unexpected behavior - Post-mortem analysis is requested ## Five-Phase Process ### Phase 1: Detection and Triage 1. Create incident directory: `.hestai/state/incidents/YYYYMMDD-[incident-name]/` 2. Create subdirectories: `01-root-cause/`, `02-corrective-action/`, `03-future-proof/` 3. Document initial symptoms and severity assessment 4. Determine if full RCCAFP is warranted vs minor fix ### Phase 2: Root Cause Investigation 1. Collect evidence: exact causality chains, artifacts, logs 2. Cross-validate through multi-agent assessment 3. Document in `01-root-cause/causality-chain.md` 4. Identify which system boundaries were violated ### Phase 3: Corrective Action 1. Immediate containment and mitigation 2. Constraint validation - identify gaps in existing boundaries 3. Execute triage and damage control 4. Document in `02-corrective-action/constraint-validations.md` and `triage-execution.md` ### Phase 4: Future Proofing 1. Extract architectural learnings from the incident 2. Design prevention mechanisms with evidence 3. Define monitoring requirements 4. Document in `03-future-proof/prevention-mechanisms.md` ### Phase 5: Closure and Integration 1. Verify all phases are complete and documented 2. Pass findings through synthesis gate before integration 3. Update system documentation only after review 4. Refine protocol based on learnings ## Agent Roles in RCCAFP | Agent | RCCAFP Role | |-------|-------------| | Holistic Orchestrator | Orchestrates process, owns gap accountability | | Critical Engineer | Leads root cause investigation (tactical) | | Principal Engineer | Leads future proofing (strategic prevention) | | Implementation Lead | Executes corrective action implementations | | Requirements Steward | Validates learnings against North Star | ## Synthesis Gate All incident learnings must pass through the synthesis gate before being promoted to governance documentation: - Findings go to `.hestai/state/incidents/pending/` - Review validates evidence quality and relevance - Only validated learnings are integrated into system docs ## Anti-Patterns - **Silent Fix**: Fixing without documenting root cause - **Skip Synthesis**: Promoting learnings without gate review - **Blame Cascade**: Attributing to agents rather than system gaps - **Speculative Prevention**: Creating mechanisms without evidence - **Scope Creep**: Expanding response beyond the specific failure ## Success Metrics - Mean Time to Detection (MTTD) - Mean Time to Containment (MTTC) - Documentation completeness - Constraint validation effectiveness - Incident recurrence rate - Architecture improvement rate
Versions
The database has no other skills named rccafp.
Database snapshot: 13.11.2026 · package version 38788fde3612 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100debrief
Produces a structured post-incident analysis — timeline, root cause, and actionable follow-ups — while context is fresh. Use when the user says "debrief", "post-mortem", "incident review", or "root cause analysis". - 100agent-protocol
Design AI agent communication protocols: MCP tool schemas, A2A, function calling, and inter- agent messaging. Use when building multi-agent systems, defining tool interfaces, or implementing agent-to-agent communication. - 100a2a-testing
Test A2A implementations — unit tests, integration tests, mock agents, protocol conformance, and end-to-end multi-agent testing. Use when building test suites for A2A servers, clients, or multi-agent systems. - 100kaizen-why
Root cause analysis for incidents, defects, recurring bugs, customer complaints and process failures: 5 whys checked against facts, a fishbone when causes are many, and corrective plus preventive actions (8D style). Use when something went wrong or keeps going wrong, and when… - 100post-incident-root-cause-analysis-reporting
Use this skill when document incident timelines, root causes, business impact, and preventative recommendations. - 95incident
Guide incident response, root cause analysis, and post-mortem documentation. Use when: production incident, outage response, post-mortem writing, RCA. Not for: designing retries and checkpoints before failure — use /durable; setting alert thresholds and Error Budget policy — use…