원클릭으로
executor
Use when a PLAN.md file exists and requires execution to implement tasks atomically with commits.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Use when a PLAN.md file exists and requires execution to implement tasks atomically with commits.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when Ground Truth alignment finds memory contamination and the user explicitly requests scoped cleanup with /cleanse.
Use when registering, reviewing, merging, or rebuilding HXSK glossary term definitions after glossary-detect suggests a candidate or the user invokes /define.
Use when staged changes exist requiring qlty checks, logical split detection, or HXSK phase-scoped conventional commit creation.
Use when validating code for circular imports, layer violations, or design doc logic errors before merging architecture-level changes.
Use when .hxsk/.bootstrap-version is missing (fresh install) or exists (verify/update) to initialize HExoskeleton.
Use when shell scripts need linting/formatting before execution or commit to ensure code quality.
| allowed-tools | ["Read","Write","Edit","Bash","Grep","Glob"] |
| description | Use when a PLAN.md file exists and requires execution to implement tasks atomically with commits. |
| name | executor |
| trigger | 플랜 실행, 계획 실행, PLAN.md 실행, execute plan, start implementation, PLAN.md 실행하기, plan execute, run plan, implement plan, task 실행, atomic execution, plan carry out, 작업 시작, plan run, execute tasks, commit tasks, start plan execution, plan 구현 |
feat({phase}-{plan}): {task})| Step | Action | Detail |
|---|---|---|
| 1 | Load Project State | cat .hxsk/STATE.md — parse phase/plan/status |
| 2 | Load Plan | Parse frontmatter, objective, tasks, success criteria |
| 3 | Determine Pattern | A=autonomous, B=checkpoints, C=continuation, D=parallel wave |
| 4 | Execute Tasks | auto→work+verify+commit; checkpoint→STOP |
| 5 | Handle Deviations | Rule 1-3=auto-fix; Rule 4=checkpoint |
| 6 | Commit Tasks | One task = one commit (see commit protocol) |
| 7 | Create SUMMARY.md | .hxsk/phases/{N}/{plan}-SUMMARY.md |
| 8 | Store Memory | md-store-memory.sh execution-summary |
상세 흐름 → references/execution-flow.md
cross_phase_invariants.inherit + new 필드를 읽어 내재화.
실행 중 코드/로직이 이 조건을 위반하면 → 즉시 Rule 4 (아키텍처 체크포인트) 적용.
위반 신호:
| Rule | Trigger | Action |
|---|---|---|
| Rule 1 | Bug / wrong behavior | Auto-fix + track |
| Rule 2 | Missing critical functionality | Auto-add + track |
| Rule 3 | Blocking issue | Auto-fix blocker + continue |
| Rule 4 | Architectural change needed | STOP → checkpoint |
Priority: Rule 4 first. If unsure → Rule 4.
상세 규칙 + Deviation Memory + Authentication Gates → references/deviation-rules.md
Types: human-verify (90%) · decision (9%) · human-action (1%)
When checkpoint hit: STOP immediately. Return structured message.
Return format + Continuation Handling → references/checkpoint-protocol.md
git add -A && git commit -m "feat({phase}-{plan}): {task}"
SUMMARY.md → .hxsk/phases/{N}/{plan}-SUMMARY.md
Memory → md-store-memory.sh "Plan {phase}-{plan} Summary" ...
전체 프로토콜 (Phase Checkpoint, PRD Update, SUMMARY format, Anti-Patterns, 관련스킬, 네이티브도구) → references/commit-protocol.md
NO EXECUTION WITHOUT STATE AND PLAN LOADING FIRST NO ARCHITECTURAL CHANGE WITHOUT CHECKPOINT FIRST NO TASK COMPLETION WITHOUT ATOMIC COMMIT FIRST NO CONTINUATION WITHOUT CHECKPOINT HANDLING FIRST NO CODE LOGIC VIOLATION WITHOUT ARCHITECTURAL CHECKPOINT FIRST NO SUMMARY GENERATION WITHOUT TASK EXECUTION FIRST