trellis-brainstorm

Automate structured requirements discovery to seed Trellis tasks and PRDs.

96|10|Updated Aug 15, 2024
One-click install
npx skills add https://github.com/shanyan-wcx/Harmonic --skill trellis-brainstorm-shanyan-wcx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trellis-brainstorm
Source: https://github.com/shanyan-wcx/Harmonic/tree/main/.opencode/skills/trellis-brainstorm
Command: npx skills add https://github.com/shanyan-wcx/Harmonic --skill trellis-brainstorm-shanyan-wcx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams rapidly align on requirements, seed a project PRD, and guide structured brainstorming to converge on an MVP scope.

Core Features & Use Cases

  • Task creation and PRD seeding for new initiatives.
  • One-question-at-a-time Q&A to resolve ambiguities.
  • Optional research steps to compare approaches and converge on MVP.

Quick Start

Initiate a brainstorm by starting the Trellis Brainstorm task to seed a PRD and begin iterative Q&A to converge on MVP.

Frequently Asked Questions about trellis-brainstorm

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

FAQPage Schema
How do I structure brainstorming to define clear MVP requirements?

To structure brainstorming for clear MVP requirements, this skill automates a one-question-at-a-time Q&A loop to resolve ambiguities, seeds a PRD, and enforces convergence on a defined scope with clear acceptance criteria.

How do I create a PRD for a complex feature request with unclear scope?

To create a PRD for a complex feature request, the skill initiates a structured requirements discovery process, framing the problem collaboratively and seeding the document directly in Trellis.

Can I compare multiple viable approaches before defining an MVP?

Yes, you can compare multiple viable approaches before defining an MVP using optional research steps built into the workflow, guiding stakeholders toward a shared decision.

What is the best way to align stakeholders on task management requirements?

The best way to align stakeholders on task management requirements is enforcing a one-question-at-a-time Q&A loop that collaboratively resolves ambiguities and frames complex initiatives.

When should I not use structured requirements discovery for task creation?

You should not use structured requirements discovery for task creation when dealing with simple, well-defined tasks that lack multiple viable approaches or complex feature requests requiring collaborative framing.