Specify
Reference for Akka Specify, the Spec-driven development tooling: the commands you run from an AI coding assistant, and the concepts behind them.
Commands
The commands are used from within an AI coding assistant (such as Claude Code) after installing the Akka plugin.
Configure your environment (CLI, Java, Maven, Akka tokens) |
|
Create or update the project constitution |
|
Supply a prompt to produce your feature spec |
|
Find gaps in your spec |
|
Convert your spec into a technical implementation plan |
|
Itemize the work required to build according to the spec |
|
Cross-artifact consistency and quality analysis |
|
Generate a custom checklist for the current feature |
|
Generate the required code, tests, harnesses, etc. |
|
Generate the enterprise-configuration assets the policy requires |
|
Assess the codebase against spec, plan, and tasks and queue remaining work |
|
Review code against spec, plan, and constitution |
|
Build, test, and run locally with hot reloading |
|
Inspect a running service’s runtime state against the spec |
|
Add or remove resilience-testing instrumentation for the service |
|
Deploy to Akka Automated Operations |
|
Convert tasks into GitHub issues |
|
Show the definition-of-done rollup and current phase |
|
Run the auditors and return the definition-of-done verdict |
|
Run the auditors for the requested ship target and, on pass, run the organization’s ship steps |
|
Switch between Enforced and À la carte modes |
|
Generate rendered project documentation into |
Concepts
-
Exit condition schema — the fields of an exit condition.
-
Exit condition states — the three states, the two
openreasons, the properties, and the drift model. -
Prohibitions — NEVER conditions, and why an unaudited one reds.
-
Default exit-condition library — the built-in conditions and their ids.
-
Requirement analysis — how feedback becomes a checkable exit condition.
-
Auditors — how a check is authored and bound to a condition.
-
Auditor kinds — introspective, provisioned, and delegated checks.
-
Project surface coverage — the code, harness, and doc surfaces a build must account for.
-
The coverage gate —
PROC-AUDITOR-COVERAGEover every surface. -
The adequacy review —
PROC-ADEQUACY-REVIEWED, the adversarial check of the checks. -
Attestations — recorded receipts that resolve delegated checks.
-
Content governance — exit conditions over generated prose.
-
Exit condition catalog — further candidate conditions to consider, by type.
-
Policies — the enterprise governance controls, defined as policy-as-code.