executing-plans

Execute written plans as auditable tasks with guardrails and verifications.

24|5|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/yves-s/just-ship --skill executing-plans-yves-s
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/yves-s/just-ship/tree/main/skills/executing-plans
Command: npx skills add https://github.com/yves-s/just-ship --skill executing-plans-yves-s

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan-driven execution automates turning a written plan into an auditable sequence of tasks with guardrails and checkpoints.

Core Features & Use Cases

  • Load a plan, critically review it for gaps, and translate it into actionable tasks.
  • Execute tasks step-by-step with status tracking, verifications, and completion notes.
  • Complete development using a finishing-a-development-branch workflow and subagent coordination.
  • Stop on blockers and escalate to human input when needed.

Quick Start

Load your plan file, review it for gaps, and begin executing tasks with built-in verifications.

Frequently Asked Questions about executing-plans

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

FAQPage Schema
How do I execute a development plan step-by-step with built-in guardrails?

Plan-driven execution translates a written plan into auditable tasks with verifications and status tracking. You load your plan, review it for gaps, and execute tasks sequentially using subagent coordination until completion.

What is the best way to track task status and verification during a development workflow?

Task status tracking and verification are automated through stepwise execution checkpoints. The system records completion notes and applies guardrails at each step, stopping on blockers to escalate for human input when needed.

Can I use subagents to automate critical review and task execution from a predefined plan?

Subagents coordinate critical review and task execution from a predefined plan. The workflow reviews the plan for gaps, translates it into actionable tasks, and delegates execution while maintaining auditability through completion notes.

Does this plan execution workflow integrate with finishing a development branch?

The execution workflow integrates directly with finishing-a-development-branch processes. After stepwise execution and verification, it completes development using subagent coordination to finalize the branch workflow.

When should I expect plan execution to stop and require human input?

Execution stops automatically when blockers are encountered during task verification. The system escalates these hold-ups for human input, ensuring critical gaps are addressed before resuming the stepwise development workflow.

Do I need a written plan file before starting task execution?

A predefined written plan is required as input to begin. The execution process loads the plan, critically reviews it for gaps, and translates it into actionable, auditable tasks before stepwise execution begins.