executor

Execute HXSK plans with atomic Git commits and STATE.md tracking.

2|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/SukbeomH/HExoskeleton --skill executor-sukbeomh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: executor
Source: https://github.com/SukbeomH/HExoskeleton/tree/main/.claude/skills/executor
Command: npx skills add https://github.com/SukbeomH/HExoskeleton --skill executor-sukbeomh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires scripts/md-store-memory.sh, scripts/detect-language.sh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the execution of project plans, ensuring tasks are completed atomically with proper version control, deviations are handled, and project state is consistently managed.

Core Features & Use Cases

  • Atomic Task Execution: Executes tasks defined in a plan one by one, creating a separate Git commit for each.
  • Deviation Handling: Automatically fixes bugs, adds missing critical functionality, or resolves blocking issues based on predefined rules. Escalates architectural changes for user approval.
  • Checkpointing & State Management: Pauses execution at defined checkpoints for verification or decisions, and maintains project state via STATE.md.
  • Use Case: A developer can use this Skill to execute a complex feature implementation plan. The Skill will automatically commit each sub-task, fix minor bugs encountered, and pause if a significant architectural change is needed, allowing the developer to review and approve before proceeding.

Quick Start

Execute the current plan by running the executor skill.

Frequently Asked Questions about executor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate project plan execution with atomic Git commits?

Automating project plan execution with atomic Git commits is done by parsing PLAN.md, executing tasks sequentially, and creating a separate Git commit for each completed task to ensure version control integrity.

How does deviation handling work when executing a development plan?

Deviation handling during plan execution automatically fixes bugs, adds missing critical functionality, and resolves blocking issues, while escalating significant architectural changes for user approval before proceeding.

What is a checkpoint protocol in state management for task execution?

A checkpoint protocol in state management pauses task execution at predefined points for human verification, user decisions, or manual actions, tracking the current progress via STATE.md before resuming.

Do I need a PLAN.md file to manage state and execute tasks?

Yes, you need a PLAN.md file to define tasks for execution and a STATE.md file to maintain project state, as the execution flow sequentially parses the plan and records progress.

When should I escalate architectural changes during plan execution?

You should escalate architectural changes during plan execution when a deviation requires structural modifications beyond bug fixes or critical functionality additions, pausing execution to request explicit user approval.