skills.rest
iJosueeh
iJosueehCOMMUNITY
Explore all skills by this author →
GitHub

dev-planner

Generates phased development plans from a completed product specification document.

Updated Jun 29, 2026
Search Tags:#development planning#dependency graph#phase breakdown#dev-plan#product spec#mvp scope#tech stack validation
One-click install
npx skills add https://github.com/iJosueeh/amauta --skill dev-planner-ijosueeh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dev-planner
Source: https://github.com/iJosueeh/amauta/tree/main/.opencode/skills/dev-planner
Command: npx skills add https://github.com/iJosueeh/amauta --skill dev-planner-ijosueeh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning a finished product specification into an executable development plan is error-prone: phases get ordered against dependencies, tasks are too vague to implement, and tech stack choices go unverified. This Skill converts Product-Spec.md into a structured DEV-PLAN.md with dependency-ordered phases, concrete file paths, and acceptance criteria. ## Core Features & Use Cases - Generation Mode: Reads Product-Spec.md (and Design-Brief.md if present), validates the tech stack via web search, and outputs a phased DEV-PLAN.md with deliverables, key files, and acceptance criteria per phase. - Iteration Mode: When the spec changes, analyzes impact scope and updates only pending phases while leaving completed phases untouched. - Plan Critique Check: Challenges phase ordering, MVP scope, and tech stack choices before writing the plan to counteract sycophantic planning. - Use Case: After finalizing a product spec for a web app, run the skill to produce a DEV-PLAN.md where Phase 1 is a runnable MVP and each subsequent phase lists exact files to create, ready for a dev-builder agent to execute. ## Quick Start Ask the AI to run /dev-planner after your Product-Spec.md is complete to generate a phased DEV-PLAN.md development plan.

Frequently Asked Questions about dev-planner

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

FAQPage Schema
How do I turn a product spec into a development plan?▼

Run /dev-planner after completing Product-Spec.md. The skill reads the spec, validates the tech stack via web search, builds a feature dependency graph, and outputs DEV-PLAN.md with ordered phases, key files, and acceptance criteria.

What inputs does a development planning skill require?▼

Product-Spec.md is mandatory, including its completed Idea Stage Exit Criteria section. Design-Brief.md and existing project code are optional; without them the plan runs in degraded mode with visual details marked as pending.

Can I update an existing dev plan when the spec changes?▼

Yes, iteration mode compares the updated Product-Spec.md against the existing DEV-PLAN.md, identifies affected phases, and updates only pending phases. Phases already marked complete remain untouched.

Why does the plan require explicit user confirmation before coding?▼

A hard gate prevents invoking the dev-builder until DEV-PLAN.md is saved and the user explicitly confirms, recorded in .forge/plan-confirmed.json. This ensures phase boundaries are agreed upon before any code is written.

What are the limitations of automated phase breakdown?▼

The skill does not write code, gather requirements, or fix bugs; those belong to separate skills. Plans depend on spec quality, and tech stack validation requires web search access to confirm framework versions.

Related Skills

Explore More Software Engineering Skills→
tapaniatapania
5

5d-sdd

Orchestrate a 10-phase 5D Spec-Driven Development workflow producing PLAN.md, SPEC.md, and a Task List.

Community
Basic
mystilleefmystilleef
1

spae-build

Executes one atomic task from PLAN.md with test-driven implementation and state persistence.

Community
Advanced
ddsyasasddsyasas

architecture

Design software with Clean Architecture patterns and explicit boundaries.

Community
Basic
jacksonlee-twjacksonlee-tw

planning-and-task-breakdown

Decomposes specifications into ordered, verifiable implementation tasks with acceptance criteria.

Community
Intermediate