docslisted

Documentation bootstrapper for mature-but-undocumented repos — the 'read then ask' lane. Reads the codebase FIRST (structure, manifests, routes/entrypoints/models/migrations, existing README, git-log themes) and drafts a 'what this system appears to do' map where every inference is marked ⚠ UNVERIFIED → interviews the owner in ONE batched question table (each question carries what the code suggests, what is ambiguous, and a proposed answer acceptable in one word) → writes the standard oracle the other lanes assume exists: specs INDEX + per-area shards (DRAFT-FROM-CODE vs OWNER-CONFIRMED), decisions.md seeds, knowledge-base.md seeds, known-issues.md → proposes a vteam.config.yaml patch (high_stakes_terms/paths, specs.sources, docs.task_context) for the owner to apply. Writes documentation only — never product code, never the config itself.
connorpham/vteam-harness · ★ 6 · Data & Documents · score 81

Install: claude install-skill connorpham/vteam-harness

> **Model routing for this tool** (from `model-routing.data.yaml`, snapshot 2026-08-17): > `frontier` → **fable** · `workhorse` → **opus** · `standard` → **sonnet** · `utility` → **haiku** > Roles → tiers: ba-challenger: standard · ba-draft: standard · dev-r1: workhorse · dev-r2: standard (high-stakes: workhorse) · dev-r3: workhorse · explore: utility · qa-challenger: standard · sa-background: workhorse · sa-challenger: workhorse · sa-writer: workhorse > Resolve at runtime: `python3 .vteam/scripts/model_route.py <role> --tool claude-code [--high-stakes]` — high-stakes diffs (review.high_stakes_*) bump dev-r2 to the workhorse tier. > Spawning a subagent: pass the resolved name as the Agent tool's `model` parameter. # /docs — create the documented truth the gates assume (docs lane, no code) **Why this exists:** every other vteam lane reads an oracle. /ba shards a spec, /dev cites `docs/specs/<feature>.md`, /qa derives expected values from it, and the review gate escalates on `review.high_stakes_terms`. A mature repo that grew without documentation has none of that — so the gates either idle or fire on nothing. This workflow CREATES that oracle from the only two sources that actually hold it: **the codebase** and **the owner's head**. It does not require documentation to pre-exist; it manufactures it, then says out loud which parts are still guesses. **What this workflow is NOT:** it never writes or edits product code, never touches `vteam.config.yaml` (it PROPOSES a patch,