trellis-brainstorm

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

1|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/MaplumeX/Milesto --skill trellis-brainstorm-maplumex
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trellis-brainstorm
Source: https://github.com/MaplumeX/Milesto/tree/main/.agents/skills/trellis-brainstorm
Command: npx skills add https://github.com/MaplumeX/Milesto --skill trellis-brainstorm-maplumex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting implementation with unclear requirements leads to rework and misaligned outcomes. This Skill structures the pre-coding phase by interviewing the user one question at a time, auto-gathering repo context, 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 derivable or meta questions, asking only blocking or preference questions one at a time. - Research-first decisions: Delegates technical-choice research to a sub-agent that persists 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 with out-of-scope items. - Use Case: A user says "add cloud sync to the app." The Skill creates a task, inspects the repo, researches sync patterns, asks targeted preference questions, and produces a PRD with requirements, acceptance criteria, and an implementation plan. ## Quick Start Ask the AI 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, and asks one high-value question at a time. Derive answers from the codebase first, then ask only blocking or preference questions until scope converges.

What is the best way to define MVP scope for a new feature?▼

First diverge by considering future evolution, related scenarios, and edge cases, then converge by explicitly listing what is in the MVP and what is out of scope. Record testable acceptance criteria and a definition of done in the PRD.

How should AI agents research technical choices during planning?▼

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

When should brainstorming be skipped before implementation?▼

Skip brainstorming for trivial changes like single-line fixes or typos, and use only a single confirmation question for simple tasks with clear goals and well-defined scope. Full brainstorming is reserved for complex, ambiguous tasks.

What questions should be avoided during requirements discovery?▼

Avoid meta questions like "should I search?" and questions answerable by inspecting the repo or docs. Only ask blocking questions that prevent progress or preference questions where multiple valid approaches exist.