plan-executor

Execute markdown implementation plans with two-stage review and batch checkpoints.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/orient-bot/orient --skill plan-executor-orient-bot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-executor
Source: https://github.com/orient-bot/orient/tree/main/.claude/skills/plan-executor
Command: npx skills add https://github.com/orient-bot/orient --skill plan-executor-orient-bot

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the execution of complex implementation plans, ensuring tasks are completed systematically with verification and checkpoints, reducing errors and improving development workflow.

Core Features & Use Cases

  • Systematic Task Execution: Follows multi-step plans extracted from documentation.
  • Two-Stage Review: Ensures both spec compliance and code quality before task completion.
  • Batch Checkpoints: Provides regular progress updates and allows for user feedback.
  • Verification: Mandates evidence-based completion for all tasks.
  • Parallel Execution: Supports using sub-agents for independent tasks.
  • Use Case: When implementing a new feature defined by a detailed plan file, this skill will execute each step, run tests, perform code reviews, and commit changes, reporting progress at defined intervals.

Quick Start

Execute the implementation plan found in the file docs/plans/2024-01-15-new-feature.md.

Frequently Asked Questions about plan-executor

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

FAQPage Schema
How do I automate execution of a multi-step implementation plan from a markdown file?

You can automate implementation plan execution by applying a two-stage review process to markdown files, ensuring spec compliance and code quality while running verification commands. Batch checkpoints provide regular progress updates and allow user feedback during systematic multi-task feature implementation.

What is the two-stage review process for systematic task management in feature implementation?

A two-stage review process for task management verifies both spec compliance and code quality before task completion. It enforces evidence-based completion through verification commands, applying to systematic multi-task feature implementation within a worktree flagged with --plan or referencing a specific plan file.

How to execute implementation plans with batch checkpoints and verification commands?

Executing implementation plans with batch checkpoints involves processing tasks systematically from documentation while running verification commands to mandate evidence-based completion. Batch checkpoints provide regular progress updates, allow user feedback, and support parallel execution using sub-agents for independent tasks.

Can I use sub-agents for parallel execution of independent tasks within an implementation plan?

Yes, you can use sub-agents for parallel execution of independent tasks within an implementation plan. This systematic task execution approach extracts multi-step plans from documentation, utilizing batch checkpoints to provide regular progress updates and allow user feedback during the process.

Does this systematic plan execution approach work with worktrees flagged with --plan?

Yes, systematic plan execution applies directly to multi-task feature implementation within a worktree flagged with --plan or when referencing a plan file. It ensures evidence-based completion through verification commands while adhering to spec compliance and code quality standards.

When do I need automated verification and code review for multi-task feature implementation?

You need automated verification and code review for multi-task feature implementation when executing complex plans from markdown files to reduce errors and improve development workflow. This systematic approach mandates evidence-based completion through verification commands and ensures spec compliance before committing changes.