trellis-task-brief

Generate and validate Trellis task brief.md files from prd, design, and implement documents.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/SilentFlower/flower-trellis --skill trellis-task-brief-silentflower
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: trellis-task-brief
Source: https://github.com/SilentFlower/flower-trellis/tree/main/.agents/skills/trellis-task-brief
Command: npx skills add https://github.com/SilentFlower/flower-trellis --skill trellis-task-brief-silentflower

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping a task's brief.md handoff summary synchronized with its source prd.md, design.md, and implement.md files is error-prone, and starting implementation without a reviewed brief risks scope drift and missed constraints. ## Core Features & Use Cases - Brief Generation and Refresh: Derives Goal, Scope, Non-Goals, Key Decisions, Key Context, Risks, Acceptance, and Next Step from the latest three source documents and overwrites stale brief.md content. - Confirmation Gating: Displays the full brief in conversation and waits for explicit user confirmation before task.py start, with a validated auto-loop exception for runner-authorized refresh_brief actions. - In-Progress Safeguards: Detects missing briefs on in_progress tasks and recommends backfill instead of silently generating unreviewed content. - Use Case: Before running Phase 1.4 task.py start on a Trellis task, invoke this Skill to regenerate brief.md from the current prd.md and design.md, review it in chat, and confirm before implementation begins. ## Quick Start Generate and show the brief for my current Trellis task from its prd, design, and implement files before starting implementation.

Frequently Asked Questions about trellis-task-brief

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

FAQPage Schema
How do I generate a Trellis task brief before starting implementation?▼

Run the Skill against the task directory; it reads prd.md, design.md, and implement.md, derives Goal, Scope, Non-Goals, Key Decisions, Acceptance, and Next Step, writes brief.md, and displays the full text for confirmation before task.py start.

How does the brief stay in sync with prd and design documents?▼

Every run re-reads the latest prd.md, design.md, and implement.md and overwrites brief.md with newly derived content. An existing brief.md is never a reason to skip synchronization, and untraceable old content is discarded.

Can task.py start run without confirming the brief first?▼

Only with explicit user pre-authorization tied to the current task or a validated auto-loop refresh_brief action from the runner. Generic implementation intent like 'go ahead' does not count as brief pre-authorization.

What happens if an in_progress task is missing brief.md?▼

The Skill reads the three source documents, reports the brief is missing, and recommends a backfill. It does not auto-generate an unreviewed brief unless the user explicitly requests backfill and review.

Does the brief replace prd.md, design.md, or implement.md?▼

No. brief.md is a derived handoff view only; the three source documents remain authoritative. The Skill never modifies the sources to fit the brief and never invents requirements they do not express.