spec-execute

Implement plan.md into code changes and generate summary.md.

140|20|Updated Jan 8, 2026

Search Tags:#workflow #execution #spec #archiving #plan.md #summary

Ready to run

npx skills add https://github.com/HHU3637kr/skills --skill spec-execute

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-execute
Source: https://github.com/HHU3637kr/skills/tree/main/spec-execute
Command: npx skills add https://github.com/HHU3637kr/skills --skill spec-execute

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces disciplined execution of approved design plans by implementing plan.md, generating a summary, and archiving the work after confirmation, ensuring traceability and adherence to the spec-first workflow.

Core Features & Use Cases

Enforces plan-driven implementation: reads plan.md, translates it into code changes or documentation, and produces a summary.md.
Ensures user confirmation and retrospective reflection before archiving, enabling risk mitigation and learning.
Supports end-to-end workflow: validation of plan completeness, task generation, sequential execution, and archival.

Quick Start

Run the spec-execute workflow on the target plan.md to implement the approved design and generate a summary.md for review.

Frequently Asked Questions about spec-execute

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

FAQPage Schema

How do I execute a plan.md file and generate a summary for my spec-driven workflow?▼

The spec-execute workflow automates this by reading plan.md, translating it into code changes, and producing a summary.md. It enforces plan-driven implementation by validating task completeness before sequential execution.

What is a spec-first development workflow and how does archiving work?▼

A spec-first workflow requires an approved plan.md before coding. After implementation and user confirmation, the spec-execute process generates a retrospective reflection and archives the work, ensuring traceability and adherence to the design plan.

Can I validate task completeness before executing a plan.md?▼

Yes, you can validate plan completeness before execution. The spec-execute workflow supports end-to-end validation of the plan.md, ensuring required tasks are generated and verified before sequential execution begins.

Do I need user confirmation to archive a completed plan-driven implementation?▼

Yes, user confirmation is required to archive a completed plan-driven implementation. The workflow ensures user confirmation and retrospective reflection occur before archiving, enabling risk mitigation and learning from the executed plan.md.

What is the best way to ensure strict adherence to an approved design plan during coding?▼

The best way to ensure strict adherence is using an automated execution workflow like spec-execute. It reads plan.md, generates sequential tasks, and produces a summary.md, enforcing strict compliance with the spec-first design.

Are there limitations to automating end-to-end execution of approved plans?▼

Limitations include the strict requirement for an approved plan.md prior to execution. The workflow applies specifically to spec-first development processes, requiring validation, user confirmation, and reflection before archiving completed work.