JuliusBrussee/cavekit

COLLECTIONcommunity
JuliusBrusseeMITUpdated 4mo agoGitHub

A Claude Code plugin that turns natural language into blueprints, blueprints into parallel build plans, and build plans into working software with automated iteration, validation, and cross-model peer review.

compressed spec-driven development for claude code one file · three commands · zero sub-agents Plan-then-execute forgets. SDD remembers — but most SDD frameworks bury that value under agent swarms, dashboards, and ceremony that costs more tokens than it saves. Cavekit 4 is a rewrite from the ground up. It keeps only what earns its durable spec — at repo root survives context resets. caveman…

This collection bundles
5 skills3 commands

⚠ The trust score below reflects the collection's repository only. The bundled units are not individually verified or scanned — review them before use.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1kGitHub stars
71Forks
4mo agoLast update
Package
AuthorJuliusBrussee
LicenseMIT
Sourcegithub
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface—
Security scan✓ CleanvHEAD · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 14, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

No tool declarations found in the source3mo ago

Forge read 0 source files from the repository archive and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.

About

compressed spec-driven development for claude code one file · three commands · zero sub-agents Plan-then-execute forgets. SDD remembers — but most SDD frameworks bury that value under agent swarms, dashboards, and ceremony that costs more tokens than it saves. Cavekit 4 is a rewrite from the ground up. It keeps only what earns its durable spec — at repo root survives context resets. caveman encoding — ~75% fewer tokens than prose. Symbols, fragments, pipe tables for repeating records. backprop…

Keywords
claude-codeparallel-agentsskillsspec-driven-developmenttest-driven-developmentcollection
Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.

Topics

Related in testing & ci