dev-plan

Generate PRDs and track checkpoints for multi-phase software feature planning.

2|Updated Jan 28, 2026
One-click install
npx skills add https://github.com/andreaserradev-gbj/dev-workflow --skill dev-plan-andreaserradev-gbj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-plan
Source: https://github.com/andreaserradev-gbj/dev-workflow/tree/main/plugins/dev-workflow/skills/dev-plan
Command: npx skills add https://github.com/andreaserradev-gbj/dev-workflow --skill dev-plan-andreaserradev-gbj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan and document new software features by generating PRDs and tracking checkpoints throughout multi-session work.

Core Features & Use Cases

  • PRD generation: creates structured master plans and optional sub-PRDs to guide implementation.
  • Research and planning workflow: coordinates agents to research, plan, and document the feature.
  • Progress tracking: records phase gates and deliverables to resume across sessions.

Quick Start

Run the dev-plan skill with a feature description to start the PRD workflow.

Frequently Asked Questions about dev-plan

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

FAQPage Schema
How do I generate a PRD for a new software feature?

You generate a PRD by providing a feature description to initiate a structured planning workflow. The system produces a Master Plan and optional Sub-PRDs with defined phase gates and file outputs.

What is the best way to track feature planning progress across sessions?

Feature planning progress is tracked by recording phase gates and deliverables as checkpoints. This allows you to resume multi-phase research, planning, and documentation workflows across different sessions.

Can I use this workflow to coordinate research and planning agents?

Yes, you can coordinate agents to research, plan, and document software features. The workflow supports multi-phase task execution across research and planning before finalizing documentation.

Do I need any dependencies to start planning features with PRDs?

No dependencies are required to start planning features with PRDs. You only need to provide a feature description to initiate the automated workflow and generate the necessary documentation outputs.

When should I create optional Sub-PRDs instead of a single Master Plan?

You create optional Sub-PRDs when a feature requires multi-phase documentation that exceeds a single Master Plan. Sub-PRDs break down complex workflows into defined gates for more manageable progress tracking.