skills.rest
hs3180
hs3180COMMUNITY
Explore all skills by this author →
GitHub

executor

...

3|3|Updated Jan 26, 2026
Search Tags:#automation#documentation#coding#tasks#execute#tests#execution-md
One-click install
npx skills add https://github.com/hs3180/disclaude --skill executor-hs3180
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: executor
Source: https://github.com/hs3180/disclaude/tree/main/skills/executor
Command: npx skills add https://github.com/hs3180/disclaude --skill executor-hs3180

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Executor Agent implements a disciplined workflow to turn Task.md requirements into concrete code changes and a formal execution summary, ensuring work is verifiable and traceable.

Core Features & Use Cases

  • Executes tasks based on Task.md requirements and guidance from Evaluator when available.
  • Creates an execution.md with a concise summary of changes, verification steps, and files touched.
  • Enforces a deterministic workflow: read Task.md, implement changes, run validations, and document results; adheres to the specified DO NOT rules for feedback or preemption.

Quick Start

Read Task.md, implement the required changes, and generate an execution.md summarizing the work.

Frequently Asked Questions about executor

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

FAQPage Schema
How do I automate coding tasks and generate verifiable execution reports?▼

To automate coding tasks and generate verifiable execution reports, implement features and fixes according to Task.md requirements, then generate an execution.md summarizing changes, verification steps, and files touched.

What is the best way to document iterative software development tasks with formal summaries?▼

Documenting iterative software development tasks requires generating an execution.md per iteration, providing an explicit, iteration-scoped summary of concrete code changes, validation results, and work artifacts.

How does an evaluator guide task execution and bug fixes in an iterative workflow?▼

An evaluator guides task execution and bug fixes by providing feedback within an iterative workflow, which the executor implements to produce concrete code changes and formal execution summaries while adhering to specified preemption rules.

Can I use this workflow to execute bug fixes without generating an execution.md file?▼

No, executing bug fixes within this workflow requires generating an execution.md per iteration to ensure work is verifiable and traceable, summarizing changes, validation steps, and files touched.

Do I need a Task.md file to start implementing features and fixes?▼

Yes, a Task.md file is required to start implementing features and fixes, acting as the source for task requirements that the deterministic workflow reads to execute changes and document results.

Why does my iterative development workflow need an iteration-scoped execution summary?▼

An iterative development workflow needs an iteration-scoped execution summary to satisfy requirements for performing concrete changes, validating results, and documenting work artifacts, ensuring traceability and verifiable outputs.

Related Skills

Explore More Software Engineering Skills→
FleronFleron
1

team-plan

Generate engineering implementation plans with tasks, dependencies, and assignments.

Community
Advanced
memorysavermemorysaver

openspec-verify-change

Verify implementation completeness against openspec delta spec artifacts.

Community
Advanced
backlinbacklin

testing

Automate unit and integration test execution for Python code.

Community
Intermediate
evandrodevbrevandrodevbr
1

openspec-verify-change

Verify software implementations against OpenSpec change specifications and artifacts.

Community
Advanced