executing-plans

Execute implementation plans with review checkpoints and verification gates.

Updated Apr 29, 2026
One-click install
npx skills add https://github.com/pgm1980/stryker-netx --skill executing-plans-pgm1980
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/pgm1980/stryker-netx/tree/main/.claude/skills/executing-plans
Command: npx skills add https://github.com/pgm1980/stryker-netx --skill executing-plans-pgm1980

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of turning a written implementation plan into reliable, step-by-step execution with review checkpoints and verification gates.

Core Features & Use Cases

  • Plan loading and critical review: Reads the plan, identifies concerns, and resolves them with your human partner before starting execution.
  • Task execution with enforced granularity: Executes each task by following bite-sized steps exactly as written, with explicit in_progress and completed states.
  • Safety stops and re-review triggers: Halts immediately on blockers or repeated verification failures, and returns to review when the plan changes fundamentally.

Quick Start

Use the executing-plans skill to load the provided implementation plan, review it critically for gaps, then execute each task exactly as specified while running every required verification step.

Frequently Asked Questions about executing-plans

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

FAQPage Schema
What is task orchestration with review checkpoints and how does it work?

Task orchestration with review checkpoints works by loading a written plan, resolving gaps with a human partner, tracking tasks through in-progress and completed states, and halting execution on blockers or verification failures.

How do I structure a development handoff to ensure tasks are completed deterministically?

Structure a development handoff by providing a written implementation plan with bite-sized steps. The execution engine enforces step granularity, tracks completion states, and applies post-run verification for deterministic delivery.

Do I need a pre-written implementation plan to use task orchestration with checkpoints?

Yes, a pre-written implementation plan is required. The workflow reads this plan input to identify concerns, enforce step granularity, and manage the lifecycle of each task from in-progress to completed.

What triggers a safety stop during task orchestration and execution?

Safety stops are triggered by blockers or repeated verification failures during execution. Halting immediately ensures workflow control, preventing flawed code from progressing through the development handoff.