trellis-brainstorm

Create a task directory, seed a PRD, and converge on MVP scope.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/C-jcbest/agent --skill trellis-brainstorm-c-jcbest
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trellis-brainstorm
Source: https://github.com/C-jcbest/agent/tree/main/.agents/skills/trellis-brainstorm
Command: npx skills add https://github.com/C-jcbest/agent --skill trellis-brainstorm-c-jcbest

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Brainstorming to clarify requirements before implementation by creating a task directory, seeding a PRD, asking focused questions, researching options, and converging on MVP scope.

Core Features & Use Cases

  • Task-first documentation: ensures a task exists and seeds initial PRD.
  • One-question-per-message Q&A loop: drives convergence with minimal blocking questions.
  • Research-first exploration: uses sub-tasks to compare options and map to repo constraints.
  • Expansion & risk analysis: considers future evolution and edge cases before final decisions.
  • ADR-lite decisions: captures decisions and consequences for traceability.

Quick Start

Create a new brainstorm task directory and seed a PRD with the initial goal.

Frequently Asked Questions about trellis-brainstorm

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

FAQPage Schema
How do I brainstorm and clarify product requirements before writing a PRD?▼

To brainstorm product requirements, you can use a structured discovery process that seeds an initial PRD, asks focused questions one at a time, and researches options to converge on an MVP scope. This ensures task-first documentation and traceable decisions.

What is the best way to structure collaborative requirements discovery for new features?▼

Collaborative requirements discovery works best when it creates a dedicated task directory, enforces a one-question-per-message Q&A loop to minimize blocking, and maps research options to repository constraints before finalizing decisions.

How do I converge multiple proposed options into a single MVP scope for product development?▼

To converge multiple options into an MVP scope, apply a research-first exploration approach that compares alternatives, analyzes future expansion risks, and captures ADR-lite decisions to document consequences and enforce traceability.

Does this requirements brainstorming approach work when initial task descriptions are unclear?▼

Yes, this requirements brainstorming approach is specifically designed for tasks where requirements are unclear or multiple options exist. It guides developers and product teams from vague proposals to a structured PRD through focused Q&A.

How do I capture decisions and consequences during early product development brainstorming?▼

You can capture decisions and consequences during brainstorming by using an ADR-lite format. This records traceable choices made after researching options and analyzing edge cases, ensuring future evolution is considered before finalizing the MVP.