A queue instead of sprints
The product owner ranks the approved features. A developer and their agent take the next one, so there are no sprints to plan and no board to groom.
KiwiPow Server
Specs an agent can build without guessing.
Work trackers track tickets. KiwiPow Server plans, reviews and accepts the requirement itself: every rule one provable sentence, every unknown a named question, every term the product's own and every source cited. The same spec is what the tester accepts against.
What KiwiPow Server does
Nothing left to guess
One provable sentence per behaviour, edge cases written out, and open questions that block approval. What, never how: no tasks, file names or technical steps.
Planned from your own sources
Word, PDF, Excel, Markdown, JSON and JSON Schema become citable sections. Every behaviour drawn from a document cites the section and version it came from.
Specs reviewed like code
Review rounds, strikes, answered questions and numbered revisions. Every comment is answered before approval, and struck stays struck.
The code talks back
Disagreements found in the code reach the requirement owner as decisions with up to three proposals, written as the text the behaviour would have instead.
Proof per behaviour
A behaviour counts as built only when a test proves it. A live board shows progress without a status meeting.
Acceptance behaviour by behaviour
The tester accepts or reopens each behaviour. A reopened one needs fresh evidence, and a verdict on text that later changed no longer counts.
Documents that stay current
A changed document flags every spec that cites it, old text beside new. An accepted spec lists the document sections it has overtaken.
Decisions made once
Answers that settle something for the whole product are kept as standing decisions, and the planner plans by them on every feature after.
One language per domain
An information model per product, read by the planner first and changed only when a feature is accepted. Specs use the product's own words.
Control
Your code, your models, your rules
Your code never leaves your machines
Mapping, building and testing happen in the IDE. The server receives decisions in words, tasks and proofs with a test name, never source code. Any Git host works.
Your models, your infrastructure
On premises with local models and your own OIDC identity provider, or SaaS with your own key or prepaid credits. Anthropic or any OpenAI-compatible endpoint.
Need to know, also for the AI
A classification ladder of your own. Documents above a user's clearance are absent, not locked, and the AI working for them is never cleared higher.
For regulated industries
From clause to verdict
In finance, insurance, pensions, healthcare, energy and the public sector, requirements are not invented. KiwiPow imports your laws, standards and policies as citable sections, and every feature is planned from them.
- Every behaviour cites the clause and the document version it was read from.
- When a regulation is amended, every spec citing a changed section is flagged with old and new text side by side.
- Each behaviour carries its citation, revision history, proving tests and the tester's verdict, so an auditor's question is answered from the spec.
- Runs fully on premises with local models.
- ClausePension act ยง12, version 2026-01
- BehaviourOne provable sentence, stable id
- RulingWhere the code disagreed, on the record
- TestNamed, against the approved revision
- VerdictAccepted by the person who asked
From empty tenant to first spec
A guided page takes a new team from sign-in to its first planned spec. Developers pair their IDE from the browser.