메뉴
Use when the user asks for a behavior-preserving refactor plan before implementation. Do not trigger when the user already requested a clear, scoped refactor to be implemented directly.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use only when the user explicitly invokes this skill to map unresolved product, domain, repository, or delivery unknowns before choosing a path.
Use only when the user explicitly invokes this skill to create or resume a persistent file-based goal tracker across sessions.
Use only when the user explicitly invokes this skill to stress-test an existing plan or design through one load-bearing question at a time.
Use only when the user explicitly invokes this skill to evaluate a skill with representative cases, isolated runs, independent judging, and evidence-driven edits.
Use for a concrete defect or regression that needs reproduction, root-cause diagnosis, a fix, and regression validation. Do not trigger for routine localized edits or primarily performance-focused work.
Use when the requested feature genuinely spans at least two delivery layers such as frontend, backend, API, data, scripts, or tests. Do not expand a single-layer change into a full-stack workflow.
| name | dev-refactor-plan |
| description | Use when the user asks for a behavior-preserving refactor plan before implementation. Do not trigger when the user already requested a clear, scoped refactor to be implemented directly. |
| metadata | {"version":"0.5","updated":"2026-07-26"} |
Use this workflow when the task is to refactor code while preserving behavior.
State the refactor goal.
Map current structure.
Identify contracts.
$codex-next:core-grilling and stop. Wait for the user to invoke it
explicitly; do not imitate or begin that workflow here.Propose an incremental plan.
Define rollback and stop conditions.
Return: