juliusbrussee/blueprint
5 skills197k installs5k starsGitHub
Install
npx skills add https://github.com/juliusbrussee/blueprintSkills in this repo
1CavemanCaveman is a blueprint agent skill that re-encodes SPEC.md and spec-referencing writes into a terse grammar with symbolic operators so Claude Code–style agents spend fewer tokens reading the same constraints. It is loaded by /spec, /build, and /check in the juliusbrussee blueprint stack, triggering on SPEC.md edits or when you say caveman, compress this, or be brief. The rules are strict about what must never be mangled: file paths, env names, numeric versions, and entire code or SQL blocks stay literal while connective tissue shrinks. Invariants use numbered V-lines so downstream /build steps can cite them. Solo builders running spec-driven agent loops use it to keep long-running threads affordable without turning the spec into ambiguous shorthand. It does not replace brainstorming or plan approval—it compresses the artifact once you are ready to write durable spec text.197kinstalls2Backpropbackprop is the spec-driven development discipline that separates SDD from plan-then-execute: when behavior is wrong, you fix code and edit the living spec so recurrence is blocked. Solo builders running Blueprint-style specs use it after verification fails, when users report defects, after incidents, or when checks flag violations with identified root causes. The agent traces to file:line, states root cause in one plain sentence, decides if §V invariants, §I intent, or §T targets need change, drafts §B rows paired with testable §V lines, adds the failing test first, amends the spec, and re-runs verification. It is multi-phase because the same loop applies during Build verification, Ship testing gates, and Operate post-mortems. Expect intermediate familiarity with spec sections (§B, §V, §I, §T) and your test runner. Outcomes are durable: documented backprop history plus invariants future agents and humans must satisfy.5installs3Buildbuild is a Blueprint agent skill for solo builders who already maintain SPEC.md and want deterministic implementation passes without spawning a swarm. It parses build §T.3, build --next, implement next task, or run the build style invocations, reads FORMAT.md once, and plans against every applicable §V invariant and §I interface before touching code. During execute it flips §T status from dot to tilde to x, runs the named verification command, and on failure chains to the backprop skill so recurring breaks become documented invariants. The flow expects a prior spec skill run when SPEC.md is absent. Use it when your spec tasks are lined up and you want one accountable agent thread to chew through the queue with explicit gates and test-aligned edits.5installs4CheckCheck is a Blueprint companion skill that compares your SPEC.md contract to the repo on disk and returns a structured drift report—never mutating files. Solo builders living spec-driven keep §V invariants honest as features land, §I interface shapes aligned with exported APIs, and §T task checkboxes truthful against real commits. Invocation arguments narrow scope: default §V only, or §I, §T, or --all for a full pass. Each finding carries severity grouping and grep-backed addresses so you can open the right line before deciding whether to amend the spec or invoke implementation skills. Because it deliberately does not chain into build or spec writers, it fits recurring Ship review rituals and mid-Build sanity checks when you suspect the agent marked work done prematurely.5installs5SpecSpec is an agent skill that owns every write to SPEC.md at your repository root, so solo builders stop scattering requirements across chat and tickets. It listens for phrases like “write the spec for…”, “new spec”, “distill spec from code”, “amend §V.3”, or “bug: …” and routes to the right workflow. On a greenfield idea it drafts goal, constraints, external interfaces, invariants, and a prioritized task table, then leaves a bug section ready for later backprop. When code already exists, distill mode inventories the repo and encodes reality into the same section model. Amend and backprop keep the living document aligned as you ship and fix issues. The skill always follows FORMAT.md for terse caveman encoding and consistent tables. After a pass it shows the full file and asks whether to edit further or invoke build, making it the handoff artifact between scoping and implementation agents.5installs