harness:executing-plans

Execute implementation plans with review checkpoints and features.json scope validation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It turns a written implementation plan into a controlled, verifiable execution session so work doesn’t drift, skip required checks, or proceed without clear alignment to scope and acceptance criteria.

Core Features & Use Cases

  • Plan-first execution with critical review: Loads the plan, identifies questions or concerns, and pauses for partner alignment before starting when needed.
  • Step-accurate task execution: Executes each task by following bite-sized steps exactly as written in the plan, updating task states through in_progress to completed.
  • Rigid scope and verification guardrails: Enforces that every task traces to features.json acceptance criteria and that out-of-scope items trigger an explicit pause/ask; also emphasizes running gates after each task and stopping when verification fails.
  • Completion handoff to the finishing workflow: After tasks and verification, delegates the finalization and branch completion to the required finishing sub-skill.

Quick Start

Use the harness:executing-plans skill when you have a plan you want executed in a separate session with checkpoints and scope validation.

Frequently Asked Questions about harness:executing-plans

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

FAQPage Schema
How do I execute a development plan without scope creep?

Plan execution with scope control works by constraining task implementation to features.json acceptance criteria and pausing explicitly when out-of-scope items or unclear instructions arise. Verification gates run after each task to prevent drift.

What is the best way to add review checkpoints to workflow orchestration?

Workflow orchestration with review checkpoints loads the implementation plan, identifies concerns, pauses for partner alignment, and runs verification gates after each task. Execution stops when verification fails to maintain alignment.

Can I trace tasks to acceptance criteria during plan execution?

Tracing tasks to acceptance criteria during plan execution is enforced by mapping every task rigidly to features.json. Out-of-scope items trigger an explicit pause, and discovered architectural decisions must be escalated.

How do I handle out-of-scope tasks discovered during development branch execution?

Handling out-of-scope tasks during development branch execution requires triggering an explicit pause and asking for alignment. Architectural decisions discovered during execution must be escalated rather than resolved autonomously.

Does plan execution support handoff to a finishing workflow for branch completion?

Plan execution supports handoff to a finishing workflow by delegating finalization and development branch completion to a required finishing sub-skill after all tasks and verification gates pass, separating execution from branch closure.

When do I need verification gates in a task-by-task engineering execution workflow?

Verification gates are needed in task-by-task engineering execution workflows after every task completes to validate acceptance criteria. Execution stops immediately when verification fails, preventing compounding errors across subsequent tasks.