forth-ai-harness

|

What it does

WorkOS-native product-lifecycle harness. Six commands carry a feature from idea to shipped, hook-enforced at every gate: /fspec (interview -> one-page bilingual contract, EARS acceptance criteria, human approval gate), /fbuild (worktree, red-lock-green TDD with a hard AC-coverage gate, concurrent builds isolated per issue, a bug fast lane that skips the /fspec bounce, fresh-context evaluator), /fverify (independent verifier exercises every criterion on the live stack -- local by default, or a real deployed staging host via --staging with a gated magic-otp login -- mocks off, a product-only UAT checklist plus a technical acceptance brief for the tech lead), /fship (two-lens human acceptance -- product and technical, each handoff-able -- merge and authorship gates, deploy verification), /fstatus (read-only sweep naming who each item is waiting on, concurrent builds and coverage included), /flessons (proposes lesson diffs as real, previewable edits, applied only with your approval). The law: nothing merges without real-stack, per-criterion evidence from an agent that did not build the feature -- no n/a escapes, and a human is never asked to re-execute what an agent already proved. Domain skills for the WorkOS agent layer and DIKW memory layer ship in the box. GitHub is SSoT; a prose LESSONS.md compounds learning across runs.