executing-plans

Execute pre-written implementation plans with checkpoints and HANDOFF.md context updates.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/hicucu/forge --skill executing-plans-hicucu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/hicucu/forge/tree/main/skills/executing-plans
Command: npx skills add https://github.com/hicucu/forge --skill executing-plans-hicucu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of lost context, skipped checkpoints, and inconsistent execution when implementing pre-written project plans across separate development sessions, ensuring every planned step is completed as intended.

Core Features & Use Cases

  • Pre-Execution Plan Review: Critically evaluates the implementation plan before starting to catch gaps, ambiguities, or risks early, preventing wasted work on flawed plans.
  • Step-by-Step Checkpoint Execution: Tracks each planned task with explicit verification steps, marking tasks as in-progress and completed only after passing required checks.
  • Cross-Session Context Preservation: Automatically updates HANDOFF.md for complex full-path implementations to record progress and context, so work can be seamlessly picked up in future sessions.
  • Use Case: If you have a multi-phase feature implementation plan split across 3 separate work sessions, use this Skill to execute each phase without losing progress, missing verification steps, or repeating work already completed.

Quick Start

Use the executing-plans skill to implement the feature plan saved in the docs/2024-q3-user-auth-plan.md file, following all checkpoints and verification steps outlined in the plan.

Frequently Asked Questions about executing-plans

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

FAQPage Schema
How do I maintain context continuity when executing implementation plans across separate development sessions?

Executing implementation plans across separate development sessions maintains context continuity by tracking step-by-step checkpoints and automatically updating HANDOFF.md for complex paths to record progress for future work.

What is the best way to prevent skipped checkpoints during multi-phase feature implementation?

Preventing skipped checkpoints during multi-phase feature implementation requires step-by-step task tracking with explicit verification steps, marking tasks completed only after passing required checks.

How do I critically evaluate a pre-written project plan before starting implementation?

Critically evaluating a pre-written project plan before implementation catches gaps, ambiguities, or risks early through mandatory pre-execution plan review, preventing wasted work on flawed plans.

Can I use step-by-step checkpoint execution for simple 1-2 file changes and debugging workflows?

Step-by-step checkpoint execution applies to all plan execution scenarios including simple 1-2 file changes, systematic debugging workflows, and complex full-feature implementation pipelines with multi-phase specifications.

Does plan execution integrate with git worktree management and development branch finalization?

Plan execution integrates with required forge workflow skills for git worktree management and development branch finalization, ensuring isolated work sessions and proper branch handling.

Why does context get lost when running implementation pipelines split across multiple work sessions?

Context gets lost across multiple work sessions without automatic HANDOFF.md context updates and checkpoint tracking, which enforce mandatory plan review and record progress to seamlessly pick up future work.