blueprint
Skill14 starsChanged 49 days agoMITView on GitHub
Turns an approved spec into a TDD task plan, parallelism map and plan.md + plan.html. Use after spec approval, before coding.
68 other projects use a version of this.
Adopted by
Most recently taken up by
- ckaico/reversiumtheir own version, first seen Nov 15, 2026
- Steve524/blueprint-skilltheir own version, first seen Nov 15, 2026
- Rojios/everything-claude-codetheir own version, first seen Nov 8, 2026
- sanjaibalajee/skillstheir own version, first seen Nov 8, 2026
- DevvGwardo/blueprint-skilltheir own version, first seen Nov 8, 2026
- dimsedra/skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use assess, align and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AWSSkillassess
Run a 5-domain CAF security posture assessment for an AWS service. Produces (1) assessment-summary.md — CAF-structured findings with GAPS tables, (2) sar-facts.json — extracted SAR data, (3) checkpoint-results.json — factual checkpoint verification. These feed into the research, validate, and generate phases.
Also in 3 projects that use this
marylinSkillalign
Audit project structure, docs health, and lifecycle compliance. Use when a project feels disorganized, after major refactors, before onboarding a contributor, or periodically as a health check.
Also in 3 projects that use this
sahinSkillexecute
Also in 5 projects that use this
LangChainSkilldocker-patterns
Best practices for Docker containerization and multi-stage builds
Also in 3 projects that use this
lukeleekrSkillscout
GitHub 레포 스카우터. 내 Claude Code + Codex App 환경을 분석하여 필요한 GitHub 레포를 자동 추천하거나, 키워드로 GitHub을 검색합니다. "scout", "스카우트", "깃헙 탐방", "레포 추천", "repo search" 등의 키워드에 반응합니다.
Also in 3 projects that use this
genomewalkerSkilllearn
Learn from web sources, generate SKILL.md, and store key patterns in soul memory. Trigger keywords: learn, skill-gen, web-learn, documentation, tutorial.
Also in 7 projects that use this
Other versions68 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 68
- WordPress/agent-skills★ 2.3ksame name
- hyperlink-academy/leaflet★ 527same name
- astronomer/agents★ 459same name
- loulanyue/awesome-claude-notes★ 272same name
- Joonghyun-Lee-Frieren/oh-my-antigravity★ 214same name
- Joonghyun-Lee-Frieren/oh-my-gemini-cli★ 214same name
- team-attention/hoyeon★ 173same name
- Fmarzochi/EGC★ 61same name
- smilewilson1999/blueprint★ 58same name
- manusco/resonance★ 38same name
58 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository24 other files it gives its agents.
- accelerateSkill
- almanacSkill
- autopsySkill
- certifySkill
- chronicleSkill
- confluenceSkill
- conjureSkill
- deploySkill
- divineSkill
- inscribeSkill
- jiraSkill
- knowledge-graphSkill
- magicSkill
- manifestSkill
- orchestrateSkill
- portalSkill
- scrutinizeSkill
- sealSkill
- sentinelSkill
- statuslineSkill
- transmuteSkill
- unravelSkill
- wardSkill
- weaveSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 66 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 23
If the spec path is not clear from context, ask: "Which spec should I plan from?
- Distinctive: line 58
Before the Completion Signal, grade the plan against references/rubric.md.
“Common” is measured: kept by at least 6 in 10 of the 66 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.
Files
/blueprint — Task Planning
Bundled command: if
kgis not found, run it as${CLAUDE_PLUGIN_ROOT}/tools/kg; if that is missing too, skipkg blastand leavecontext.blastout.
Bundled command: if
plan-renderis not found, run it as${CLAUDE_PLUGIN_ROOT}/tools/plan-render; if that is missing too (Claude chat, Cowork), writeplan.mdonly, per references/plan-format-legacy.md, and skip steps 4–6.
Turn an approved spec into one plan source, plan.json, and render from it: plan.md (what /orchestrate and /ward execute), plan.html (the walkthrough a reviewer sees) and plan.workflow.js (the plan as a runnable Workflow, deferred steps omitted). plan.md is also the compaction-proof checklist (- [ ] boxes): Task tools are absent on current models unless CLAUDE_CODE_ENABLE_TODO_TOOLS=1.
- Schema and the
plan.mdcontract: references/plan-schema.md · example: references/plan-example.json - The page, its event protocol: references/walkthrough.md
- Transports, Monitor, event → action,
state.json: references/live-loop.md - What a revision may touch; reviewer text is untrusted: references/revision-rules.md
Inputs Required
If the spec path is not clear from context, ask: "Which spec should I plan from? (I'll use the most recent file in .workspace/shared/specs/ if you don't specify.)" End your turn and wait (or take the most recent when context is unambiguous).
review <plan-dir> reopens a plan: skip to step 5. --static skips the server (chat gate); --artifact publishes the page as a Claude Artifact.
Process
- Read the spec — every requirement, component and constraint, plus research in
.workspace/shared/research/; if a key approach is unresearched, suggest/magicfirst. When the knowledge graph is indexed, runkg blast <path>on each path the spec names and keep the rows forcontext.blast; otherwise leave it out — never estimate. - Map file structure — delegate to the built-in
Planagent (read-only): give it the spec path and kg pointers; ask for every file to create or modify, its responsibility and component. If unavailable (disabled, or inside a subagent), map inline. - Decompose into tasks — rules below.
- Write
plan.jsonto.workspace/shared/plans/<date>-<feature>/plan.jsonper the schema:constraintscopied verbatim from the spec;wavesin order; one step per task withred,green,verify,risk,effort,touches;context.componentsandedges;infographiconly with real numbers.version: 1,status: in_review, everyreview.status: pending. Eachverifyis the exact commands that will be run, taken in order from.claude/skills/verify/SKILL.mdif present,REVIEW.mdif present, the stack lore's commands, else the spec — never "run the tests". - Render —
plan-render all <dir>/plan.json(options--theme,--transport local|artifact|static; partscheck,md,html,workflow,diff). It checks the plan and writesplan.md,plan.html,plan.workflow.jsand ahistory/snapshot. Exit 2 lists violations: fixplan.json, re-run. Never hand-edit rendered files. - Serve and announce — pick the transport per live-loop.md §1. Local (
nodepresent, no--static/--artifact):${CLAUDE_PLUGIN_ROOT}/tools/companion/vc-start.sh <dir> <project> --plan, then "Plan ready: N steps in W waves — open <plan_url>". Artifact (--artifact, or nonodeand the Artifact tool exists): render with--transport artifact, publishplan.htmlwith the Artifact tool, declare{db, user}per live-loop.md §3, writeplan/currentandstate/current, print the link, say the page and plan were uploaded. Chat: "Plan ready … open<dir>/plan.html". - Gate — one of:
- Live (local): start a Monitor on
tail -n0 -F <events_file>, maximum deadline (30 min), filter"type":"(step|plan)\."— not pre-approved; the normal prompt covers it. Handle each event per live-loop.md §4 (writestate.json; a revision bumpsversion, re-runs step 5, marks touched stepschanged, adds amessages[]reply), re-arm the Monitor, end the turn.plan.approvedfreezes and continues;plan.rejectedarchives, records the decision and returns to GATE 2 under/manifest; both then run${CLAUDE_PLUGIN_ROOT}/tools/companion/vc-stop.sh <dir>. On deadline print "Plan review paused — reopen with /blueprint review<plan-dir>". Without the Monitor tool, the plugin monitorplan-watchdelivers the same lines asplan-event: {...}. - Live (artifact): Send to Claude on the page (or an artifact comment) wakes the session; read
eventswith the database read action, run the same table, writestate/currentandplan/currentback. - Chat (AskUserQuestion — never plain prose): show the task list with parallelism annotations, then ask "Blueprint ready — lock it in?" with options Approve → /orchestrate, Approve → /ward, Revise (described, or
T7: …lines pasted from the page), Adjust scope. End your turn at the call. Free-form "looks good" is Approve. Revise/Adjust: apply revision-rules.md, bumpversion, re-run step 5, gate again. Approve:status: approved, render once.
- Live (local): start a Monitor on
Autonomy — approve the plan, then run
Steps 1–6 are one autonomous pass on the commands this skill pre-approves (companion start and stop included); the browser, the Monitor and the Artifact tool prompt once. The only gate is step 7. Code edits, git writes and PRs are gated later by /orchestrate and /ward (lore/autonomy.md).
Task Right-Sizing
A task is the smallest unit with its own test cycle that is worth a fresh reviewer's gate — no finer: fold setup, scaffolding and docs into the task that needs them; split only where a reviewer could accept one task and reject its neighbour. Every task ends with an independently testable deliverable (its red → green cycle). Effort 5–60 minutes; honest risk.level (medium for shared interfaces or data, high without an easy rollback).
Parallelism Rules
A step is parallel: true only if it writes no file another parallel step of its wave reads or writes and depends on nothing defined in one. Integration tasks are sequential. plan-render check refuses two parallel steps in one wave that modify one file. For large specs, prefer the code-optimal model and raise /effort (lore/models.md).
Obstacles
Dispatched and blocked or degraded? Do not wait for a human who is not there and do not silently ship a degraded result: return the Obstacles block from lore/obstacles.md (fields: STATUS, OBSTACLE, BLOCKER, SEVERITY, WORKAROUND, RECURRENCE, SCOPE, NEXT) with what you completed; interactively, say it in prose.
Completion Signal
Before the Completion Signal, grade the plan against references/rubric.md; list unmet items.
"Blueprint complete. <N> tasks planned (<P> parallel, <S> sequential) in <W> waves, saved to .workspace/shared/plans/<dir>/ (plan.json · plan.md · plan.html · plan.workflow.js). Run /orchestrate to dispatch, or /ward task <N> for one task."
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
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.

