Fast agent-assisted delivery can lose the decisions, constraints, and verification that explain why a change was made. Reviews also become less credible when the implementation context reviews its own work.
Product
Private BuildKeel
Durable decisions and fresh-context review for agent-assisted work
Keel is a portable workflow for planning consequential work, handing implementation back to the host, reviewing the committed scope from a fresh context, and recording the actual outcome without introducing another orchestration runtime.
Keel supplies three instruction-only skills—plan, review, and close—around one tracked task record. Git remains the history and concurrency mechanism, while implementation stays in the developer’s existing agent host and toolchain.
A lightweight decision record makes important work easier to approve, review independently, and understand later without turning every task into process overhead.
Workflow
Plan, work, review, close
Each task moves through four explicit states, with approval before implementation and a fresh context responsible for review.
- 01
Plan
Explore the task, record the goal and decisions, then stop for human approval.
- 02
Work
Implement through the host’s ordinary workflow and commit the complete review scope.
- 03
Review
Inspect the committed scope and focused verification from a fresh context without fixing it.
- 04
Close
Preserve the actual outcome, durable reasoning, verification, and one next action.
Who it is for
- Developers working with coding agents
- Technical leads reviewing consequential changes
- Small teams that want durable engineering decisions
- Teams using Pi, Codex, or Claude Code
Use cases
- Plan a non-trivial change and stop for human approval
- Give a fresh context a narrow committed review scope
- Preserve verification and the actual outcome after review
- Share one workflow across supported coding-agent hosts
Explore all 8 technical features
- A concise plan record with goal, constraints, decisions, tasks, and review scope
- Explicit approval before implementation begins
- Fresh-context review against a recorded base revision and committed scope
- Closeout that records verification, durable reasoning, outcome, and one next action
- Instruction-only skills with no CLI, database, journal, model router, or runtime dependency
- Portable workflow for Pi, Codex, and Claude Code
- Git-backed history and ordinary Markdown records
- A deliberate skip path for trivial work where ceremony adds no value
Build with the lab
Build with Keel
Have a focused use case for Keel? Green Harbor Labs can help shape the integration, workflow, or prototype.