SharperFlow Open Source

Advance

Spec-driven engineering infrastructure for AI-assisted development. OpenCode-first today, with Claude Code and ACP-first versions coming soon.

View on GitHub Read docs

governed agent loop

/adv-proposal add OAuth login

proposal scoped contract

planning approved task graph

apply red/green evidence

archive specs + wisdom saved

Vibe coding does not scale. Advance gives agents a contract: specs, gates, evidence, durable task state, and explicit human checkpoints.

What it gives you

Autonomy with engineering guardrails

Specs as laws

Durable capability requirements in .adv/specs/ anchor proposals, implementation, review, and archive.

7-gate delivery

Proposal, discovery, design, planning, execution, acceptance, and release all have explicit contracts.

Temporal orchestration

Change and task workflows survive process failure, compaction, worktree switches, and long-running sessions.

Evidence-first execution

TDD output, task checkpoints, review findings, and hardening results are recorded instead of claimed.

Worktree isolation

Implementation runs in per-change worktrees while shared ADV state keeps coordination durable.

Wisdom loop

Patterns, gotchas, conventions, and reflections survive the change that produced them.

Workflow

The 7 gates

proposal Confirm problem statement

discovery Approve objectives and acceptance criteria

design Validate architecture and tradeoffs

planning Approve task graph before autonomous work

execution Implement with TDD evidence and checkpoints

acceptance Review delivered work against the agreement

release Harden, archive, reflect, and finalize

Quick install

git clone https://github.com/Sharper-Flow/Advance.git
cd Advance
./scripts/deploy-local.sh --fix

Requires OpenCode and a local Temporal dev server. The deploy script syncs the plugin, commands, overlays, bundled agents, and skills into your OpenCode setup.

Credit where due

Inspired by strong ideas, extended for durable agent work

Beads

Inspired by: agent-friendly task memory, dependency-aware graphs, and ready-task discovery.

Advance adds: Advance binds task graphs to gates, TDD evidence, checkpoint commits, worktrees, and Temporal recovery.

Spec Kit

Inspired by: spec-driven phases that define what to build before implementation.

Advance adds: Advance adds durable gates, typed tools, contract review matrices, and release-stage enforcement.

OpenSpec

Inspired by: proposal, design, tasks, delta specs, and archive as a spec-promotion moment.

Advance adds: Advance makes the lifecycle stateful, auditable, Temporal-backed, and shared across worktrees.

OpenCode

Inspired by: local agents, slash-command workflows, plugins, sub-agents, and tool-mediated coding.

Advance adds: Advance narrows autonomy with spec law, gate contracts, tool-only state mutation, and auditable evidence.

Temporal

Inspired by: durable workflow execution, signal/query surfaces, and recovery after process failure.

Advance adds: Advance uses Temporal as the persistence spine for changes, tasks, gates, and recovery state.

Coming next

ACP-first and Claude Code versions

An ACP-first version is planned, with Zed as the editor surface we are most excited to use. We have not focused there first because OpenCode ACP still has blocking interaction bugs for ADV-style workflows — especially anomalyco/opencode#17920, where the question tool hangs in ACP mode. Advance relies on reliable proposal, agreement, prep, acceptance, archive, and cancellation checkpoints, so ACP needs dependable question/permission round-trips before it can be the primary path.

Shoutout Zed editor. Can't wait to use you.