workflow-plan-writer

Convert approved specs or work-item briefs into structured implementation plans.

9|Updated Feb 22, 2026

Search Tags:#workflow #planning #architecture #implementation #protocol #spec #project-management

Ready to run

npx skills add https://github.com/lhpaul/ai-dev-framework-template --skill workflow-plan-writer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: workflow-plan-writer
Source: https://github.com/lhpaul/ai-dev-framework-template/tree/main/.codex/skills/workflow-plan-writer
Command: npx skills add https://github.com/lhpaul/ai-dev-framework-template --skill workflow-plan-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts an approved spec or work-item brief into a concrete implementation plan that guides cross-functional teams and reduces ambiguity.

Core Features & Use Cases

Spec-to-plan automation: generates a structured plan from an approved spec, including milestones, tasks, dependencies, and success criteria.
Refactor planning: produces a plan-only document for refactors, leveraging the work item brief and architectural constraints.
Protocol-guided execution: enforces steps, guardrails, and decision records to ensure consistent planning across projects.

Quick Start

Provide an approved spec or work item brief and request the plan writer to generate an implementation plan following the generate-implementation-plan protocol.

Frequently Asked Questions about workflow-plan-writer

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

FAQPage Schema

How do I convert an approved spec into a concrete implementation plan?▼

To convert an approved spec into a concrete implementation plan, you provide the work-item brief to generate a structured document mapping milestones, tasks, dependencies, and success criteria ready for execution.

What is the best way to plan a major refactor using architectural constraints?▼

Planning a major refactor using architectural constraints involves producing a plan-only document from your work item brief, mapping protocol-driven milestones and decisions to guide execution and reduce ambiguity.

Can I generate milestones and task dependencies from a work-item brief automatically?▼

Yes, you can generate milestones and task dependencies from a work-item brief automatically by applying a protocol-driven process that maps risks and decisions into a structured plan for cross-functional teams.

Does implementation planning work for both feature development and refactors?▼

Implementation planning works for both feature development after spec approval and refactors that require a plan-only document, ensuring protocol-guided execution and consistent decision records across projects.

Do I need an approved spec before generating an implementation plan?▼

Yes, you need an approved spec or work item brief before generating an implementation plan, as the protocol-driven process maps architectural constraints and requirements from the approved brief into structured milestones.