skills.rest
WASIDJ
WASIDJCOMMUNITY
Explore all skills by this author →
GitHub

trellis-brainstorm

Guide collaborative requirements discovery and MVP scoping for development tasks.

Updated May 2, 2026
Search Tags:#decision making#product management#technical research#requirements discovery#development collaboration
One-click install
npx skills add https://github.com/WASIDJ/git-demo --skill trellis-brainstorm-wasidj
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trellis-brainstorm
Source: https://github.com/WASIDJ/git-demo/tree/main/.opencode/skills/trellis-brainstorm
Command: npx skills add https://github.com/WASIDJ/git-demo --skill trellis-brainstorm-wasidj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill aids in collaborative requirements discovery for development tasks, enhancing the brainstorming process to be efficient and thorough.

Core Features & Use Cases

  • Collaborative Requirements Discovery: Guides the exploration of requirements before implementation, ensuring clarity and reducing ambiguity.
  • Task-Driven Workflows: Uses task directories, product requirement documents (PRD), and focused question sets to structure brainstorming sessions.
  • Research and Decision-Making: Incorporates research for technical choices and uses converging questions to arrive at a Minimum Viable Product (MVP) scope.

Quick Start

To begin a brainstorming session, type /trellis:start when describing a new development task.

Frequently Asked Questions about trellis-brainstorm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I start collaborative requirements discovery for a new development task?▼

You can start collaborative requirements discovery by initiating a brainstorming session to create task directories, seed product requirement documents, and structure your development tasks efficiently.

What is the best way to scope an MVP during technical research and development collaboration?▼

The best way to scope an MVP is to use converging Q&A sessions that guide technical research and decision making, ensuring your development collaboration converges on a clear minimum viable product scope.

Can I use a task-first approach for product management instead of starting with research?▼

Yes, product management workflows support a task-first approach that uses task directories and seed PRDs to structure brainstorming, alongside a research-first mode for evaluating technical choices.

Does requirements discovery work without setting up specific task directories and PRDs?▼

Requirements discovery relies on creating task directories and seed PRDs to reduce ambiguity, ensuring the brainstorming process remains structured and thorough before implementation begins.

Why do I need guided Q&A sessions for technical research and decision making?▼

You need guided Q&A sessions for technical research and decision making because they automate the convergence of scattered ideas into a focused MVP scope, reducing ambiguity in product management.

Related Skills

Explore More Software Engineering Skills→
huangjunsen0406huangjunsen0406
77

trellis-brainstorm

Create task directories, seed PRDs, and research MVP scope for development tasks.

Community
Advanced
jlawsjlaws
2

agent-product-manager

Translate ideas into structured PRDs, roadmaps, and launch plans.

Community
Intermediate
0xHoneyJar0xHoneyJar
4

planning-sprints

Converts PRDs and SDDs into structured sprint plans with tasks and dependencies.

Official
Advanced
aimskraimskr

prd-strategist

Transform abstract ideas into PRD documents and MVP roadmaps.

Official
Advanced