brainstorm SKILL.md skillA
brainstorm from chipweaver/veripower is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add chipweaver/veripower/brainstorm@git:20260920.095d122Pins git:20260920.095d122 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- chipweaver/veripower
- Path
skills/brainstorm/SKILL.md- Versions recorded
- 12
- Latest version
- git:20260920.095d122, committed Sep 20, 2026
- First version recorded
- Aug 2, 2026
- Size
- 4,102 bytes
- Repository stars
- 9
- License
- MIT
Use when brainstorming a new module's requirements and architecture into a brainstorm.md, one way to write the intent document the pipeline starts from; not for design.md, RTL, constraints, or any in-pipeline stage.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Pre-Pipeline Requirements Brainstorm
Interview the engineer and write `{module}/intent/brainstorm.md`, one way to produce the intent
document the pipeline starts from. Run **in your own session, before the pipeline** — this
conversation never enters the pipeline's context, and you write no `result.json`.
The document is frozen once a run starts, so a requirements change is a fresh invocation of
this skill, never an edit to an in-flight artifact. Re-invoked that way, the existing document
is your input: what is left to ask is what the change unsettles, and you say in the document
which parts this round did not touch.
## Where the output goes
`{module}` is any path the engineer wants — the same one the pipeline is later given as
`--module`. If they named only a module, ask; do not invent a parent, or you send them looking
for a tree they did not ask for.
Create `{module}/intent/` and put the document in it, along with anything the engineer delivers
that it names as authoritative — a reference model, a register map, a standard. That directory
is the whole of what the pipeline treats as intent: a file left at the module root is handed to
no stage and recorded by no proof.
…Read the whole file at its exact version.
How to install
mdr add chipweaver/veripower/brainstorm@sha256:dab735335abb85feThe line at the top of this page pins the label git:20260920.095d122, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_hvnjdevuxyoq2jit)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 12 versions of this file, between Aug 2, 2026 and Sep 20, 2026, about one every 4 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260920.095d122 latest | 2026-09-20 | 095d122 | 4,102 B | A | view · diff |
| git:20260914.2c79f06 | 2026-09-14 | 2c79f06 | 4,078 B | A | view · diff |
| git:20260907.3d16bec | 2026-09-07 | 3d16bec | 4,072 B | A | view · diff |
| git:20260907.90db501 | 2026-09-07 | 90db501 | 4,241 B | A | view · diff |
| git:20260907.a691012 | 2026-09-07 | a691012 | 5,372 B | A | view · diff |
| git:20260907.2d2f196 | 2026-09-07 | 2d2f196 | 5,613 B | A | view · diff |
| git:20260907.c461cc0 | 2026-09-07 | c461cc0 | 5,595 B | A | view · diff |
| git:20260905.c63a078 | 2026-09-05 | c63a078 | 5,517 B | A | view · diff |
| git:20260904.b0fbf80 | 2026-09-04 | b0fbf80 | 6,067 B | A | view · diff |
| git:20260807.97731ce | 2026-08-07 | 97731ce | 5,321 B | A | view · diff |
| git:20260806.6fea301 | 2026-08-06 | 6fea301 | 5,520 B | A | view · diff |
| git:20260802.fb52ea0 | 2026-08-02 | fb52ea0 | 5,523 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4102 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
chipweaver/veripower · 9 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hvnjdevuxyoq2jit GET https://markdownregistry.com/api/v1/resolve?ref=chipweaver/veripower/brainstorm GET https://markdownregistry.com/api/v1/blob/dab735335abb85fe9bb6806d345ae6437060fa8c8929fa5238818726030746a8
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from chipweaver/veripower
Every file in chipweaver/veripower