trellis-brainstorm

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

1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/hejiajiudeeyu/delegated-execution-workspace --skill trellis-brainstorm-hejiajiudeeyu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trellis-brainstorm
Source: https://github.com/hejiajiudeeyu/delegated-execution-workspace/tree/main/.agents/skills/trellis-brainstorm
Command: npx skills add https://github.com/hejiajiudeeyu/delegated-execution-workspace --skill trellis-brainstorm-hejiajiudeeyu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Jumping into implementation with vague 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 and delegating technical research to a trellis-research sub-agent. - 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 and acceptance criteria. - Use Case: A user says "add a plugin system to our CLI." The Skill creates the task, inspects the codebase, researches plugin patterns in comparable tools, presents 2-3 concrete approaches with trade-offs, and produces a confirmed PRD with an implementation plan split into small PRs. ## Quick Start Ask the AI to brainstorm requirements for a new feature you are planning, and it will create a task, seed a PRD, and interview you one question at a time until the scope is confirmed.

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 repo inspection and asks only blocking or preference questions one at a time. The session ends with a confirmed requirements summary and implementation plan.

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

Use a diverge-then-converge approach: first expand thinking across future evolution, related scenarios, and failure cases, then explicitly select what enters the MVP and record everything else under Out of Scope in the PRD.

How do I research technical approaches without polluting the main conversation?▼

Delegate each research topic to a trellis-research sub-agent that persists findings to research/<topic>.md files and returns only a file path and one-line summary. Independent topics can be researched in parallel, and the PRD references the persisted files.

When should brainstorming be skipped for a development task?▼

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

Does this workflow work on Codex CLI?▼

Yes, but with an exception: on Codex CLI the research is done inline in the main session instead of dispatching a trellis-research sub-agent, because Codex sub-agents run with isolated context and cannot resolve the active task path.