design-flow

design-flow is a skill for Claude Code from chipweaver/veripower. It costs 31 tokens per session (925 once invoked), scanned A, original, MIT.

A design-flow skill coordinates the stages of an integrated-circuit module project. It checks the module's recorded status and decides whether to dispatch work, collect results, wait, finish, or escalate.

In plain words
What is it for?
It is for routing work across IC design stages and deciding when a module should advance, be repaired, paused, completed, or escalated.
Why use it?
It keeps stage changes and rework decisions tied to recorded results, so the next action does not depend on manually tracking the whole pipeline.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions subagents.

Part of the veripower plugin — 12 skills, 2 hooks shipped together

Good fit It is for routing work across IC design stages and deciding when a module should advance, be repaired, paused, completed, or escalated.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/chipweaver/veripower/design-flow
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add chipweaver/veripower --skill design-flow
Clone the repo
git clone --depth 1 https://github.com/chipweaver/veripower

Made for: Claude Code.

Or install veripower, the plugin that ships this one along with the rest of its 12 skills, 2 hooks.

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 design-flow

README.md
[![agentmods](https://agentmods.dev/badge/skills/chipweaver/veripower/design-flow/github.svg)](https://agentmods.dev/skills/chipweaver/veripower/design-flow)
Your own site
<a href="https://agentmods.dev/skills/chipweaver/veripower/design-flow"><img src="https://agentmods.dev/badge/skills/chipweaver/veripower/design-flow/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 design-flow

Your own site · 80×15
<a href="https://agentmods.dev/skills/chipweaver/veripower/design-flow"><img src="https://agentmods.dev/badge/skills/chipweaver/veripower/design-flow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 925 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.
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.00031 $0.00925
Opus 5.5 $0.00012 $0.00370
Sonnet 5.5 $0.00006 $0.00185
Haiku 4.5 $0.00003 $0.00093

Measured 13d ago against content hash 4b3356a56977, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

design-flow 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 13d 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.

skills/design-flow/SKILL.md · 87 lines

How it starts

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

Design Flow

Coordinate module stages, rework and delivery through python3 <skill>/../../framework/scripts/kernel.py, written kernel.py below. <skill> is this skill's directory; {module} contains events.jsonl, intent/brainstorm.md and the stage trees.

The kernel owns events and scheduling. Stage executors own their workdir artifacts and close through the stage CLI, whether running in this conversation or in a subagent. While orchestrating, use the kernel rather than editing events or stage results directly. Inspect source when needed to understand an operation.

Use kernel.py status --module {module} to check current status. Command arguments are available through kernel.py <command> --help.

Run the work

Run the kernel loop:

loop:
  a = kernel.py decide --module {module} [--wake <rule>:<run>] [--closing]
  execute(a)  # actions below; launching a background executor does not wait for it
  if a.action == DONE: finish

For DISPATCH, invoke the returned dispatch_args through the kernel CLI. The response prepares the workdir and identifies the executor; it does not start that executor.

execution Start the work
main-thread Invoke the returned skill in this conversation, acting as that stage's executor.
task Render the stage prompt with the module, rule, skill and workdir from dispatch; launch an independent background executor with that prompt through the host adapter.

Skill names are bare stage names. The host adapter supplies native skill loading and delegation.

After launching a background executor, query decide again so other ready work can proceed. Confirm executor exit through the host before waking or reaping its run; a result file or YIELD does not establish exit. Once it exits, pass --wake <rule>:<run> to decide, including when it left no result. Carry out the returned action:

  • REAP: run kernel.py reap --module {module} --rule <rule> --run <run>, then query again. Reap uses that run's result; an absent result is handled as an incomplete execution.
  • YIELD: report the running work and wait for an executor completion before resuming.
  • ESCALATE: address the reported blocker under the authorization below, then query decide again. Wait when needed information or a reserved human decision is unavailable. kernel.py diagnose records a later addition or correction to repair ownership; --supersedes identifies the diagnosis being replaced.
  • DONE: deliver the conclusions and complete any acceptance in scope, as described below.

Read the full file on GitHub · 87 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. 13d ago Changed · +2 lines 4b3356a56977
  2. 1mo ago Changed · -55 lines 841481e691ae
  3. 1mo ago Changed · -9 lines 0ccb3dd33f9c
  4. 1mo ago First seen · 149 lines · 31 tokens per session scan A c431c99e1ef2

Subscribe to this mod's changes

design-flow is a skill published in the GitHub repository chipweaver/veripower (10 stars, last pushed 7d ago), licensed MIT. It adds 31 tokens to every session and 925 once invoked, about $0.0001 per session on Opus 5.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-31.