Skill

execute

Use when the user wants to execute tasks autonomously, run compounder on a tasks.md file, start autonomous development, compound through a task list, or implement tasks iteratively. Guides autonomous task execution using compound loops.

Install

npx claudepluginhub jero2rome/compounder --plugin compounder

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Orchestrates autonomous task execution using compounder's iterative loop mechanism.

SKILL.md

Similar Skills

cache-components

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

139.1k

claude-opus-4-5-migration

2 files

Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.

claude-opus-4-5-migration

83.2k

claude-code-plugin-release

1 file

Automates semantic versioning and release workflow for Claude Code plugins: bumps versions in package.json, marketplace.json, plugin.json; verifies builds; creates git tags, GitHub releases, changelogs.

claude-mem

64.7k

Stats

Stars0

Forks0

Last CommitJan 6, 2026

Actions

View Source View Plugin View on GitHub View README

Execute Skill

Orchestrates autonomous task execution using compounder's iterative loop mechanism.

Quick Start

When user has tasks ready for autonomous execution:

/compounder:compound-loop "Execute tasks from tasks.md. Mark completed with [X]. Run tests after each." --max-iterations 20 --completion-promise "ALL_TASKS_COMPLETE"

Phase Detection

Before starting, detect project state:

Check for tasks.md: Look for tasks.md, .specify/specs/*/tasks.md, or similar
- If found with - [ ] uncompleted tasks: Ready for execution
- Count tasks to estimate iterations (2-3 per task)
Check for plan.md/spec.md: If no tasks.md exists
- Guide user to create tasks first (manually or via speckit)

Launching Compounder

Calculate Parameters

iterations = (uncompleted_tasks * 2) + 5  # buffer for debugging
completion_promise = "ALL_TASKS_COMPLETE" or custom from user

Prompt Template

Build a prompt that:

References the tasks file explicitly
Instructs to follow task order (phases if present)
Mark tasks [X] as completed
Run verification after each task
Output <promise>COMPLETION</promise> only when truly done

Example Invocations

For a tasks.md with 10 tasks:

/compounder:compound-loop "Execute all tasks in tasks.md following TDD. After each task: mark [X], run tests. When ALL tasks complete and tests pass, output <promise>ALL_TASKS_COMPLETE</promise>" --max-iterations 25 --completion-promise "ALL_TASKS_COMPLETE"

For a single complex task:

/compounder:run-task "Implement user authentication" --iterations 10 --done-when "AUTH_WORKING"

Speckit Integration

If speckit commands are available in the project:

Phase	Command	Output
Specify	`/speckit.specify`	spec.md
Plan	`/speckit.plan`	plan.md
Tasks	`/speckit.tasks`	tasks.md
Execute	`/compounder:compound-loop`	Implementation

Completion Signals

The compound loop ends when:

<promise>COMPLETION_PROMISE</promise> is output (and TRUE)
Max iterations reached
/compounder:cancel-compound is run

Monitoring Progress

# Check current iteration
head -10 .claude/compounder-*.local.md

# View task completion
grep -E "^\- \[.\]" tasks.md