Skip to main content
Plan one governed change with Claude | beyond10xUse focused Agent Plugins and ESS to turn one feature idea into a validated system model, deterministic docs, and a scoped, critic-reviewed plan with visible blockers.try-spec-driven-developmentexperiencetry-spec-driven-developmentexperiencedeveloperadopterspec driven development claude

Try it · Experimental

Plan one governed change with Claude

Use focused Agent Plugins and ESS to turn one feature idea into a validated system model, deterministic docs, and a scoped, critic-reviewed plan with visible blockers.
Audience
Developer · Adopter
Expected time
About 30 minutes
Access
Public · 6 required artifacts
Finish with
Finish with a validated ESS model and generated docs, a scoped and critic-reviewed plan, and explicit blocker and evidence records; driven implementation remains optional and experimental.
Understand the governed loop

Adoption contract

Use the declared artifacts, versions, and access boundary.

This contract names the artifacts behind the path so documentation alone is not mistaken for a working runtime.
Primary path

Plan one governed change with Claude

Available now
Support: ExperimentalDeclared access: PublicEffective access: Public

Finish with a validated ESS model and generated docs, a scoped and critic-reviewed plan, and explicit blocker and evidence records; driven implementation remains optional and experimental.

Orientation time: about 30 minutes

Prerequisites

  • A Git repository
  • Claude Code
  • AEP 0.55.0 on PATH for a supported Linux or macOS target
  • Rust to build ESS 0.22.0 from its source tag, with ess on PATH

Required artifacts

  • Agentplugins DocumentationDocumentation · Available · Public
  • Agentplugins Release SourceVersion 0.9.0 · Source · Available · Public

    Pinned source release for focused Claude Code and Codex plugins. Model-backed AEP driving uses Metaharness; planning and specification work use AEP and ESS.

  • ESS DocumentationDocumentation · Available · Public
  • ESS CLI SourceVersion 0.22.0 · Source · Available · Public

    Build the ess-cli package from the 0.22.0 source tag with the repository's Rust toolchain. This release contains source only; no prebuilt CLI archives or checksum asset are published.

  • AEP DocumentationDocumentation · Available · Public
  • AEP CLI BinaryVersion 0.55.0 · Binary · Available · Public

    Choose one archive for your target: x86_64 or aarch64 Linux GNU, or x86_64 or aarch64 macOS. The release also publishes SHA256SUMS. No Windows archive is published.

01 · Learn

See the safety boundary before giving an agent work

Understand the boundary and prerequisites before running commands.

  1. Understand the governed loop

    Learn where model reasoning ends and specifications, permissions, reviews, and evidence begin.

    Complete when

    You can name which decisions belong to the model and which must remain explicit and inspectable.

    Open this step

02 · Do

Build the source-owned plan and specification

Follow the technical instructions in the repository that owns them.

  2. Build the governed first plan

    Use the repository-owned golden path to adopt, model, decompose, scope, run critics, and preserve the unresolved decision instead of guessing it.

    Complete when

    The ESS model and planning store validate, scopes retain their citations, critic verdicts are recorded, and the open decision blocker remains inspectable.

    Open this step

03 · Verify

Inspect the proof, then decide whether to implement

Check an observable outcome before treating the experience as complete.

  1. Inspect the evidence trail

    Check that claims about the work point to concrete outputs rather than a fluent transcript.

    Complete when

    You can distinguish a claimed result from evidence that another person or tool can verify.

    Open this step

  2. Choose whether to attempt implementation

    Treat the golden path's implementation wave and reference driver as optional experimental follow-ons: the published driven run does not reach completion today.

    Complete when

    You have made an explicit go or no-go decision; completing this planning path does not depend on launching or finishing a driven implementation.

    Open this step