Recipes: reusable agent behavior without copy-paste prompts
Recipes improve Agentplane by packaging repeatable agent behavior as inspectable repository assets instead of opaque prompt blobs.
Read →Field notes
Agentplane Blog
Release notes, workflow deep dives, and implementation guidance.
Context management: the LLM Wiki pattern inside the repo
Agentplane adapts Andrej Karpathy's LLM Wiki idea for software repositories, where context becomes a reviewed artifact instead of another cache.
Read →Blueprints: routes for agent work that should not be improvised
Blueprints make Agentplane better by turning repeated work into explicit routes with scope, evidence, checks, and recovery paths.
Read →Agent Change Record: evidence for agent work
ACR v0.1 gives coding-agent work a deterministic, machine-readable evidence artifact.
Read →Audit layer: why coding agents need evidence
Agentplane's 0.4 recipe work is not just extensibility. It is the start of a repository-native audit layer for coding-agent changes.
Read →Agentplane 0.4.1: hosted close and release evidence
Agentplane 0.4.1 tightened branch_pr closure, release evidence, and hosted PR handoff.
Read →Agentplane 0.4.0: modular prompts and recipe-ready agents
Agentplane 0.4.0 turns prompts into compiled, addressable modules so recipes can target behavior instead of replacing whole instruction files.
Read →Roadmap to 0.4: modular prompts and recipes
A short development note on what the 0.3 line changed, why it took so many patches, and why modular prompt assembly is the right boundary for 0.4.
Read →Agentplane 0.3.8 and 0.3.9: preparing 0.4 and fixing installability
Why 0.3.8 spent its budget on internal cleanup for 0.4 and 0.5, how a leaked workspace dependency broke npm installs, and how 0.3.9 turned installability into a hard release gate.
Read →Agentplane 0.3.7: legacy recovery and safer publishing
What changed in Agentplane 0.3.7, in plain language: older repos recover more predictably, Redmine-backed task state gets less lossy, and the release path becomes stricter from local gate to npm.
Read →Agentplane 0.3.5: README v3 and projection-first backends
What changed in Agentplane 0.3.5, in plain language: README v3 became the active contract, docs pages got calmer on wide layouts, and Redmine-backed repos stopped hiding network reads inside ordinary task commands.
Read →Agentplane 0.3.4: install-first startup and upgrade repair
What changed in Agentplane 0.3.4, in plain language: npm-installed startup got self-contained, upgrade now restores workflow artifacts, and role guidance lines up with installed prompts.
Read →Agentplane 0.3.3: runtime hardening and README v3
What changed in Agentplane 0.3.3, in plain language: clearer runtime diagnostics, a real README v3 migration path, and less friction in local development.
Read →Agentplane 0.3.2: smoother upgrades and cleaner finish
What Agentplane 0.3.2 changes in everyday terms: easier upgrades, automatic clean closure in direct mode, and saner behavior inside the framework repo.
Read →Agentplane 0.3.1: publish recovery and cleaner docs
A practical look at Agentplane 0.3.1: fixing the blocked 0.3.x publish path and cleaning up docs and website surfaces.
Read →Agentplane 0.3.0: policy gateway and stricter release discipline
What changed in Agentplane 0.3.0, in plain language: clearer policy routing, better release notes, and safer reruns.
Read →Agentplane 0.2.25: safer commits and cleaner release flow
How the previous release tightened commit scope, publish validation, and documentation checks.
Read →