ProductFlow: Skill for Claude Code

.agents/skills/trellis-brainstorm/SKILL.md

trellis-brainstorm is a skill for Claude Code, Codex from yuqie6/ProductFlow. It costs 65 tokens per session (941 once invoked), scanned A, original, MIT.

A guided planning skill for discovering requirements before building a new feature or other complex change. It creates planning files, asks focused questions one at a time, checks the codebase for existing answers, and narrows the work to an initial version.

In plain words
What is it for?
Use it to explore an unclear request, investigate the repository, research technical choices, resolve open decisions, and prepare a shared plan.
Why use it?
It reduces the risk of building the wrong thing when requirements are incomplete or several technical approaches are possible.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is yuqie6/ProductFlow's own configuration. It tells Claude Code and Codex how to work on ProductFlow itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ProductFlow configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is TASK_DIR=$(python3 ./.trellis/scripts/task.py create "<short task title>" --slug <slug>).

Reuse

Borrowing it

Nothing to install: this file belongs to yuqie6/ProductFlow. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/yuqie6/ProductFlow/main/.agents/skills/trellis-brainstorm/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/yuqie6/ProductFlow

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for trellis-brainstorm

README.md
[![agentmods](https://agentmods.dev/badge/skills/yuqie6/productflow/trellis-brainstorm/github.svg)](https://agentmods.dev/skills/yuqie6/productflow/trellis-brainstorm)
Your own site
<a href="https://agentmods.dev/skills/yuqie6/productflow/trellis-brainstorm"><img src="https://agentmods.dev/badge/skills/yuqie6/productflow/trellis-brainstorm/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for trellis-brainstorm

Your own site · 80×15
<a href="https://agentmods.dev/skills/yuqie6/productflow/trellis-brainstorm"><img src="https://agentmods.dev/badge/skills/yuqie6/productflow/trellis-brainstorm.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 941 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Excessive Agency · line 20
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00065 $0.00941
Opus 5 $0.00032 $0.00470
Sonnet 5 $0.00013 $0.00188
Haiku 4.5 $0.00006 $0.00094

Measured 10d ago against content hash 056f7cab7274, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

trellis-brainstorm scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/trellis-brainstorm/SKILL.md · 113 lines

How it starts

The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Trellis Brainstorm

Non-Negotiable Interview Contract

Interview me relentlessly about every aspect of this plan until we reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer.

Ask the questions one at a time.

Non-Negotiable Evidence Rule

If a question can be answered by exploring the codebase, explore the codebase instead.

This is mandatory. Before asking the user a question, first check whether the answer is already available in code, tests, configs, docs, existing specs, or task history.

Do not ask the user to confirm facts that the repository can answer. Ask only for product intent, preference, scope, risk tolerance, or decisions that remain ambiguous after inspection.


Use this skill during Phase 1 planning to turn the user's request into clear requirements and planning artifacts.

Preconditions

Use this skill only after task-creation consent has been given and the user is ready to enter Trellis planning.

If no task exists yet, create one:

TASK_DIR=$(python3 ./.trellis/scripts/task.py create "<short task title>" --slug <slug>)

Use a concise title from the user's request. Use a slug without a date prefix. task.py create adds the MM-DD- directory prefix automatically.

task.py create creates the default prd.md. Update that file with the current understanding before asking follow-up questions.

Planning Flow

  1. Capture the user's request and initial known facts in prd.md.
  2. Inspect available evidence before asking questions:
    • code, tests, fixtures, and configs
    • README files, docs, existing specs, and domain notes
    • related Trellis tasks, research files, and session history when present
  3. Separate what you found into:
    • confirmed facts
    • product intent still needed from the user
    • scope or risk decisions still needed from the user
    • likely out-of-scope items
  4. Ask the single highest-value remaining question.
  5. Include your recommended answer with the question.
  6. After each user answer, update prd.md before continuing.
  7. For complex tasks, create or update design.md and implement.md before implementation starts.

Read the full file on GitHub · 113 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 10d ago First seen · 113 lines · 65 tokens per session scan A 056f7cab7274

Subscribe to this mod's changes

trellis-brainstorm is a skill published in the GitHub repository yuqie6/ProductFlow (302 stars, last pushed today), licensed MIT. It adds 65 tokens to every session and 941 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

ordercli

Foodora-only CLI for checking past orders and active order status (Deliveroo WIP).

djblack1209-coder/OpenClaw-Bot · 21 tokens

resume-builder

Generate professional resumes that conform to the Reactive Resume schema. Use when the user wants to create, build, or generate a resume through conversational AI, or asks about resume structure, sections, or content. This skill guides the agent to ask clarifying questions, avoid hallucination, and produce valid JSON…

amruthpillai/reactive-resume · 71 tokens

frontend-feature

Build a new page, view, or data-driven feature in the Next.js frontend. Use when adding a route under the dashboard/marketing area, wiring UI to a backend endpoint, adding client state, or creating a localized page. Covers App Router, data fetching, Zustand stores, and i18n.

vstorm-co/full-stack-ai-agent-template · 64 tokens

stripe-skill

Process payments, manage customers, issue refunds, and handle subscriptions via the Stripe CLI. Pass any Stripe command (customers, charges, paymentintents, refunds, invoices, products, prices, subscriptions) and the tool runs it for you and returns parsed JSON.

zeenie-ai/OpenCompany · 56 tokens

authoring-ci-workflows

Use when adding or editing a GitHub Actions workflow, composite action, or reusable workflow under .github/ — new CI jobs, triggers, matrices, checkout/clone tuning, action pinning, GitHub App token auth, concurrency groups, timeout-minutes, paths filters, caching, or runner choice. Covers PostHog's workflow-authoring…

PostHog/posthog · 193 tokens

Nerve Development

Nerve backend (Python) and frontend (React/TS) development and code contribution. Use when writing Python code for Nerve, fixing bugs, adding features, reviewing Nerve PRs, building the frontend, running tests, or working with the Nerve codebase. Triggers on "nerve code", "nerve PR", "fix nerve", "nerve feature"…

ClickHouse/nerve · 96 tokens