caveman
Replies drop filler and pleasantries and keep every technical detail. On from the first message.
Better outcomes,
every round
Memory, workflows and review for Claude Code and Codex, built into the repository.
Your goal
Long HorizonContinues across rounds
your decision
01 / Recall
Start with project memory
Illustrative workflow04 / Audit
A fresh set of eyes
Independent review checks the work against the goal. Findings return to Execute, then face a fresh audit.
How auditing works ↗·
Candidate
awaiting checks
Human
approval
your decision
Illustrative system · choose skills for the task
Coding agents start every session from zero
This one starts where you left off
Only what the task needs
Token-efficient
Skill names sit in a small index. The full instructions, project notes and checks load when a task calls for them, so the context window stays free for your code.
See how memory loadsSome of it runs by itself
You never type these. They run in every session.
recall
Before unfamiliar work, the agent reads the project notes that apply and skips the rest.
pitfalls.md
A mistake that cost a retry gets written down, so the next session avoids it.
Planned
Question the problem, try more than one answer, and tune it before it ships.
/dare
Takes the problem apart from first principles in four fresh passes: break it down, test each assumption, rebuild, check the result against reality.
/arena
Runs several attempts in parallel, keeps the strongest as the base, and folds in the best parts of the rest.
/lab
Builds a live prototype with controls, so you tune motion and layout by feel before anything is final.
Audited
A second opinion on every change, from a reviewer with no stake in the work.
Inspect
A fresh reviewer gets the change, its scope and the checks it must pass.
Repair
Each finding is checked against the actual code before anything changes. Confirmed gaps get fixed, then reviewed again.
Decide
You get the evidence. Nothing merges, publishes or ships without your approval.
/codex-reviewA different model family, OpenAI's Codex, reviews the diff.
/impartial-reviewFresh agents that never saw the work review it.
/handoff-auditWrites an audit brief with exact scope and pass/fail checks that another session can run.
Remembered
Decisions, pitfalls and commands live in plain files next to your code. They go wherever the repository goes.
Explore memoryCLAUDE.mdCore rules, read every session
AGENTS.mdThe same for Codex
architecture.mdHow the system fits together
pitfalls.mdHard-won lessons
commands.mdBuild, test, deploy
/long-horizon
Your session holds the planA fresh agent builds each roundA separate auditor checks the real filesOnly work that passes moves forward
Building and checking happen in fresh contexts, so your main conversation stays small and quality holds on tasks too big for one context window.
/long-horizon · Claude Code and Codex
/long-horizon-workflows · Claude Code · the ultra version
Runs the same rounds through Claude Code's built-in workflows, with a fresh builder, an inspector and a panel of judges each round, written verdicts, and a run journal.
Production-ready
Long tasks run in audited rounds. Finished work gets polished and measured before it ships.
/showpiece
Pushes a page, deck or document past the generic look toward work you'd put in a portfolio.
/wow-loop
Reviews and repairs one piece against the goal, round after round, and keeps only changes that prove better.
/perf-loop
Measures speed against a baseline, changes one thing, and measures again with an independent check.
Handing work to another agent: /enhance-prompt writes the prompt it needs, and /handoff-audit writes the checks it must pass.
Self-improving
When a workflow stumbles, /refine finds the cause and puts the fix into the skill itself.
Start your next
repository with it
Use the template for a new project, or add the skills to one you already have. Built for Claude Code and Codex.
Questions
What am I installing? +
A repository template with agent instructions, reusable skills, and project references. Read and change the files like the rest of your code.
Does it remember automatically? +
Memory lives in project files. Agents can read those files and record approved, useful lessons. What gets retained depends on your workflow and instructions.
Does every improvement apply to every project?+
Keep project-specific lessons with the project. Review broadly useful improvements before sharing them through the template.
Where does the human stay involved? +
You set the goal and decide what can run. Reviews and checks provide evidence; your authorization controls publishing, merging, and other external actions.
Can I use it with an existing project? +
The skills-only plugin works with Claude Code in an existing repository. For a new project or Codex support, use the full template. See the setup instructions .
How is this different from a CLAUDE.md file?+
A CLAUDE.md holds rules. Harness Firmware adds the rest around it: project memory the agent reads when it applies, skills for planning, review and long tasks, and checks that run on every change.
Does it add token overhead?+
Very little up front. Each session loads the core rules and a short index of skill names. Full skills and project notes load only when a task calls for them.