trellis-brainstorm

Guide structured requirements discovery and seed a PRD before implementation.

60|7|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/Ziphyrien/Pi-Telegram --skill trellis-brainstorm-ziphyrien
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: trellis-brainstorm
Source: https://github.com/Ziphyrien/Pi-Telegram/tree/main/.pi/skills/trellis-brainstorm
Command: npx skills add https://github.com/Ziphyrien/Pi-Telegram --skill trellis-brainstorm-ziphyrien

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides AI through collaborative requirements discovery before implementation to prevent scope creep and misalignment across teams and tasks.

Core Features & Use Cases

  • Task-first requirement capture to ensure a concrete starting point
  • Action-before-asking approach that accelerates PRD seeding
  • Research-first mechanism that summarizes options and maps them to repo constraints
  • MVP convergence workflow that seeds a PRD and outlines acceptance criteria

Quick Start

Trigger a brainstorming task with /trellis-start to seed a PRD and outline requirements for a new feature.

Frequently Asked Questions about trellis-brainstorm

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

FAQPage Schema
How do I prevent scope creep during requirements discovery for a new feature?

Requirements discovery prevents scope creep by guiding AI through collaborative brainstorming before implementation, seeding a task directory and a PRD to ensure alignment across teams.

What is the best way to seed a PRD when multiple valid implementation paths exist?

Seeding a PRD uses an action-before-asking approach to accelerate initial document generation, applying research-first mechanisms that summarize options and map them to repo constraints.

How do I start AI-assisted brainstorming for MVP task management?

AI-assisted brainstorming starts by triggering a task with a simple command to capture concrete requirements, run expansion sweeps, and outline acceptance criteria for MVP convergence.

When do I need structured requirements discovery before starting development?

Structured requirements discovery is needed when requirements are unclear, a new feature is described, or multiple implementation paths exist, ensuring a final PRD structure ready for implementation.