MCP server and Agent Plugin packaging for goal-acceptance criteria

Framework-agnostic core for goal acceptance criteria and validation

Audits a spec for acceptance criteria that lack a concrete verification method (C1/P1).

OpenClaw native plugin for goal-acceptance criteria management

Verify GitHub pull requests against issue acceptance criteria using deterministic evidence from CI, diffs, and repository artifacts.

Review acceptance criteria across projects, and generate the scenario clauses your tests cite.

Acceptance Criteria emit helper for Vitest. Tag tests with tagAc(), emit pass/fail to a Memex workspace.

Acceptance-criteria-driven goal completion for autonomous agents — MCP server, dsh Cordis plugin, and OpenClaw plugin in one package.

Turn an agreement into verifiable acceptance criteria, verify fulfillment, and determine what was earned. Use Spoolis when payment depends on whether work actually passed. Produces signed outcome receipts: attestations of acceptance criteria, what passed,

Project-agnostic visual AI tester: captures what an app actually renders, judges it against UI best practices and per-project rules via the local Claude Code CLI, verifies acceptance criteria, and tracks findings in an adjudicated backlog.

Turn an agreement into verifiable acceptance criteria, verify fulfillment, and determine what was earned. Use Spoolis when payment depends on whether work actually passed.

Acceptance criteria scenarios on top of Vitest.

Match Acceptance Criteria Codes with the tests that test them

CLI tool that syncs markdown epics and user stories with Linear hierarchy and acceptance criteria

Visual feedback as agent work packets. Stakeholders drop pins on your live app; your AI coding agent reads each pin (selector, screenshot, DOM, thread, acceptance criteria) via MCP and ships the fix.

Read-only MCP access to versioned system specs: AsyncAPI, OpenAPI, ODCS data contracts and Gherkin acceptance criteria.

Local-first evidence primitive — record evidence with its acceptance criteria, re-derive integrity deterministically, and record independent third-party judgments. Never trusts a stored verdict, never lets work self-grade its own "done".

Verification gates for a Bun + Elysia + Drizzle + Turborepo modular monolith: pinned dependency declarations, acceptance-criteria coverage, work queue, screen wiring, prototype boundary, declared debt. Plain files in, exit code out — no dependencies.

Autonomous reviewer/merger: reviews the PRs Praktor opens against Boule's acceptance criteria, posts a GitHub review, and enables gated auto-merge — closing the Boule → Praktor → Krites loop.

Model-provider-neutral goal acceptance criteria and validation enforcement plugin for the DeepSeek Harness