Ship the right thing,
not just something.
Spec-driven development workflows with team approval gates, EARS acceptance criteria, and a clean PM-to-engineering handoff. Three workflows scaled to the size of the work.
See it in action
From requirements to shipped PR in one structured flow.
Choose your workflow
Three workflows for three sizes of work. Vibe for small changes. Spec-Driven for features that need team alignment. Design-Driven for multi-week, multi-engineer features.
Bug fixes, quick changes. AI generates an implementation brief.
Requirements → Tech Spec → Design → Tasks, with approval gates.
Design doc decomposed into parallel blocks with a roadmap view.
Three workflows. One size doesn't fit all.
Match the process to the scope of the work. Over-engineering a bug fix wastes time. Under-speccing a major feature ships the wrong thing.
Write fast, ship now
Bug fixes, config changes, quick refactors. Describe what needs to happen — AI generates a focused implementation brief.
Best for: Scope is obvious, risk is low.
Team alignment before code
Requirements → Tech Spec → System Design → Task Specs, with team approval gates between each stage. Nothing moves forward without sign-off.
Best for: Standard features that need peer review.
Multiple engineers, in parallel
A hand-crafted design document decomposed into independent blocks. Each block gets its own mini-spec. A roadmap view shows the full dependency graph.
Best for: Large multi-week features, multiple engineers.
Built around team review
Every other spec tool is single-player. Fettink makes approval gates the core primitive — nothing advances until the right people sign off.
Approval gates
Configure how many reviewers must approve each stage before the next one can be generated. Self-approval optional. Change requests block progression until resolved.
EARS acceptance criteria
AI generates structured acceptance criteria in Easy Approach to Requirements Syntax — WHEN / THEN, WHILE / SHALL, IF / THEN. Every requirement is testable.
PM → Engineering handoff
PMs write plain-language requirements. AI converts them to EARS criteria. One click creates a spec-driven session pre-populated and ready for the engineering team.
GitHub integration
Link a PR to any session. Fettink posts your EARS criteria as a PR comment immediately and marks sessions complete when the PR merges.
Spec anchors & living docs
Tag named sections of your spec. Link blocks to anchors. When the spec changes, anchors are automatically flagged stale so nothing slips through.
Session forking
Completed sessions become reference points. Fork any session to start a related feature with inherited requirements and EARS criteria already in place.
Simple pricing
Free
$0
- ✓ Vibe workflow
- ✓ 3 sessions/mo
- ✓ Bring your own AI key
Pro
$29/mo
- ✓ All 3 workflows
- ✓ Unlimited sessions
- ✓ Approval gates
- ✓ EARS criteria
- ✓ GitHub integration
- ✓ Analytics
Enterprise
$59/mo
- ✓ Everything in Pro
- ✓ Brand voice rules
- ✓ Unlimited team members
- ✓ Priority support