Project Overview
Live status of the documentation → harness → code pipeline
Spec Completeness
68%
▲ 12% this week
Tasks Completed
2 / 8
T-002 in review
Gate Pass Rate
87%
▼ 1 retry on T-006
Open Questions
3
due before M1
Recent Activity
✅
T-002 · Data layer + migrations passed verification gate2h ago · executor-01 · 3 files changed
📝
PRD §6 Success Metrics updated — North Star set to "weekly active teams"Yesterday · by you
§
ADR-003 Auth strategy accepted — OAuth2 + short-lived JWTs2 days ago · reviewed by Eng Lead
⚠️
T-006 failed contract test, retry 1/3 with error feedbackToday 09:14 · orchestrator
Spec Readiness
68%ready to build
Complete PRD + Scope + Spec checklists to reach 100%
Documentation Pyramid
Why → What → How. Check items off to raise the readiness score.
00 · PRD Reviewed
01 · Scope Draft
02 · Tech Spec Draft
💡 Why scope is its own document
The PRD justifies the build; the Scope fences it; the Tech Spec makes it executable; the harness enforces it. The Scope doc is what you paste into the agent's system prompt when it starts to drift — every "explicitly out of scope" line is a hallucination you prevent.
Tech Spec — Sections
Click a section to expand. Status: DRAFT → REVIEWED → ACTIVE
Task Board
One task = one PR = one concern. Click a card to inspect & run.
Orchestrator
Spec-driven loop: pick task → build context → execute → verify → advance
1 · Pick Tasktopo-sort WBS
→
2 · Build Contextspec + task + deps
→
3 · Executeexecutor agent
→
4 · Verify Gatetests · lint · build
→
5 · AdvancePR + state update
[orchestrator] ready. state.json loaded — 8 tasks, 2 done. Click "Run Next Task".
Gate Configuration
Typecheckblocking
Unit testsblocking
Contract testsblocking
Lintblocking
Security scanwarn only
Max retries3
Human checkpointsschema · auth · arch
💡 Failed gate? The error output is injected into the retry prompt. If a task needs >2 clarifications, the spec is the bug — fix the doc, not the prompt.
Decision Log (ADRs)
Append-only. Decisions get superseded, never deleted.
Orchestration Architecture
From-scratch component map of the harness
┌──────────────────────────────────────────┐
│ DOCS (source of truth) │
│ 00-prd · 01-scope · 02-tech-spec │
│ tasks/ · ADRs/ · contracts/ │
└──────────────────┬───────────────────────┘
│ read-only for agents
┌──────────────────▼───────────────────────┐
│ ORCHESTRATOR │
│ task scheduler (topo-sort WBS graph) │
│ prompt builder · state store · │
│ human checkpoint policy │
└────┬─────────────┬──────────────┬────────┘
│ │ │
┌─────▼────┐ ┌─────▼─────┐ ┌─────▼─────┐
│ PLANNER │ │ EXECUTOR │ │ REVIEWER │
│ agent │ │ agent(s) │ │ agent │
└─────┬────┘ └─────┬─────┘ └─────┬─────┘
└─────────────┼──────────────┘
┌──────▼───────┐
│ VERIFY GATE │ typecheck · tests · lint
│ PASS ▶ PR │ FAIL ▶ retry ≤3 ▶ human
└──────────────┘Build order
1. Docs
2. State store
3. Loop
2. State store
3. Loop
Roles
Executor ≠ Reviewer
(fresh context)
(fresh context)
Context
Per-task slice,
never full history
never full history
Escalation
3 failures →
human checkpoint
human checkpoint