Works with GitHub Spec Kit and AWS Kiro

Operational transparency, straight from your specs.

Connect a GitHub repository. OT reads the specs already in it and drafts the outcomes, operations pages, registers and readiness report your stakeholders need. Your team confirms it, and every save is a pull request.

Read only until you choose to save. Nothing reaches your default branch without a merged pull request.

Illustration: OT reads a spec file, builds an outcome chain from business outcome to build items, and marks the business outcome confirmed when its pull request is merged.

How it works

From specs to a confirmed operating picture in three steps.

  1. 01

    Connect

    Sign in with GitHub and pick a repository. OT finds the Spec Kit or Kiro specs, tasks, commits and pull requests that are already there.

  2. 02

    Draft

    Claude works backwards from the specs to business outcomes, operations pages, registers and a readiness report. Everything it proposes is marked inferred until a person confirms it.

  3. 03

    Confirm

    Edit and confirm in OT. Every save opens a pull request that updates .ot/ and patches the specs, so developers keep building from the current plan. Merging is the approval.

A GitHub Action keeps OT current on every merge.

What you get

Four views of the same truth, all traced back to your specs.

ORS

Outcome chain

Business outcome to operations outcome to requirement to build item, each with acceptance criteria and how it is measured.

GOF

Operations pages

One clear operating page per outcome: who runs it, how it is checked and when it is next reviewed.

Registers

Risks, decisions and more

Risks, decisions, changes, benefits and delegations, seeded from your specs and kept in step with every merge.

Readiness

Readiness and gaps

Traceability metrics and a plain list of what is missing before you go live.

Principles

Claude drafts. People decide.

ExtractedInferredDraftConfirmed

Every record shows where it came from

Extracted from a spec, inferred by Claude, drafted in OT, confirmed by a person or retired. Claude never overwrites what a person has confirmed.

Your repo is the record

OT lives in a .ot folder in your repository. The app keeps only accounts and unsaved drafts. Client data stays with you.

Nothing lands without review

OT never pushes to your default branch. Changes arrive as labelled pull requests, and the merge is recorded in the change register.

Same input, same output

Scans are deterministic, so pull request diffs show only real change. Specs are patched line by line, never rewritten.

Your specs already describe the plan. Let everyone see it.