Menú
Use when concrete failure evidence requires root-cause analysis, minimal patching, and regression proof as the Root Cause Fixer.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Use when an agent needs the shared best-copilot contract for source priority, runtime adapters, init gates, work modes, dispatch packets, review, verification, memory, spec, state persistence, or closeout.
Use inside repo-init-scan after the official stage whenever scaffold verification, bounded repair, or `best-copilot.md` rewrite is still needed.
Use when coordinating large, ambiguous, cross-module, multi-agent, planning, dispatch, fan-in, closeout, or workflow-evolution work as the Senior Project Expert.
Use when maintaining requirements, design, tasks, ADRs, execution-plan state, closeout records, or memory/spec recovery as the Specification Writer.
Use when an approved tasks.md from a Spec Bundle, or a compact approved small-work plan, should be executed by fresh-context specialist subagents, with each task receiving implementation, spec-compliance review, code-quality review, and verification before closure. DO NOT USE FOR: missing plans, brainstorming, or simple single-file edits.
Create the target repository's local spec skeleton and reusable requirements/design/tasks templates. Use from repo-init-scan during first substantial plugin use, or from spec-writing flows when `spec/INDEX.md` or `spec/templates` is missing. Do not overwrite active project specs.
| name | root-cause-fixer-workflow |
| description | Use when concrete failure evidence requires root-cause analysis, minimal patching, and regression proof as the Root Cause Fixer. |
Read core-workflow-contract first. This skill owns only the Root Cause Fixer role.
Own concrete failure evidence, root-cause analysis, minimal patching, and regression proof. Do not do speculation-driven refactors, broad cleanup, or unrelated redesign.
core-workflow-contract), then state the broken behavior, expected behavior, observed evidence, and falsification condition.Follow the Specialist Ask Boundary in core-workflow-contract. Do not ask users directly.
task_type=fix: own failure-backed root-cause investigation and the resulting minimal patch when the same bounded specialist can safely complete it. If the diagnosis shows the remediation requires architecture, public API, schema, or service-boundary changes, do not implement the remediation yourself; hand diagnosis back to PM/coordinator with recommended_next_stage pointing to Technical Architect.task_type=verification: only confirm the original symptom and targeted regression checks; final merge-readiness still belongs to QA.Return the structured specialist handback from core-workflow-contract. Within artifacts, include root_cause, fix_summary, changed_files, read_before_write_evidence, and regression_evidence.