trellis-brainstorm

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

Updated Jun 9, 2026
One-click install
npx skills add https://github.com/gyc-12/Archipelago --skill trellis-brainstorm-gyc-12
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trellis-brainstorm
Source: https://github.com/gyc-12/Archipelago/tree/main/.cursor/skills/trellis-brainstorm
Command: npx skills add https://github.com/gyc-12/Archipelago --skill trellis-brainstorm-gyc-12

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Jumping into implementation with unclear requirements leads to rework, scope creep, and misaligned outcomes. 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 repo inspection, docs, and research, asking only blocking or preference questions. - Research-First Decisions: Delegates technical-choice research to a trellis-research sub-agent that persists findings to research files, then presents 2-3 concrete approaches with trade-offs. - Diverge-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: When a user describes a vague new feature like "add group chat delegation", the Skill creates the task, inspects the codebase, researches orchestration patterns, asks targeted preference questions, and produces a PRD with acceptance criteria and an implementation plan. ## Quick Start Ask the AI to brainstorm requirements for a new feature you are considering 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 asks one high-value question at a time. Derive answers from the codebase first, then converge on MVP scope with explicit acceptance criteria and out-of-scope items.

What is the best way to research technical options during planning?

Delegate each research topic to a dedicated sub-agent that identifies comparable tools, summarizes conventions, and persists findings to research files. The main conversation then reads those files and presents 2-3 feasible approaches with trade-offs for the user to choose.

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 affecting 1-2 files, ask one confirmation question then implement. Reserve full brainstorming for complex tasks with vague goals or architectural choices.

How do I avoid asking too many questions during requirements gathering?

Apply a question gate: never ask anything derivable from repo inspection, docs, or quick research, and never ask meta questions like whether to search. Only ask blocking questions that prevent progress or preference questions between concrete presented options.

What should a PRD contain before implementation starts?

A pre-implementation PRD should contain the goal, requirements, testable acceptance criteria, definition of done, technical approach with an ADR-lite decision record, explicit out-of-scope items, and technical notes with constraints and research references.