trellis-brainstorm

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

4|1|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/ZipperCode/lingma2api --skill trellis-brainstorm-zippercode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trellis-brainstorm
Source: https://github.com/ZipperCode/lingma2api/tree/main/.opencode/skills/trellis-brainstorm
Command: npx skills add https://github.com/ZipperCode/lingma2api --skill trellis-brainstorm-zippercode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting implementation with vague or evolving requirements leads to rework, scope creep, and misaligned solutions. 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-first technical choices: Delegates investigation of libraries, patterns, and conventions to a research sub-agent, then presents 2-3 concrete approaches with trade-offs. - Diverge-then-converge workflow: Expands thinking across future evolution, related scenarios, and edge cases, then locks an explicit MVP scope with out-of-scope items. - Use Case: A user says "add a plugin system to our CLI." The Skill creates a task, inspects the codebase, researches plugin patterns in similar tools, presents feasible approaches, and produces a PRD with acceptance criteria and an ADR-lite decision record. ## Quick Start Ask the assistant to brainstorm requirements for a new feature or complex task 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?

Use a structured brainstorm workflow that creates a task directory, seeds a PRD with known facts and assumptions, then asks one high-value question at a time. Derive answers from the codebase and docs first, and only ask blocking or preference questions.

What is the best way to choose between multiple implementation approaches?

Research how similar tools solve the problem first, then present 2-3 concrete approaches with pros and cons mapped to your repo's constraints. Record the chosen direction as an ADR-lite entry covering context, decision, and consequences.

When should I skip brainstorming and implement directly?

Skip brainstorming for trivial changes like single-line fixes or typos. For simple tasks with a clear goal and well-defined scope, ask one confirmation question and proceed. Reserve full brainstorming for vague goals or architectural choices.

How do I define MVP scope for a new feature?

After understanding the goal, diverge across future evolution, related scenarios, and failure cases, then converge by explicitly listing what is in the MVP and what is out of scope. Capture testable acceptance criteria as checkboxes in the PRD.

What questions should I avoid asking users during requirements discovery?

Avoid meta questions like "should I search?" and questions answerable by inspecting the repository, such as "what does the code look like?" Only ask blocking questions that prevent progress or preference questions between concrete options.