Files

T

jpmschweitzerandClaude Sonnet 4.6 cbe8b5b5ab chore(meta): plan Sprint 26: Clean House

13 tickets across server (5), copy (6), client (1), planning (1).
Sprint goal: ship voice pipeline to production via observer integration,
remove v0.1 dead weight, stabilize codebase. #648 cancelled as duplicate
of #658.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

2026-03-07 19:44:02 +01:00

2.3 KiB

Raw Blame History

Sprint 26: Clean House — Planning Tasks

Goal: Ship the voice pipeline to production by integrating observer, removing v0.1 dead weight, and stabilizing the codebase.

Branch: planning (or main — no code, docs only) Agents: Qatux (documenter), SI (project manager)

New Tickets

#	Title	Blocked by
#658	Update agent profiles and briefings for v0.2	—

Use tooling/db/ticket show <id> for full details.

Key Decisions

decisions/scope.md — D-114 (generator-first proof-of-life), D-117 (tycoon bookmark, zero investigation content), D-119 (generator spike Sprint 25 as critical path)
decisions/content.md — D-122 (all NPCs generated), D-128 (culture implicit in location), D-138 (LLM re-voicing pipeline)

Notes

#658 Update agent profiles and briefings for v0.2: Audit and update .claude/agents/ (20 files) and docs/briefings/ (18 files). Many still reference v0.1 detective/smuggler gameplay, hand-authored content pipeline, and pre-workshop assumptions. Specific removals: all references to Kael Davan, Sera Venn, smuggler/detective archetypes as playable characters, the v0.1 triangle configuration, the complicity framing (superseded by consequence per D-132). Specific additions: generator-first approach (D-114), all NPCs generated (D-122), voice pipeline (D-138), tycoon bookmark (D-117), Krenn culture as implicit starting context (D-128). Work through each agent briefing systematically — do not bulk-replace. Each agent has a different scope and different stale assumptions. After updating, cross-check: does any briefing still imply a playable detective or smuggler? Does any profile still describe the hand-authored content pipeline as the primary content creation method? Note: #648 (superseded by this ticket) was cancelled — its scope is included here.

Dependency Chain

#658 (update agent profiles and briefings) — standalone

PR Workflow

When ready to submit, commit to main directly (no code branch needed for doc-only changes), or create a PR from a short-lived branch:

tea pr create --repo jpmschweitzer/settled-reach --login schweitz --title "docs(briefings): update agent profiles and briefings for v0.2 pivot" --description "body" --base main --head planning

2.3 KiB Raw Blame History