execute

Name: execute
Availability: InStock
Author: jdwalle

Orchestrates software lifecycle execution via task-implementer agents with phased checkpoints and artifact logging.

Updated Aug 23, 2026

Search Tags:#automation #verification #agent #lifecycle #execute #orchestrate #git-commit

Ready to run

npx skills add https://github.com/jdwalle/expedite-plugin --skill execute-jdwalle

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: execute
Source: https://github.com/jdwalle/expedite-plugin/tree/main/skills/execute
Command: npx skills add https://github.com/jdwalle/expedite-plugin --skill execute-jdwalle

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Coordinating end-to-end execution of a software lifecycle by dispatching task-implementer agents, tracking progress, and enforcing per-task verification ensures a traceable, auditable workflow from scope to completion.

Core Features & Use Cases

Orchestrates end-to-end execution by dispatching task-implementer agents for each plan task.
Supports spike vs unspiked task modes, per-task verification, and per-phase checkpoints.
Tracks state via .expedite/state.yml, PROGRESS.md, and per-phase PROGRESS files, enabling auditability.
Integrates optional Git commits to preserve changes when verification passes.
Provides a structured interaction model with micro-interactions and robust error handling.

Quick Start

Begin the Expedite lifecycle with /expedite:scope and progress through /expedite:research, /expedite:design, /expedite:plan, /expedite:spike, and /expedite:execute.

Frequently Asked Questions about execute

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

FAQPage Schema

How do I automate end-to-end software lifecycle execution with task tracking and verification?▼

Automated lifecycle execution dispatches per-task implementer agents, tracks progress via state files, and enforces per-task verification to ensure a traceable workflow from scope to completion.

What is the best way to orchestrate plan execution with phase checkpoints and artifact logging?▼

Orchestrating plan execution involves dispatching task-implementer agents for each plan task, enforcing per-phase checkpoints, and logging artifacts to maintain auditability throughout the software lifecycle.

Can I integrate automated git commits into my plan execution workflow when verification passes?▼

Yes, you can integrate optional Git commits into the workflow to automatically preserve changes when per-task verification passes, ensuring traceable progress from design to implementation.

How does per-task verification work when dispatching implementer agents?▼

Per-task verification works by dispatching implementer agents for individual tasks and enforcing checkpoints after each one, ensuring evidence and implementation traceability before moving to the next phase.

Do I need to complete scope and design phases before starting automated plan execution?▼

Yes, automated execution follows a structured lifecycle beginning with scope, then research, design, plan, and optional spike phases, ensuring the design evolves properly before final execution begins.

What are the limitations of using automated orchestration for software lifecycle tasks?▼

Automated orchestration requires a structured lifecycle progression through scope, research, design, and plan phases beforehand, and relies on state tracking files like state.yml and PROGRESS.md for auditability.