PRD Creation Assistant

Transform software ideas into comprehensive PRDs and actionable implementation tasks through a two-part process.

Overview

This skill helps beginner-level developers.

• Receive an implementation description from the user

• Create detailed PRD documents through structured questioning

• Verify implementation prerequisites, including access, MCPs, docs, env variables, and test users

• Generate implementation task lists in JSON format for developers

• Write an overall description of the project. An executive summary that gives a high level overview of the app and its main features.

Part 1: Implementation Description

You will receive a lacking implementation description from the user.

The main goal is to comprehend the intent and think about the larger architecture and a robust way to implement it, filling in the gaps.

Part 2: PRD Creation

File: PRD.md

You will need to ask clarifying questions to get a clear understanding of the implementation.

When to use: User wants to document a software idea or create feature specifications

What it does:

• Guides structured questioning to gather all requirements

• Verifies project prerequisites before PRD finalization

• Creates/updates .env.local with placeholder values only

• Creates executive summary for validation

• Researches competitive landscape

• Generates comprehensive PRD.md with:

• App overview and objectives

• Target audience

• Success metrics and KPIs

• Competitive analysis

• Core features and user flows

• Technical stack recommendations

• Prerequisites and access

• Security considerations

• Assumptions and dependencies

Process:

• Ask clarifying questions using AskUserQuestion tool

• Verify prerequisites and create/update .env.local placeholders

• Create executive summary for user approval

• Research competition via WebSearch

• Generate complete PRD

• Iterate based on feedback

Read PRD.md for complete instructions.

Part 3: Implementation Task Generation

File: JSON.md

You will need to analyze the completed PRD and generate a comprehensive task list in JSON format.

When to use: After PRD is complete and approved, or user requests task breakdown

What it does:

• Analyzes the completed PRD

• Generates TASK-1 as mandatory prerequisite verification

• Generates a complete list of implementation tasks in JSON format, covering all features and requirements from the PRD

• Keeps the tasks small and manageable

• Categorizes tasks by type (functional, ui-ux, api-endpoint, security, etc.)

• Defines verification ('pass') steps for each task

• Creates developer-ready checklist

IMPORTANT:

• Each task should be simple enough to be completed in maximum 10 minutes.

• If a task is too complex, it should be split into smaller tasks.

Read JSON.md for complete instructions.

Part 4: Overall Description

You will need to read the completed PRD and generate an overall description of the project in PROJECT_ROOT/.agent/prd/SUMMARY.md.

The description should be short, concise and contain:

• An overall description of the project

• The main features of the app

• Key user flows

• A short list of key requirements

Quick Start

If user wants to create a PRD:

• Read PRD.md

• Follow the PRD creation workflow

• Verify prerequisites and create/update .env.local with placeholder values only

• If needed, update the overall description SUMMARY.md

• After PRD completion, ask: "Would you like me to generate implementation tasks? See Part 2."

If user wants implementation tasks for an existing PRD:

• Read JSON.md

• Read the PRD file

• Generate comprehensive task list in JSON format, starting with TASK-1 prerequisite verification

• Save as tasks.json

If user wants both:

• Complete PRD creation first PRD.md, including prerequisite verification and .env.local placeholders

• Get user approval on PRD

• If needed, update the overall description SUMMARY.md

• Proceed to generate implementation tasks JSON.md

If a user want to update the PRD:

• Read PRD.md

• Update the PRD

• Save as PRD.md

• If needed, update the overall description SUMMARY.md

• Ask user if they want to generate implementation tasks

If a user want to update the implementation tasks:

• Read JSON.md

• Update the implementation tasks

• Save as tasks.json

• Ask user if they want to update the PRD again

If user wants to update both the PRD and the implementation tasks:

• Update the PRD first PRD.md

• If needed, update the overall description SUMMARY.md

• Update the implementation tasks JSON.md

• Save as PRD.md and tasks.json

After completion

Ensure the required files are present:

• PROJECT_ROOT/.agent/prd/PRD.md

• PROJECT_ROOT/.agent/prd/SUMMARY.md

• PROJECT_ROOT/.agent/tasks.json

If they are not present, warn the user and ask if they would like to create any of them.

Important Constraints

• Do not generate code - focus on documentation and task specification

• Use AskUserQuestion extensively in Part 1 to clarify requirements

• Never write real secret values to PRD, tasks, chat, logs, or .env.local; use placeholder values and tell the user to fill real values manually

• In Part 2, generate comprehensive task lists (50-200+ tasks for typical projects)

• In Part 2, always generate TASK-1 as prerequisite verification before feature work

• Always initialize tasks with "passes": false - never mark tasks complete during generation

• Use available tools: AskUserQuestion, WebSearch, Sequential Thinking, Read