메뉴
Diagnose and fix bugs with root-cause analysis and verification. Use when you have a concrete issue report, failing behavior, runtime error, or test regression that should be resolved safely. Stop and escalate to brainstorm when scope or risk grows.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Execute an approved implementation plan exactly and safely. Use for ExecPlan-style plan execution, resumable phase checklists, multi-hour implementation work, migrations, significant refactors, and plans that require verification checkpoints, status tracking, and final reporting.
Collaborative discovery and design framing for ambiguous or high-risk work. Use when requirements are unclear, multiple approaches are possible, or you need to turn an idea into a validated design brief before planning or coding.
Create detailed, execution-ready implementation plans for complex or high-risk changes without coding. Use for ExecPlan-style work, multi-hour changes, significant refactors, migrations, resumable phase checklists, and work that should be handed off to execute-plan with clear validation.
Create source-adjacent HTML visualizations for /visualize requests, docs, markdown, standardized plans, process flows, charts, Mermaid diagrams, context maps, and recommendation diagrams.
Structured clarification and requirements gathering through focused dialogue or with dry code. Use when a task is ambiguous, underspecified, or requires user input before any action can be taken. Do not plan or implement anything—only ask questions to collect the information needed.
Create or refresh project documentation in `docs/`. Use when a project needs docs initialized or existing docs synced to the current codebase.
| name | fix |
| description | Diagnose and fix bugs with root-cause analysis and verification. Use when you have a concrete issue report, failing behavior, runtime error, or test regression that should be resolved safely. Stop and escalate to brainstorm when scope or risk grows. |
| argument-hint | [bug report or issue description] |
| license | MIT |
Use this skill only when all conditions below are true:
Concrete issue signal exists
Likely localized fix path
Low-to-moderate architectural risk
Straightforward verification path
If any condition fails, escalate to brainstorm or write-plan.
Immediately stop and switch to planning if any of these occur:
Escalation action:
brainstorm or write-plan first to define phased diagnosis, implementation, and risk controls."docs/SUMMARY.md exists, read it first.Code Standard docs for implementation conventions.Guidelines:
Classify the work before coding:
Most are true:
brainstorm or write-plan)Any are true:
If it is a bigger fix, follow Hard Stop Escalation Criteria.
Run validation in increasing scope:
Fix is complete only when:
If verification indicates broader impact, escalate to brainstorm or write-plan.
Provide a concise completion report with:
If behavior or documentation-relevant rules changed, update the minimal relevant docs. If architecture changed, this should have been escalated.
Use when the report is incomplete: