brainstorm

Orchestrate multi-step discovery to produce PRD and design outputs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Brainstorm skill guides teams through the Inception phase, aligning problem framing, ownership, and architecture concepts to prepare a clear PRD and design artifacts before moving to Define.

Core Features & Use Cases

  • Discovery orchestration: kick off the Inception phase, synchronize memory files, and collect problem statements, success criteria, and constraints.
  • Pre-flight Sync & Context loading: pull project constitution, intent, and interaction-mode to determine how to run the phase.
  • Artifact generation: synthesize a PRD and design documents from the brainstorm results, including UX considerations if UX Discovery ran.
  • Progression gating: ensure prerequisites (sync checks, ROADMAP state, and STATE memory) are satisfied before proceeding to Define.
  • Branching paths for UX: optional UX Discovery, threat modeling, and edge-case analyses feed into later steps.

Quick Start

Initiate brainstorming for a feature by running the Brainstorm unit and providing the feature name.

Frequently Asked Questions about brainstorm

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

FAQPage Schema
How do I run an inception brainstorming session to shape a feature PRD?

To run inception brainstorming, initiate the process by providing the feature name to collect problem statements, success criteria, and constraints, then synthesize the results into a PRD and design documents.

What is Socratic discovery for UX and how does it elicit feature requirements?

Socratic discovery for UX is a guided questioning process that elicits problem statements, requirements, and risk signals, branching into optional UX Discovery and edge-case analyses to inform design documents.

How do I create design docs and a PRD from problem statements before development?

You create design docs and a PRD by orchestrating a multi-step discovery process that performs adversarial review and edge-case analysis on collected problem statements, synthesizing the outputs for handoff.

Do I need a project roadmap and sync checks before starting feature discovery?

Yes, you need a project roadmap and sync checks before starting feature discovery, because progression gating ensures prerequisites like ROADMAP state, STATE memory, and project constitution are satisfied.

Can I include threat modeling and edge-case analysis during inception?

Yes, you can include threat modeling and edge-case analysis during inception, as the process features branching paths that feed these risk signals and UX considerations into later design steps.

What is the best way to align architecture concepts and ownership for a new feature?

The best way to align architecture concepts and ownership is running a structured inception phase that loads project context, performs pre-flight syncs, and frames the problem before generating handoff artifacts.