trellis-brainstorm

Guides requirements discovery and produces PRD, design, and implementation planning artifacts.

Updated Sep 5, 2026
One-click install
npx skills add https://github.com/jiozhaoyue/ST-BgLoader --skill trellis-brainstorm-jiozhaoyue
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trellis-brainstorm
Source: https://github.com/jiozhaoyue/ST-BgLoader/tree/main/.cursor/skills/trellis-brainstorm
Command: npx skills add https://github.com/jiozhaoyue/ST-BgLoader --skill trellis-brainstorm-jiozhaoyue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents premature implementation by turning vague feature requests into validated requirements, forcing evidence gathering from the codebase and explicit user approval before any code is written. ## Core Features & Use Cases - Structured Planning Flow: Creates a Trellis task directory, seeds prd.md, and iteratively refines it through one-at-a-time high-value questions. - Evidence-First Questioning: Requires inspecting code, tests, docs, and task history before asking the user, so only genuine product decisions reach the user. - Convergence Gates: Enforces a requirement convergence gate and a lossless PRD convergence pass, producing design.md and implement.md for complex tasks. - Use Case: A user asks to add a caching layer. The skill inspects the repository, asks only about scope and risk trade-offs, then delivers a final planning summary with goal, acceptance criteria, and key decisions awaiting explicit approval. ## Quick Start Ask the assistant to brainstorm and plan the new feature using the trellis-brainstorm skill 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 plan a feature before writing code with an AI assistant?▼

Use a structured brainstorming workflow that captures the request in a PRD file, inspects the repository for existing evidence, and asks one high-value question at a time. Implementation only begins after you explicitly approve the final planning summary.

What artifacts does the Trellis planning workflow create?▼

It creates prd.md for requirements and acceptance criteria in every task. Complex tasks also require design.md for architecture and trade-offs, plus implement.md for the ordered execution checklist and validation commands.

When should I use brainstorming instead of starting implementation directly?▼

Use it when requirements are unclear, multiple valid technical approaches exist, or the task is a new feature or complex change. Lightweight tasks with fully resolved decisions can proceed after the final summary approval.

Why does the skill ask questions one at a time?▼

Single-question turns keep each user decision focused and prevent unresolved product, scope, or risk choices from piling up. Each question must include the decision needed, why it matters, a recommendation, and the trade-off.

Can the planning phase be skipped if the request seems simple?▼

No. Even lightweight tasks must pass evidence inspection, requirement convergence, final review, and receive fresh explicit approval. Only design.md and implement.md may be omitted for lightweight tasks.