trellis-brainstorm

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Starting implementation with unclear requirements leads to rework, scope creep, and misaligned outcomes. This Skill structures the pre-implementation phase by capturing ideas into a task directory immediately, asking only high-value questions one at a time, and converging on a documented MVP scope. ## Core Features & Use Cases - Task-first capture: Creates a task directory and seeds a PRD immediately so no ideas are lost during discovery. - Question gating: Filters out questions answerable by repo inspection or research, asking only blocking or preference questions one at a time. - Research-first technical choices: Delegates technical research to sub-agents that persist 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, the Skill creates a task, inspects the codebase, researches comparable tools, 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?

Start by creating a task directory and seeding a PRD with what is already known, then inspect the repository for existing patterns before asking questions. Ask only blocking or preference questions one at a time, updating the PRD after each answer until scope converges.

How to choose between multiple implementation approaches for a feature?

Research comparable tools and conventions first, then present 2-3 concrete approaches with pros and cons mapped to your repo constraints. Record the chosen direction as an ADR-lite decision with context and consequences in the PRD.

When should I skip brainstorming and implement directly?

Skip brainstorming for trivial changes like single-line fixes or typos, and ask only one confirmation question for simple tasks with clear goals affecting one or two files. Full brainstorming is reserved for vague goals or architectural choices.

What questions should be avoided during requirements discovery?

Avoid meta questions like asking whether to search, requests for code that exists in the repo, and questions answerable through documentation or quick research. Only blocking questions and genuine preference decisions justify interrupting the user.

How do I define MVP scope for a complex feature?

After understanding the goal, diverge across future evolution, related scenarios, and failure cases, then ask the user which items belong in the MVP. Record included items as requirements and explicitly list exclusions in an out-of-scope section.