skills.rest
bdemarzo
bdemarzoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

implement-plan

Implement approved workflow plans with bounded, validated code changes.

2|Updated Mar 27, 2026
Search Tags:#implementation#remediation#handoff#spec compliance#UI verification#validation evidence#workflow plan
One-click install
npx skills add https://github.com/bdemarzo/ai-workflows --skill implement-plan-bdemarzo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement-plan
Source: https://github.com/bdemarzo/ai-workflows/tree/main/skills/implement-plan
Command: npx skills add https://github.com/bdemarzo/ai-workflows --skill implement-plan-bdemarzo

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

It prevents misaligned engineering work by turning an approved plan document into bounded, validated code changes that stay consistent with the product contract.

Core Features & Use Cases

  • Plan-driven implementation: Executes work strictly in the order of plan.md while treating spec.md as the source of truth for user-visible behavior and correctness.
  • Small, bounded changes with guardrails: Stops when the plan becomes invalid or when contract ambiguities threaten correctness, and routes architectural changes back through the orchestrator when needed.
  • Evidence-ready handoff: Produces either a plan-consistent implementation ready for implementation-review or uses execution.md (from the provided template) to record concise validation and deviations for more complex steps.

Quick Start

Use implement-plan to apply the approved workflow plan at docs/workflows/{slug}/plan.md and hand off a validated, ready-for-implementation-review implementation.

Frequently Asked Questions about implement-plan

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

FAQPage Schema
How do I implement an approved workflow plan while preserving the spec contract?▼

Plan-driven implementation executes work strictly in the order of plan.md while treating spec.md as the source of truth for user-visible behavior and correctness, applying bounded, validated code changes.

What happens when a workflow plan becomes invalid or ambiguous during implementation?▼

When the plan becomes invalid or contract ambiguities threaten correctness, implementation stops and routes architectural changes back through the orchestrator rather than proceeding with uncertain modifications.

How do I record validation evidence for complex implementation steps?▼

Use the execution.md template to record concise validation and deviations for complex steps, producing evidence-ready handoff documentation for the implementation review process.

Can I use this approach for UI changes that require visual verification?▼

Yes, this workflow supports rendered UI changes by requiring disciplined validation and verification before handing off to implementation-review with clear progress and next steps.

What's the best way to hand off completed implementation work for review?▼

Produce a plan-consistent implementation ready for implementation-review, including execution.md evidence with validation details and any recorded deviations from the original plan.

Do I need an approved plan document before starting implementation?▼

Yes, this requires an approved workflow plan at docs/workflows/{slug}/plan.md and treats the spec contract from docs/workflows/{slug}/spec.md as the source of truth for correctness.

Related Skills

Explore More Software Engineering Skills→
a2musa2mus

speckit-tasks

Convert plan.md and spec.md into dependency-aware task lists.

Community
Advanced
nexus-a1nexus-a1

todo-work

Surface pending tasks from TODO.md and mark them in progress.

Community
Advanced
matsenmatsen
29

bip.epic.tuckin

Persist orchestrator state to durable storage before a context reset.

Community
Intermediate
miles990miles990

requesting-code-review

Dispatch a code-reviewer subagent to review changes before merging.

Community
Intermediate