brainstorm

Automate structured brainstorming to define requirements and seed PRDs for AI coding tasks.

114|18|Updated May 15, 2026
One-click install
npx skills add https://github.com/jlifeng/JobPilot --skill brainstorm-jlifeng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brainstorm
Source: https://github.com/jlifeng/JobPilot/tree/main/.agents/skills/brainstorm
Command: npx skills add https://github.com/jlifeng/JobPilot --skill brainstorm-jlifeng

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorm guides AI through collaborative requirements discovery before implementation, ensuring that problems are captured, scope is defined, and a seed PRD is created to drive focused development.

Core Features & Use Cases

  • Task-first approach that guarantees a task exists at the outset and seeds a PRD structure.
  • Action-before-asking principle to derive answers from repo/docs/configs before posing questions.
  • Research-first guidance to surface 2–3 feasible approaches and map them to project constraints.
  • Diverge → Converge workflow to explore future evolution, related scenarios, and edge cases, then converge to an MVP.
  • Step-based workflow encompassing Step 0 seed and Steps 1–7 discovery, followed by final confirmation and handoff to implementation.

Quick Start

Create a brainstorm task with a short goal and seed a PRD using the provided task tooling.

Frequently Asked Questions about brainstorm

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

FAQPage Schema
How do I define requirements for AI coding tasks before implementation?

Structured brainstorming defines requirements for AI coding tasks by capturing goals, seeding a PRD, and tracking open questions. It enforces a Step 0 seed and Steps 1–7 discovery workflow to ensure problems are fully scoped before development begins.

What is the best way to generate a seed PRD for a new software feature?

Generating a seed PRD is best handled through a task-first brainstorming approach that derives answers from repo configs before asking questions. This research-first action maps feasible approaches to project constraints, creating a focused document for MVP scoping.

How does structured brainstorming scope an MVP from broad feature ideas?

Structured brainstorming scopes an MVP using a Diverge to Converge workflow. It explores future evolution and edge cases during discovery, then converges these broad scenarios into a defined minimum viable product scope ready for implementation handoff.

Can I use AI to track open questions during product requirements discovery?

AI tracks open questions during requirements discovery by guiding a step-based workflow from Step 0 through Steps 1–7. This process guarantees a task exists at the outset, capturing unresolved queries alongside the seeded PRD for focused resolution.

Do I need existing repo documentation to start AI-driven requirements planning?

Existing repo documentation is not strictly required but is leveraged by an action-before-asking principle. The process derives answers from available repo docs and configs first, minimizing manual input while grounding the brainstorming in actual project constraints.

When should I not use a structured brainstorming workflow for PRD creation?

You should avoid structured brainstorming workflows for PRD creation when your task scope is already rigidly defined and leaves no room for discovery. The process enforces Steps 0–7 to explore edge cases, which adds overhead for straightforward implementation tasks with no open questions.