pedroknigge

Orderfield — Development skill for Claude Code

Development community

Contract kernel for multi-agent software work.

How to install Orderfield

This entry records only its repository, not the path inside it, so there is no exact command to give. Open pedroknigge/orderfield and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Orderfield does

Contract kernel for multi-agent software work. The plan lives on disk. Children cannot rewrite it. Close is proof.

Alternatives in Development

Claude Coder — Kodu is an autonomous coding agent that lives in your IDE 5.2k ★
Dev — Switch to Dev Work mode - optimized for software development 2.8k ★
Claudes C Compiler — Claude Opus 4.6 wrote a dependency-free C compiler in Rust, with backends targeting x86 (64- and 32-bit), ARM 2.6k ★

README

   ___  ____  ____  _____ ____  _____ ___ _____ _     ____
  / _ \|  _ \|  _ \| ____|  _ \|  ___|_ _| ____| |   |  _ \
 | | | | |_) | | | |  _| | |_) | |_   | ||  _| | |   | | | |
 | |_| |  _ <| |_| | |___|  _ <|  _|  | || |___| |___| |_| |
  \___/|_| \_\____/|_____|_| \_\_|   |___|_____|_____|____/

     anyone can persist a plan. only the leader may change it.

Anyone can persist a plan. Only the leader may change it.

The chat can die. ORDER stays. Children cannot rewrite the mission, the phase, the constraints, or done-when.

**After `/clear`, without a leader-owned field**

Agent: I don't have the earlier plan. What were we building?

**After `/clear`, with Orderfield**

`of resume` prints `next`. The mission on disk did not change. A child residual cannot rewrite it.

v0.7.99 · contract kernel · MIT · Python 3.11+ stdlib · Agent Skill interface

Typical problems → what Orderfield does

Orderfield keeps a software plan on disk so the work can continue after chat ends, tokens run out, or you change model or CLI. Children get bounded packets with exclusive owners. They cannot rewrite the mission, the phase, the constraints, or done-when.

Problem	Orderfield
A long or complex implementation prompt with steps that must be respected	The brief lives on disk as SPEC. Packs bind each step. The plan is not reinvented mid-flight.
You find an error or a gap mid-run	It becomes an amend, a patch, or a residual. The next packet carries it. It is not lost in ch