Development · By JuliusBrussee

After a bug is found, traces its root cause and feeds a new testable invariant back into the project spec so the bug class can't recur.

JuliusBrussee/cavekit

Compresses SPEC.md writes and spec-referencing prose into terse, symbol-heavy fragments that drop articles, filler and hedging while keeping facts intact.

JuliusBrussee/cavekit

Read-only detector that compares SPEC.md with the code and reports invariant, interface and task drift grouped by severity, without changing anything.

JuliusBrussee/cavekit

Trace bugs and manual fixes back to kits and prompts; fix at the source so the iteration loop can reproduce the fix autonomously.

JuliusBrussee/caveman-code

Builds a skeptical reviewer grounded in the codebase and research notes to try to refute a spec before any code is written, citing file:line evidence and ending in a go or no-go gate.

JuliusBrussee/cavekit

Build feature work with high overbuilding risk. Use for new behavior, product slices, or integrations where repository reuse, strict scope, and an…

JuliusBrussee/caveman

Run a spec-driven agent loop where coding tasks live as markdown specs that move through inbox → active → archive, get implemented by Claude Code or Codex, and pass a review gate before they count…

JuliusBrussee/skills

Scans the code a spec touches for its shallowest module, then proposes a refactor that hides more behind a smaller interface without changing behavior.

JuliusBrussee/cavekit

A read-only explorer for cold-start orientation or failed searches that replies with nothing but file path and line range citations, keeping its reads out of main context.

JuliusBrussee/caveman

Diagnose ambiguous failures before editing. Use for unknown causes, intermittent behavior, performance regressions, or investigations needing…

JuliusBrussee/caveman

Implement reversible compatibility-safe transitions. Use for schema, data, API, protocol, configuration, or dependency migrations requiring rollback…

JuliusBrussee/caveman

Restructure code while preserving behavior. Use for extraction, consolidation, ownership moves, or cleanup where verification must bracket…

JuliusBrussee/caveman

Fix bugs and small behavior changes at the narrowest responsible layer. Use when regression proof, preserved surrounding behavior, and task-relevant…

JuliusBrussee/caveman

Gather external knowledge the spec needs and distill it into §R — the durable research log — so build grounds in facts instead of hallucinating library behavior.

JuliusBrussee/cavekit

Creates, distills, amends and updates the project's SPEC.md from ideas, existing code or bug reports, as the only skill allowed to write that file.

JuliusBrussee/cavekit