executing-plans

Route upstream executing-plans workflows into devflow finish-feature verification and PR/MR creation.

1|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/AndreJorgeLopes/devflow --skill executing-plans-andrejorgelopes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/AndreJorgeLopes/devflow/tree/main/skills/executing-plans
Command: npx skills add https://github.com/AndreJorgeLopes/devflow --skill executing-plans-andrejorgelopes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents an upstream “execute plans” workflow from handing off to the wrong branch-finishing mechanism, so your work ends with devflow’s verification and PR/MR creation instead of an incompatible default flow.

Core Features & Use Cases

  • Delegates execution to the upstream skill: Uses the upstream executing-plans logic for task-by-task execution discipline and tracking while passing arguments through.
  • Forces the final handoff to devflow: Overrides only the terminal finish step to route completion into /devflow:finish-feature, ensuring verification, PR/MR creation, and Hindsight learnings happen coherently with devflow’s VCS workflow.
  • Handles upstream skill discovery and renames: Attempts to locate superpowers:executing-plans, searches for renamed variants, optionally consults a cached changelog or generates one, and surfaces actionable errors if it cannot find the upstream skill.
  • Supports incomplete-work transparency: Passes BLOCKED / NEEDS_CONTEXT style status from the upstream completion into devflow’s finish-feature so users understand what remains before PR/MR creation.

Quick Start

Use devflow:executing-plans when you have a step-by-step implementation plan and want the agent to complete tasks and then hand off to devflow:finish-feature for verification and PR/MR creation.

Frequently Asked Questions about executing-plans

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

FAQPage Schema
How do I ensure execution plans finish with a pull request instead of the default branch flow?

To ensure execution plans finish with a pull request, you need a workflow that overrides the terminal state transition to route completion into VCS verification and PR/MR creation rather than the upstream default branch flow.

What happens to blocked or incomplete tasks when handing off to PR creation?

Blocked or needs-context status from the upstream completion is passed transparently into the PR creation flow, so users can see exactly what work remains before the pull request is generated.

How do I execute a step-by-step implementation plan while maintaining devflow VCS coherence?

You execute a step-by-step implementation plan by delegating task-by-task discipline to an upstream skill, then overriding the final handoff step to invoke devflow's finish-feature verification and PR creation process.

Can I use this workflow if the upstream executing-plans skill has been renamed?

Yes, the workflow handles upstream skill discovery by searching for renamed variants and consulting a cached changelog, surfacing actionable errors only if it cannot locate the required upstream skill.

Why does my execution plan hand off to the wrong branch-finishing mechanism?

Your execution plan hands off to the wrong branch-finishing mechanism because the upstream default flow is incompatible with devflow, requiring a terminal state override to force VCS-coherent verification and PR creation.

Do I need a written execution plan before starting the devflow PR automation workflow?

Yes, you need a written execution plan because this workflow applies to implementation sessions driven by step-by-step plans where upstream per-task discipline is needed before the final devflow handoff.