brainstorm-prd

Analyze raw ideas and repository context to generate a detailed PRD.

Updated Jan 30, 2026
One-click install
npx skills add https://github.com/nikhilakjoshi/prd-skills --skill brainstorm-prd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorm-prd
Source: https://github.com/nikhilakjoshi/prd-skills/tree/main/brainstorm-prd
Command: npx skills add https://github.com/nikhilakjoshi/prd-skills --skill brainstorm-prd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Take raw ideas and requirements, analyze the current project, and produce a detailed PRD to guide development.

Core Features & Use Cases

  • Analyze ideas against the repository to ground the PRD in the actual codebase.
  • Ask clarifying questions using the AskUserQuestion flow before finalizing.
  • Generate and save the PRD to {project}/plans/prd.md with a structured format.

Quick Start

Analyze the provided ideas and repository context and generate a detailed PRD saved to {project}/plans/prd.md.

Frequently Asked Questions about brainstorm-prd

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

FAQPage Schema
How do I generate a detailed PRD from raw ideas using my existing codebase?

To generate a detailed PRD from raw ideas, you can use a tool that analyzes your repository context to ground the product requirements. It asks clarifying questions and saves the final document to your project directory.

What is the process for turning early discovery ideas into a structured product requirements document?

Turning early discovery ideas into a structured product requirements document involves analyzing raw concepts against the actual codebase, defining project scope, and guiding cross-functional planning through clarification questions before finalizing the output.

Can I generate a PRD that is grounded in my actual repository structure?

Yes, you can generate a PRD grounded in your actual repository structure. The analysis process reads your project context and codebase to ensure the resulting product requirements align with your existing architecture.

How do I handle scope definition and clarifications before finalizing a PRD?

To handle scope definition and clarifications before finalizing a PRD, the system uses an interactive flow to ask clarifying questions. This ensures cross-functional planning requirements are met before saving the final document.

Where does the generated product requirements document get saved in my project?

The generated product requirements document gets saved directly to your project directory at {project}/plans/prd.md. This structured markdown file captures the finalized scope, context analysis, and planning details.

Do I need any specific dependencies or components to brainstorm a PRD?

No specific dependencies or components are required to brainstorm a PRD. The tool operates independently to analyze your project context and raw ideas to produce the structured requirements document.