jpmschweitzer/settled-reach
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat(meta): replace sprint workflow with kanban + milestones (D-221)

Browse Source 
Sprint-based workflow (38 sprints) replaced by kanban + milestones.
Milestones are many-to-many with tickets and can block each other.

New: /whats-next skill (dependency-driven batch selection with Si
refinement review), /pr-process skill (renamed from pr-push, adds
review comment pickup), clerk agent + pre-push hook for D-record
consistency checks.

Deleted: sprint CLI, sprint-start/sprint-plan/sprint-status skills,
team-scoped file restrictions. Si rewritten as refinement manager.
All 19 agent briefings updated from stale PROJECT_STATE.md reference
to live ticket milestone queries.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
jpmschweitzer
2026-05-03 20:11:00 +02:00
co-authored by Claude Opus 4.6
parent 287f9ba3a6
commit e6a557e8e7
48 changed files with 1164 additions and 2158 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/briefings/araminta.md
+2 -1
View File
@@ -11,7 +11,8 @@ updated: 2026-03-13
Last updated: 2026-03-13
## Current Project State
See [PROJECT_STATE.md](../../PROJECT_STATE.md) for shared project state (cascade phase, sprint, decision count).
Check active milestones: `tooling/db/ticket milestone list`
Check your tickets: `tooling/db/ticket list --assigned araminta`
## v0.2 Pivot — Key Changes for Your Role
The visual system shifts from designing layouts for three hand-crafted social sites to designing the visual grammar that the generator uses to produce legible zones at scale.
docs/briefings/burnelli-sheldon.md
+2 -1
View File
@@ -11,7 +11,8 @@ updated: 2026-04-05
Last updated: 2026-04-05
## Current Project State
See [PROJECT_STATE.md](../../PROJECT_STATE.md) for shared project state (cascade phase, sprint, decision count).
Check active milestones: `tooling/db/ticket milestone list`
Check your tickets: `tooling/db/ticket list --assigned burnelli-sheldon`
## Your Domain
docs/briefings/clerk.md
+42
View File
@@ -0,0 +1,42 @@
---
title: "Clerk - Project Briefing"
description: "Pre-push institutional guardrail — checks D-record consistency, ticket drift, decision contradictions, and Q-record surfacing before code lands"
type: briefing
status: active
agent: Clerk
updated: 2026-05-03
---
# Clerk - Project Briefing
Last updated: 2026-05-03
## Role: Pre-Push Institutional Guardrail
Review branch changes before push to catch institutional drift: decision contradictions, ticket scope creep, missing D-records for new behavior, and unresolved Q-records that should block merge.
## What to Check
1. **D-record consistency** — do the branch changes align with referenced D-records? Does any new code or content introduce behavior that contradicts a confirmed decision?
2. **Ticket drift** — does the work on the branch match the ticket description and acceptance criteria, or has scope crept?
3. **Decision contradictions** — do any two D-records referenced by this branch contradict each other? Has a D-record been amended elsewhere but not reflected in the branch?
4. **Q-record surfacing** — are there open Q-records (questions) that this branch implicitly resolves or depends on? If so, flag them for explicit resolution before merge.
## Where to Find Decisions
- **Decision index:** `decisions/README.md` — master index of all domain files
- **Domain files:** `decisions/architecture.md`, `decisions/perception.md`, `decisions/content.md`, `decisions/scope.md`, `decisions/economics.md`, `decisions/process.md`
- **Open questions:** `decisions/questions.md`, `decisions/questions-process.md`
- **Rejected proposals:** `decisions/rejected.md`
- **Decision DB table:**
```bash
tooling/db/sqlite-query "SELECT id, title, status, domain FROM decisions WHERE domain = '<domain>'"
```
## Output
Write findings to `.cache/pre-push-review.md`. End with a binary verdict:
- **APPROVED** — no institutional issues found, safe to push
- **REJECTED** — list each issue with the D/Q-record reference and what needs resolution
The findings file is gitignored (lives in `.cache/`) and is consumed by the push workflow.
docs/briefings/dudley.md
+2 -1
View File
@@ -11,7 +11,8 @@ updated: 2026-03-13
Last updated: 2026-03-13
## Current Project State
See [PROJECT_STATE.md](../../PROJECT_STATE.md) for shared project state (cascade phase, sprint, decision count).
Check active milestones: `tooling/db/ticket milestone list`
Check your tickets: `tooling/db/ticket list --assigned dudley`
## Status
STANDBY. This briefing will be populated when backend/engine implementation begins. Dudley activates when simulation implementation work is assigned.
docs/briefings/gestalt.md
+2 -1
View File
@@ -11,7 +11,8 @@ updated: 2026-03-13
Last updated: 2026-03-13
## Current Project State
See [PROJECT_STATE.md](../../PROJECT_STATE.md) for shared project state (cascade phase, sprint, decision count).
Check active milestones: `tooling/db/ticket milestone list`
Check your tickets: `tooling/db/ticket list --assigned gestalt`
## Key Design Pivots
- **Tycoon bookmark (D-117):** Zero investigation content. Tycoon (small business owner) is the starting state.
docs/briefings/gore.md
+2 -1
View File
@@ -11,7 +11,8 @@ updated: 2026-03-13
Last updated: 2026-03-13
## Current Project State
See [PROJECT_STATE.md](../../PROJECT_STATE.md) for shared project state (cascade phase, sprint, decision count).
Check active milestones: `tooling/db/ticket milestone list`
Check your tickets: `tooling/db/ticket list --assigned gore`
## v0.2 Pivot — Key Changes for Your Role
The workshop confirmed and sharpened the thematic frame. "Is this enough?" survives as the central question. The change is that it now must be posed through a generated tycoon's life, not through authored detective/smuggler characters.
docs/briefings/hoshe.md
+2 -1
View File
@@ -11,7 +11,8 @@ updated: 2026-03-13
Last updated: 2026-03-13
## Current Project State
See [PROJECT_STATE.md](../../PROJECT_STATE.md) for shared project state (cascade phase, sprint, decision count).
Check active milestones: `tooling/db/ticket milestone list`
Check your tickets: `tooling/db/ticket list --assigned hoshe`
## Status
**ACTIVE.** Test infrastructure from earlier sprints is operational. v0.2 focus: generator output validation — can the generator produce legible NPCs? Are relationships readable from generator output?
docs/briefings/justine.md
+2 -1
View File
@@ -11,7 +11,8 @@ updated: 2026-03-13
Last updated: 2026-03-13
## Current Project State
See [PROJECT_STATE.md](../../PROJECT_STATE.md) for shared project state (cascade phase, sprint, decision count).
Check active milestones: `tooling/db/ticket milestone list`
Check your tickets: `tooling/db/ticket list --assigned justine`
## Status
**ACTIVE.** CI and build pipeline maintenance. Content validation infrastructure remains relevant as the AI-assisted content pipeline (D-123) produces NPC content at scale.
docs/briefings/mellanie.md
+2 -1
View File
@@ -11,7 +11,8 @@ updated: 2026-03-13
Last updated: 2026-03-13
## Current Project State
See [PROJECT_STATE.md](../../PROJECT_STATE.md) for shared project state (cascade phase, sprint, decision count).
Check active milestones: `tooling/db/ticket milestone list`
Check your tickets: `tooling/db/ticket list --assigned mellanie`
## v0.2 Pivot — Key Changes for Your Role
The copy pipeline fundamentally shifts from hand-authoring specific NPC profiles to designing the culture-driven voice system that feeds the generator.
docs/briefings/miri.md
+2 -1
View File
@@ -11,7 +11,8 @@ updated: 2026-03-13
Last updated: 2026-03-13
## Current Project State
See [PROJECT_STATE.md](../../PROJECT_STATE.md) for shared project state (cascade phase, sprint, decision count).
Check active milestones: `tooling/db/ticket milestone list`
Check your tickets: `tooling/db/ticket list --assigned miri`
## v0.2 Pivot — Key Changes for Your Role
The workshop confirmed Sova Transit District as the v0.2 setting (tycoon bookmark in Van Maanen's Star) and resolved the culture architecture gap in Miri's favour.
docs/briefings/nigel.md
+2 -1
View File
@@ -11,7 +11,8 @@ updated: 2026-03-13
Last updated: 2026-03-13
## Current Project State
See [PROJECT_STATE.md](../../PROJECT_STATE.md) for shared project state (cascade phase, sprint, decision count).
Check active milestones: `tooling/db/ticket milestone list`
Check your tickets: `tooling/db/ticket list --assigned nigel`
## v0.2 Pivot — Key Changes for Your Role
The replayability frame shifts from "same conspiracy, different character lens" to "same generator, different seeded world." The anti-metagaming goal survives; the mechanism changes.
docs/briefings/oscar.md
+2 -1
View File
@@ -11,7 +11,8 @@ updated: 2026-03-13
Last updated: 2026-03-13
## Current Project State
See [PROJECT_STATE.md](../../PROJECT_STATE.md) for shared project state (cascade phase, sprint, decision count).
Check active milestones: `tooling/db/ticket milestone list`
Check your tickets: `tooling/db/ticket list --assigned oscar`
## Status
STANDBY. This briefing will be populated when networking/multiplayer implementation begins.
docs/briefings/ozzie.md
+2 -1
View File
@@ -11,7 +11,8 @@ updated: 2026-03-13
Last updated: 2026-03-13
## Current Project State
See [PROJECT_STATE.md](../../PROJECT_STATE.md) for shared project state (cascade phase, sprint, decision count).
Check active milestones: `tooling/db/ticket milestone list`
Check your tickets: `tooling/db/ticket list --assigned ozzie`
## v0.2 Pivot — Key Changes for Your Role
The workshop revealed a core framing error: the game was built as a detective puzzle game but the vision is a single-character life sim. The fix is not cosmetic.
docs/briefings/paula.md
+2 -1
View File
@@ -11,7 +11,8 @@ updated: 2026-03-13
Last updated: 2026-03-13
## Current Project State
See [PROJECT_STATE.md](../../PROJECT_STATE.md) for shared project state (cascade phase, sprint, decision count).
Check active milestones: `tooling/db/ticket milestone list`
Check your tickets: `tooling/db/ticket list --assigned paula`
## v0.2 Pivot — Key Changes for Your Role
docs/briefings/qatux.md
+2 -1
View File
@@ -11,7 +11,8 @@ updated: 2026-03-13
Last updated: 2026-03-13
## Current Project State
See [PROJECT_STATE.md](../../PROJECT_STATE.md) for shared project state (cascade phase, sprint, decision count).
Check active milestones: `tooling/db/ticket milestone list`
Check your tickets: `tooling/db/ticket list --assigned qatux`
## Decisions Relevant to Your Role
All decisions (D-001 through D-137) — maintains decision domain files in `decisions/` as the canonical record. Indexes and retrieves decision context for the team.
docs/briefings/si.md
+49 -53
View File
@@ -1,66 +1,62 @@
---
title: "Si - Project Briefing"
description: "Sprint and project manager — owns sprint planning, ticket tracking, v0.2 critical path dependency chain, and CI pipeline awareness for definition of done"
description: "Refinement manager — assesses ticket readiness, ensures sufficient context before work begins, surfaces missing D/Q-records and unresolved dependencies"
type: briefing
status: active
agent: Si
updated: 2026-03-13
updated: 2026-05-03
---
# Si - Project Briefing
Last updated: 2026-03-13
Last updated: 2026-05-03
## Current Project State
See [PROJECT_STATE.md](../../PROJECT_STATE.md) for shared project state (cascade phase, sprint, decision count).
Check active milestones: `tooling/db/ticket milestone list`
Check your tickets: `tooling/db/ticket list --assigned si`
## Role: Refinement Manager
Assess whether tickets have enough context to be worked. A ticket is ready when:
- It has a **clear outcome** — the agent can tell when the work is done
- All referenced **D-records are unambiguous** and confirmed (not draft, not contradicted)
- No **conflicting Q-records** remain open that would change the ticket's direction
- All **referenced artifacts exist** (files, schemas, specs mentioned in the ticket or its D-records)
If any of these conditions fail, the ticket is not ready. Flag what is missing and who owns the resolution.
## Where to Find Decisions
- **Decision index:** `decisions/README.md` — lists all domain files and how to query them
- **Domain files:** `decisions/architecture.md`, `decisions/perception.md`, `decisions/content.md`, `decisions/scope.md`, `decisions/economics.md`, `decisions/process.md`
- **Open questions:** `decisions/questions.md` (Q-NNN), `decisions/questions-process.md` (Q-NNN process)
- **Rejected proposals:** `decisions/rejected.md` (R-NNN)
- **Decision DB queries:**
```bash
tooling/db/decision show D-NNN # Show a specific decision
tooling/db/decision check-dupes "title" # Check for duplicates before creating
```
## Where to Find Workshop Outcomes
Workshop outputs live at `docs/workshops/<workshop-name>/`:
- `workshop-outcomes.md` — final summary with confirmed D-records
- Round files — per-round notes and participant outputs
- Check these when a ticket references a workshop decision to verify the full context is captured
## What "Enough Context" Means
A ticket has enough context when an agent can pick it up cold and deliver without asking clarifying questions. Concretely:
1. **Outcome is testable** — "implement X" has acceptance criteria; "design Y" has a deliverable format
2. **D-records are stable** — no open Q-record that could reverse the referenced D-record
3. **Dependencies are met** — if the ticket says "blocked by Miri's zone spec," that spec exists or the ticket stays in backlog
4. **Scope is bounded** — the ticket does not silently depend on cascade phases that have not been reached (see D-166 development cascade in CLAUDE.md)
## Key Commands
## Decisions Relevant to Your Role
All decisions across all domains. Read `decisions/README.md` for the index. Query decisions DB for sprint planning:
```bash
make decisions-coverage # Decision-to-ticket coverage by domain
make decisions-orphan # Decisions without implementing tickets
make decisions-active # List all active decisions
tooling/db/ticket list --status backlog # Candidates for refinement
tooling/db/ticket show <id> # Full ticket details
tooling/db/decision show D-NNN # Check a referenced decision
tooling/db/sqlite-query "SELECT * FROM decisions WHERE status = 'open'" # Open decisions
```
## Open Questions Assigned to You
All open questions - tracks as tickets for assignment and progress monitoring.
## Development Cascade (D-166)
Development follows a strict 6-phase cascade. Currently in Phase 1 (wiki content). Generator spike (D-119) is Phase 5.
**Prerequisites that must exist before/during the generator spike:**
1. Miri: Zone identity spec + Van Maanen's Star culture profile — blocks voice, NPC gen, AI pipeline
2. Araminta: Zone visual grammar, tile palettes — blocked by Miri zone identity spec
3. Tyre: NpcBlueprint struct design — generator output format
4. Mellanie: Culture-primary voice cards — blocked by Miri culture profile
**Dependency chain:**
```
Miri: Zone Identity Spec + Van Maanen's Star Culture Profile
|-- Araminta: zone visual grammar, tile palettes
|-- Tyre: generator zone template parameters, NpcBlueprint
|-- Mellanie: culture-primary voice cards
v
Tyre: Generator Spike (Sprint 25)
|-- Produces: auto-generated location + NPCs
v
Test: Can the player read NPC relationships from generator output?
```
**Estimated timeline (Tyre):** 7 sprints to proof-of-life playtest (generated location + legible characters + tycoon bookmark from creation to Day 3).
## Current Priorities
Consult `docs/sprints/` for current sprint briefing. Break v0.2 decisions (D-114 through D-137) into tickets if not already covered. Track dependencies above.
## Development Workflow
See `docs/DEVOPS.md` for full procedures. Key awareness for sprint planning:
- `make ci` must pass before any PR merges — definition of done includes CI green
- `make ci-server` = lint-server → build-server → test-server
- `make ci-client` = lint-client → build-client → test-client
- Server work lives in `server/`, client work in `client/`, cross-boundary tests in `tests/`
- Hoshe's test plans target these directories per D-030 testing architecture
## Key Documents
- decisions/ - domain-split decision files (see decisions/README.md for index)
- docs/DEVOPS.md - build, test, lint, CI procedures
- docs/discussions/ - archived rounds
- TEAM.md - team roster
docs/briefings/stig.md
+2 -1
View File
@@ -11,7 +11,8 @@ updated: 2026-03-13
Last updated: 2026-03-13
## Current Project State
See [PROJECT_STATE.md](../../PROJECT_STATE.md) for shared project state (cascade phase, sprint, decision count).
Check active milestones: `tooling/db/ticket milestone list`
Check your tickets: `tooling/db/ticket list --assigned stig`
## Status
**ACTIVE.** v0.2 brings a character customisation UI requirement and removes the dual-character variant for insert/HUD.
docs/briefings/tiger.md
+2 -1
View File
@@ -11,7 +11,8 @@ updated: 2026-03-13
Last updated: 2026-03-13
## Current Project State
See [PROJECT_STATE.md](../../PROJECT_STATE.md) for shared project state (cascade phase, sprint, decision count).
Check active milestones: `tooling/db/ticket milestone list`
Check your tickets: `tooling/db/ticket list --assigned tiger`
## Status
STANDBY. This briefing will be populated when localization work begins.
docs/briefings/troblum.md
+2 -1
View File
@@ -11,7 +11,8 @@ updated: 2026-03-13
Last updated: 2026-03-13
## Current Project State
See [PROJECT_STATE.md](../../PROJECT_STATE.md) for shared project state (cascade phase, sprint, decision count).
Check active milestones: `tooling/db/ticket milestone list`
Check your tickets: `tooling/db/ticket list --assigned troblum`
## Decisions Relevant to Your Role
- D-010: Architectural baseline - four principles
docs/briefings/tyre.md
+2 -1
View File
@@ -11,7 +11,8 @@ updated: 2026-03-13
Last updated: 2026-03-13
## Current Project State
See [PROJECT_STATE.md](../../PROJECT_STATE.md) for shared project state (cascade phase, sprint, decision count).
Check active milestones: `tooling/db/ticket milestone list`
Check your tickets: `tooling/db/ticket list --assigned tyre`
## Decisions Relevant to Your Role
Read `decisions/architecture.md` (primary) and `decisions/perception.md` (secondary). Key decisions: