implement-plan

Execute phased technical plans from Markdown files with automated and manual verification.

Updated Feb 20, 2026
One-click install
npx skills add https://github.com/optimistic-updt/sync-agents --skill implement-plan-optimistic-updt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement-plan
Source: https://github.com/optimistic-updt/sync-agents/tree/main/.agents/skills/implement-plan
Command: npx skills add https://github.com/optimistic-updt/sync-agents --skill implement-plan-optimistic-updt

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the execution and verification of technical plans defined in Markdown files, ensuring changes are implemented correctly and efficiently.

Core Features & Use Cases

  • Plan Execution: Follows phased technical plans, implementing changes step-by-step.
  • Verification: Runs automated checks and pauses for manual verification after each phase.
  • Adaptability: Adapts to real-world code discrepancies while adhering to the plan's intent.
  • Use Case: A developer receives a plan.md file detailing a new feature implementation. This Skill guides them through each phase, running make check and prompting for manual sign-off before proceeding, ensuring robust delivery.

Quick Start

Implement the technical plan located at docs/changes/feature-x/plan.md.

Frequently Asked Questions about implement-plan

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

FAQPage Schema
How do I execute a technical plan from a Markdown file step-by-step?

Executing a technical plan from a Markdown file involves reading the document, understanding the codebase context, and implementing phased development tasks. The process scopes to ensuring successful integration while adhering to specified criteria.

How does automated and manual verification work during phased development execution?

Automated and manual verification during phased development execution runs automated checks like `make check` and pauses for manual sign-off after each phase. This ensures robust delivery and confirms successful integration before proceeding to the next step.

Can I adapt technical plan execution when there are real-world code discrepancies?

Yes, technical plan execution adapts to real-world code discrepancies while adhering to the plan's original intent. This ensures changes are implemented correctly and efficiently even when the codebase context differs from initial assumptions.

What do I need to implement a phased development plan from Markdown?

To implement a phased development plan from Markdown, you need the original tickets for context, an understanding of your codebase, and the specified criteria. This ensures changes are implemented correctly and efficiently with proper verification.

What is the best way to ensure successful integration when following a technical plan?

The best way to ensure successful integration when following a technical plan is to execute phased development tasks while running automated checks and pausing for manual verification. This guarantees adherence to specified criteria and robust delivery.

Why does plan execution pause after each development phase?

Plan execution pauses after each development phase to perform automated and manual verification. This ensures successful integration and adherence to specified criteria before proceeding, guaranteeing changes are implemented correctly and efficiently.