execute-plan

Execute one br epic task and generate the next actionable step.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/sQVe/cape --skill execute-plan-sqve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: execute-plan
Source: https://github.com/sQVe/cape/tree/main/skills/execute-plan
Command: npx skills add https://github.com/sQVe/cape --skill execute-plan-sqve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The next-task execution skill progresses a br epic by taking a single task through its execution loop, then returns control for review, enabling rapid, iterative advancement of planned work.

Core Features & Use Cases

  • One-task cadence: completes one epic task, reflects on learnings, and generates the next task.
  • Humans-in-the-loop by design: stops after each task until user confirmation.
  • Epics-driven workflow: loads epic context, executes, and creates the informed next step.

Quick Start

Load the current epic context, execute the next task, and present a checkpoint for review.

Frequently Asked Questions about execute-plan

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

FAQPage Schema
How do I execute the next task in an epic workflow?

To execute the next task in an epic workflow, the skill loads the current epic context, completes a single task through its execution loop, reflects on learnings, and generates the next actionable step before stopping for review.

What is a one-task cadence workflow for progressing planned work?

A one-task cadence workflow advances planned work by completing a single epic task, reflecting on outcomes, and generating the next task. It enforces humans-in-the-loop guardrails by stopping after each task until user confirmation.

How do I resume an in-progress epic after losing context?

To resume an in-progress epic after losing context, the skill orients from the current state, re-reads the epic requirements before making changes, and executes the next ready task to continue the workflow.

Does test-driven development work with epic task execution?

Yes, test-driven development works with epic task execution by relying on cape tooling like cape-test-driven-development to verify changes with tests, ensuring production-grade guardrails are met before a task is considered complete.

What are the limitations of one-task-at-a-time epic execution?

The limitation of one-task-at-a-time epic execution is that it stops after each task for user review, requires completing all substeps before closing, and enforces immutable epic requirements, preventing rapid bulk execution without human confirmation.

Can I modify epic requirements while executing a task?

No, you cannot modify epic requirements while executing a task because the skill enforces production-grade guardrails that keep epic requirements immutable, ensuring the original planned work scope remains unchanged during execution.