Skip to main content
SDLC Harness is a repository-native SDLC governance tool for developers and coding agents. It keeps requirements, architecture decisions, feature state, dependencies, and verification evidence with the code, then uses executable gates to prevent incomplete or inconsistent delivery.
Read the adopt command reference →

Get started in 10 minutes

Generate the protocol in an existing or empty repository, enable the Git hook, and complete your first feature.

Why use it

Learn about common failure modes when coding agents work across sessions or in parallel.

Daily workflow

Follow the full path from selecting work through verification, review, completion, and session closeout.

Command reference

Look up every command, option, prerequisite, and state transition.

​
What it solves

Coding agents can change code quickly, but recurring problems appear when work spans sessions, devices, or multiple agents: context remains trapped in chat, features are declared complete too early, tests lose their connection to requirements, and multiple agents modify the same task. SDLC Harness makes the repository the single source of truth:
  • AGENTS.md and docs/workflow/ store the agent working protocol.
  • feature_list.json stores milestones, features, dependencies, status, claim, and evidence.
  • sdlc-harness verify executes the verification commands declared by a feature.
  • sdlc-harness review record records the outcome of an independent review.
  • sdlc-harness feature complete atomically checks completion conditions and updates feature state.
  • sdlc-harness validate audits the entire repository and blocks noncompliant commits with a nonzero exit code.
  • .harness/events/ stores an append-only audit log that can be synchronized through Git.

​
A trustworthy completion chain

​
Core capabilities

Agent-independent

Codex, Claude Code, and any other agent that can read repository files can follow the same protocol.

Evidence bound to code

Verification, review, and approval records bind to a commit or content hash, so a claim that something passed cannot replace evidence.

The same rules locally and in CI

The Git hook and CI run the same validate audit, with stable categories for failures.

Parallel collaboration

claim, leases, WIP limits, and Git worktree isolation reduce conflicts across people and agents.

End-to-end traceability

Requirements, user stories, acceptance criteria, features, and verification items form an auditable matrix.

A post-delivery feedback loop

Environment checks, deployment policies, and feedback logs extend the process into operations and improvement.

​
Scope and limits

SDLC Harness is a protocol and governance layer. It is not a test framework, coding agent, project management system, or proof that requirements are correct. It makes the process traceable, the evidence auditable, and the rules executable; your project still owns product judgment, test content, and deployment commands.

Get started

Add SDLC Harness to a repository and complete your first trustworthy delivery chain.