agentleFS
lifan-buildslifan-builds/context-harness/.agents/skills/trellis-brainstorm/SKILL.md

trellis-brainstorm

Skill1 starsChanged 4 months agoNo licenceView on GitHub

Guides collaborative requirements discovery before implementation. Creates task directory, seeds PRD, asks high-value questions one at a time, researches technical choices, and converges on MVP scope. Use when requirements are unclear, there are multiple valid approaches, or the user describes a new feature or complex task.

20 other projects use a version of this, 13 of them edited; 12 of 13 edited versions we compared changed its rules; 1 new project in the last 4 weeks, against 0 the 4 before.

How people change it

12 of 13 edited versions changed its rules, and some changes recur.

Of the 13 edited versions we compared: 1 is an older text, 12 made changes of their own.

Not in older versions

  1. Before final review or task.py start, run the PRD convergence pass below.missing from 1 of 1
  2. When requirements are vague, solutions feel over-engineered, or you're about to add complexity "because everyone does" — decompose to fundamental truths before reasoning upward.missing from 1 of 1
  3. What if we removed this? If nothing breaks, it's unnecessary.missing from 1 of 1
  4. Who benefits from this complexity? If "nobody", simplify.missing from 1 of 1
  5. Start with the minimum viable mechanism satisfying all truthsmissing from 1 of 1
  6. Add complexity only when a specific truth demands itmissing from 1 of 1
  7. Before declaring planning ready or running task.py start, rewrite prd.md once against the final structure described in the artifact rules above. This is not optional cleanup; it is the final planning gate.missing from 1 of 1
  8. Remove resolved open questions instead of leaving empty or already-answered sections.missing from 1 of 1

Rules people drop

  1. Ask the questions one at a time.dropped by 12 of 12
  2. Ask the single highest-value remaining question.dropped by 12 of 12
  3. After each user answer, update prd.md before continuing.dropped by 12 of 12
  4. Before final review or task.py start, run the PRD convergence pass below.dropped by 12 of 12
  5. Keep only genuinely blocking open questions.dropped by 12 of 12
  6. Do not start implementation until the user approves or asks for implementation.dropped by 12 of 12
  7. 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.dropped by 4 of 12

Rules people add

  1. A rule we can't quote: its licence doesn't allow itadded by 12 of 12
  2. A rule we can't quote: its licence doesn't allow itadded by 12 of 12
  3. A rule we can't quote: its licence doesn't allow itadded by 12 of 12
  4. A rule we can't quote: its licence doesn't allow itadded by 12 of 12
  5. A rule we can't quote: its licence doesn't allow itadded by 12 of 12
  6. A rule we can't quote: its licence doesn't allow itadded by 12 of 12
  7. A rule we can't quote: its licence doesn't allow itadded by 12 of 12
  8. A rule we can't quote: its licence doesn't allow itadded by 12 of 12

We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.

Adopted by

Surging: 1 new project took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 1 new projectWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projectsWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 1 in all, so this is a hint, not a trend.

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

25 rules. 15 are common, 4 are distinctive, and 6 are very specific to this project.

  • 15

    Common

    Most of the 16 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.