Index of every page on this site: llms.txt
All skills
jetbrains avatar

/brainstorming

@e85862d
by jetbrainsjetbrains/thinkrail8.4k stars
532
Run it yourself

Use before implementing a feature, a change in behavior, or a bug fix — however small. Not for questions, checks, or edits that change no behavior (typos, documentation or configuration only, mechanical refactors).

Use this Skill: https://skilld.dev/gh/jetbrains/thinkrail/brainstorming

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

amending-specs.md

≈556 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Amending specs — brainstorming's shared tail

Entry: the accepted change is built and verified (spine step 8). Saves: the durable spec graph. Ends: the workflow.

The specs stay the ground truth only if every change lands in them. This is your job, not a round of approvals: do it yourself, and let the user see the result in the Changes review. Read the writing-specs concept skill first — its bar holds for every edit here.

  1. Find what changed in the specs' terms — from the task-spec and the actual diff, not the plan:
    • the goal doc, when a capability was added or removed or a principle overturned;
    • architecture.md, when topology, a cross-module decision, or a repo-wide invariant moved;
    • the owning module or submodule SPEC.md, for a responsibility, boundary, contract, decision, or known limitation — and a new spec for a genuinely new module;
    • for a bug classified silent or wrong, the spec that should have stated the intended behavior.
  2. Amend top-down — goal → architecture → modules — without asking the user to approve the list or the edits. spec_create for a new spec, spec_update for frontmatter, edit for prose. Write the decisions and the why the code cannot show, once, in the spec that owns them; link the rest by id. Unconfirmed assumptions are marked unconfirmed where they stand.
  3. Check against reality. Each amended spec matches what was built, not what was planned; the specs you touched don't contradict each other or use a term two ways. Run spec_validate and fix what it reports.
  4. Nothing durable changed? (A bug classified right, a change the specs already describe.) Then make no edits — never invent content to show activity.
  5. Report in a line or two: which specs changed, by name, and any unconfirmed assumption left in them. No per-file narration.
  6. Retire the task-spec — once its durable content is in the tree, set its status: done with spec_update. Never delete it: it stays in the user's Artifacts tab, and spec search skips a finished task-spec.

Ending

This workflow ends here. PR lifecycle work, if requested, then enters shipping-a-pr separately.

Source: SKILL.md on GitHub

No rule matched.

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts22d3 checks · Risk SAFE
  • Gen Agent Trust Hub22d

    The brainstorming skill provides a structured manual workflow for designing features and fixing bugs through documentation and user interviews. It consists entirely of documentation, contains no executable scripts or remote dependencies, and includes safety-conscious instructions for bug reproduction.

  • Socket26d

    No alerts

  • Snyk26d

    Risk: LOW · No issues

Signed by skilld at e85862d. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 days ago.

Activeupdated last month

README badge

README badge for jetbrains/thinkrail/brainstorming