The AmbyKit workflow

AmbyKit moves a feature idea through structured Spec-Driven Development phases. Each phase reads the artifacts before it and writes the next, so every decision is reviewable before code is written, and later phases reference earlier ones by stable ID rather than restating them. Five phases run for every feature; the constitution is written once per project, and clarify, revise, analyze, converge, and review run only when you need them.

The constitution is written once per project and its principles feed every feature. Each feature then runs five phases in sequence, each handing an artifact to the next: specify writes spec.md, design writes ui.md, plan writes plan.md, tasks writes tasks.md, and implement builds against them. Four more phases run only as needed: clarify resolves open questions in the spec, revise grows the spec in place, analyze cross-checks spec, plan, and tasks before you build, and converge checks the code against spec, plan, and tasks after implement, appending gap tasks until the feature converges. and review asks a different role to critique any artifact, returning findings by stable ID.

Solid arrows carry an artifact forward and always run. Dotted arrows run only when you need them.

−

100%

+Fit

Close

1 · ConstitutionDurable, cross-feature principles.

2 · SpecifyIdea → spec (stories, requirements).

3 · ClarifyResolve open questions in the spec.

4 · ReviseContinue an existing spec, in place.

5 · DesignUI, components, and design tokens.

6 · PlanThe technical HOW.

7 · TasksOrdered, dependency-aware checklist.

8 · AnalyzeCoverage + consistency check.

9 · ImplementExecute the tasks, track status.

10 · ConvergeVerify code against spec; append gap tasks.

11 · ReviewAnother role critiques an artifact, by ID.