trellis-brainstorm

Guides collaborative requirements discovery and converges on an MVP scope before implementation.

2|Updated Jun 2, 2026
One-click install
npx skills add https://github.com/42team-ru/teampilot --skill trellis-brainstorm-42team-ru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trellis-brainstorm
Source: https://github.com/42team-ru/teampilot/tree/main/.cursor/skills/trellis-brainstorm
Command: npx skills add https://github.com/42team-ru/teampilot --skill trellis-brainstorm-42team-ru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting implementation with unclear requirements leads to rework, scope creep, and misaligned expectations. This Skill structures the pre-implementation phase by interviewing the user one question at a time, researching technical options, and converging on a documented MVP scope. ## Core Features & Use Cases - Task-first capture: Immediately creates a task directory and seeds a PRD so ideas are recorded before any Q&A begins. - Question gating: Filters out low-value questions by deriving answers from the repo, docs, or research first, asking only blocking or preference questions. - Research delegation: Spawns research sub-agents that persist findings to research files, then presents 2-3 concrete approaches with trade-offs. - Diverge-then-converge flow: Expands thinking across future evolution, related scenarios, and edge cases, then locks an explicit MVP scope with out-of-scope items. - Use Case: A developer describes a vague new feature; the Skill creates the task, inspects the codebase, researches comparable tools, asks targeted questions, and produces a PRD with acceptance criteria and an implementation plan. ## Quick Start Ask the assistant to brainstorm requirements for a new feature you are planning before writing any code.

Frequently Asked Questions about trellis-brainstorm

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

FAQPage Schema
How do I gather requirements before starting a coding task?

Start a brainstorm session that creates a task directory and seeds a PRD immediately, then answers derivable questions from the codebase itself. It asks only blocking or preference questions one at a time and updates the PRD after each answer.

How to choose between multiple implementation approaches for a feature?

The Skill triggers research-first mode, delegating topics to research sub-agents that persist findings to files. It then presents 2-3 concrete approaches with pros and cons and asks a single preference question.

When should I skip brainstorming and implement directly?

Trivial changes like single-line fixes or typos skip brainstorming entirely. Simple tasks with a clear goal and well-defined scope need only one confirmation question before implementation.

Does the brainstorm workflow work with AI coding assistants?

Yes, it is designed for AI coding workflows and integrates with a task workflow where the brainstormed PRD feeds directly into implementation phases. A Codex CLI exception performs research inline instead of using sub-agents.

What are the limitations of one-question-at-a-time discovery?

Asking one question per message slows down sessions where the user already knows all answers upfront. The process is best suited for ambiguous or complex tasks, not well-specified work.