SPEC v0.3: orchestrator resolutions of the plans' open points
Records D-004 and D-015 to D-025: shells and ownership, server seams (router middleware, rate_limit layer, tasks::start, AuditWriter and PushQueue traits, next_occurrence_date in kvitt-domain, M3 owns recurring generation, M4 lands after M3), OpenAPI parsed-value equality, feature convention and strings, empty fake scenario and resolveRange exception, shared ledger rows and editor fields in :core:design, no bundled font, pruning at 04:00, development infrastructure as M2c-dev built it, M2c-pi allowances, release keystore, production import procedure. Plans and prompts close their open points; HANDOFF rewritten to the real state; CLAUDE.md: implementation agents never edit SPEC.md or docs/decisions.md. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
+2
-2
@@ -4,9 +4,9 @@ You are an Opus implementation agent on Kvitt (repository `/Users/jhag/projects/
|
||||
|
||||
Read PLAN-M1.md and follow it; CLAUDE.md rules apply. SPEC.md wins over both.
|
||||
|
||||
Numbers you may use (from the orchestrator):
|
||||
Numbers you may use (from the orchestrator), for proposed entries in your report only; you never edit `SPEC.md` or `docs/decisions.md` (CLAUDE.md › Orchestration):
|
||||
- Next free decision id: {{NEXT_DECISION}}
|
||||
- Spec version for any spec change: {{SPEC_VERSION}}
|
||||
- Spec version a proposed spec change would get: {{SPEC_VERSION}}
|
||||
- Schema version for any schema change: {{SCHEMA_VERSION}}
|
||||
If a value is still a `{{…}}` placeholder, write `TODO(spec)` wherever the number would go and say so in the report.
|
||||
|
||||
|
||||
+3
-3
@@ -4,14 +4,14 @@ You are an Opus implementation agent on Kvitt (repository `/Users/jhag/projects/
|
||||
|
||||
Read PLAN-M10.md and follow it; CLAUDE.md rules apply. SPEC.md wins over both.
|
||||
|
||||
Numbers you may use (from the orchestrator):
|
||||
Numbers you may use (from the orchestrator), for proposed entries in your report only; you never edit `SPEC.md` or `docs/decisions.md` (CLAUDE.md › Orchestration):
|
||||
- Next free decision id: {{NEXT_DECISION}}
|
||||
- Spec version for any spec change: {{SPEC_VERSION}}
|
||||
- Spec version a proposed spec change would get: {{SPEC_VERSION}}
|
||||
- Schema version for any schema change: {{SCHEMA_VERSION}}
|
||||
If a value is still a `{{…}}` placeholder, write `TODO(spec)` wherever the number would go and say so in the report.
|
||||
|
||||
Orchestrator notes for this run:
|
||||
(To fill: Give the keystore parameters (algorithm, size, validity); name this agent as the one on the phone.)
|
||||
(To fill: Name this agent as the one on the phone. The keystore command is fixed in SPEC §10.6, D-024.)
|
||||
{{ORCHESTRATOR_NOTES}}
|
||||
|
||||
Essentials (the plan has the detail):
|
||||
|
||||
+3
-3
@@ -4,14 +4,14 @@ You are an Opus implementation agent on Kvitt (repository `/Users/jhag/projects/
|
||||
|
||||
Read PLAN-M11.md and follow it; CLAUDE.md rules apply. SPEC.md wins over both.
|
||||
|
||||
Numbers you may use (from the orchestrator):
|
||||
Numbers you may use (from the orchestrator), for proposed entries in your report only; you never edit `SPEC.md` or `docs/decisions.md` (CLAUDE.md › Orchestration):
|
||||
- Next free decision id: {{NEXT_DECISION}}
|
||||
- Spec version for any spec change: {{SPEC_VERSION}}
|
||||
- Spec version a proposed spec change would get: {{SPEC_VERSION}}
|
||||
- Schema version for any schema change: {{SCHEMA_VERSION}}
|
||||
If a value is still a `{{…}}` placeholder, write `TODO(spec)` wherever the number would go and say so in the report.
|
||||
|
||||
Orchestrator notes for this run:
|
||||
(To fill: Settle open points (a) to (c) below.)
|
||||
(To fill: Confirm the owner's allowance to act on the production Pi. Open points (a) to (c) are resolved in PLAN-M11 §4, SPEC v0.3, D-025.)
|
||||
{{ORCHESTRATOR_NOTES}}
|
||||
|
||||
Essentials (the plan has the detail):
|
||||
|
||||
+3
-3
@@ -4,14 +4,14 @@ You are an Opus implementation agent on Kvitt (repository `/Users/jhag/projects/
|
||||
|
||||
Read PLAN-M2a.md and follow it; CLAUDE.md rules apply. SPEC.md wins over both.
|
||||
|
||||
Numbers you may use (from the orchestrator):
|
||||
Numbers you may use (from the orchestrator), for proposed entries in your report only; you never edit `SPEC.md` or `docs/decisions.md` (CLAUDE.md › Orchestration):
|
||||
- Next free decision id: {{NEXT_DECISION}}
|
||||
- Spec version for any spec change: {{SPEC_VERSION}}
|
||||
- Spec version a proposed spec change would get: {{SPEC_VERSION}}
|
||||
- Schema version for any schema change: {{SCHEMA_VERSION}}
|
||||
If a value is still a `{{…}}` placeholder, write `TODO(spec)` wherever the number would go and say so in the report.
|
||||
|
||||
Orchestrator notes for this run:
|
||||
(To fill: Settle the plan's open points (a) to (f) in the notes below.)
|
||||
(To fill: Overrides only. The plan's open points (a) to (f) are resolved in PLAN-M2a §4, SPEC v0.3.)
|
||||
{{ORCHESTRATOR_NOTES}}
|
||||
|
||||
Essentials (the plan has the detail):
|
||||
|
||||
+3
-3
@@ -4,14 +4,14 @@ You are an Opus implementation agent on Kvitt (repository `/Users/jhag/projects/
|
||||
|
||||
Read PLAN-M2b.md and follow it; CLAUDE.md rules apply. SPEC.md wins over both.
|
||||
|
||||
Numbers you may use (from the orchestrator):
|
||||
Numbers you may use (from the orchestrator), for proposed entries in your report only; you never edit `SPEC.md` or `docs/decisions.md` (CLAUDE.md › Orchestration):
|
||||
- Next free decision id: {{NEXT_DECISION}}
|
||||
- Spec version for any spec change: {{SPEC_VERSION}}
|
||||
- Spec version a proposed spec change would get: {{SPEC_VERSION}}
|
||||
- Schema version for any schema change: {{SCHEMA_VERSION}}
|
||||
If a value is still a `{{…}}` placeholder, write `TODO(spec)` wherever the number would go and say so in the report.
|
||||
|
||||
Orchestrator notes for this run:
|
||||
(To fill: Settle the plan's open points (a) to (g) in the notes below; say whether this agent may use the phone.)
|
||||
(To fill: Say whether this agent may use the phone. The plan's open points (a) to (g) are resolved in PLAN-M2b §4, SPEC v0.3.)
|
||||
{{ORCHESTRATOR_NOTES}}
|
||||
|
||||
Essentials (the plan has the detail):
|
||||
|
||||
+4
-4
@@ -4,20 +4,20 @@ You are an Opus implementation agent on Kvitt (repository `/Users/jhag/projects/
|
||||
|
||||
Read PLAN-M2c-dev.md and follow it; CLAUDE.md rules apply. SPEC.md wins over both.
|
||||
|
||||
Numbers you may use (from the orchestrator):
|
||||
Numbers you may use (from the orchestrator), for proposed entries in your report only; you never edit `SPEC.md` or `docs/decisions.md` (CLAUDE.md › Orchestration):
|
||||
- Next free decision id: {{NEXT_DECISION}}
|
||||
- Spec version for any spec change: {{SPEC_VERSION}}
|
||||
- Spec version a proposed spec change would get: {{SPEC_VERSION}}
|
||||
- Schema version for any schema change: {{SCHEMA_VERSION}}
|
||||
If a value is still a `{{…}}` placeholder, write `TODO(spec)` wherever the number would go and say so in the report.
|
||||
|
||||
Orchestrator notes for this run:
|
||||
(To fill: State whether the agent may write `infra/secrets/` and `android/app/google-services.json` in the main checkout and run gcloud/firebase.)
|
||||
(To fill: Overrides only. The allowances (infra/secrets/ in the main checkout, the Google Cloud project kvitt-1337 through the REST API) are D-022.)
|
||||
{{ORCHESTRATOR_NOTES}}
|
||||
|
||||
Essentials (the plan has the detail):
|
||||
- First step: from the main checkout, `git worktree add .claude/worktrees/agent-m2c-dev -b agent-m2c-dev main`; work only there, on branch `agent-m2c-dev`; then copy the git-ignored files the plan names.
|
||||
- Edit only `infra/**` (dev parts), plus git-ignored secrets in the main checkout if allowed below; anything else is a contract request to the orchestrator.
|
||||
- Gate: `docker compose -f infra/dev/compose.yaml config`, shellcheck, `/health` from Mac and phone, one local backup. Report only results you ran in this session.
|
||||
- Gate: `docker compose -f infra/dev/compose.yaml --env-file infra/dev/.env.example config`, `shellcheck $(find infra -name '*.sh')`, `/health` from the Mac, one local backup; the phone check is a HUMAN step. Report only results you ran in this session.
|
||||
- Stop and ask when the plan says so, when a step could touch the owner's real data, or when the spec is ambiguous in a way that changes a decision.
|
||||
- Commit on your branch when the gate is green, `git rebase main`, rerun the gate. Never merge, push or remove the worktree.
|
||||
|
||||
|
||||
+3
-3
@@ -4,14 +4,14 @@ You are an Opus implementation agent on Kvitt (repository `/Users/jhag/projects/
|
||||
|
||||
Read PLAN-M2c-pi.md and follow it; CLAUDE.md rules apply. SPEC.md wins over both.
|
||||
|
||||
Numbers you may use (from the orchestrator):
|
||||
Numbers you may use (from the orchestrator), for proposed entries in your report only; you never edit `SPEC.md` or `docs/decisions.md` (CLAUDE.md › Orchestration):
|
||||
- Next free decision id: {{NEXT_DECISION}}
|
||||
- Spec version for any spec change: {{SPEC_VERSION}}
|
||||
- Spec version a proposed spec change would get: {{SPEC_VERSION}}
|
||||
- Schema version for any schema change: {{SCHEMA_VERSION}}
|
||||
If a value is still a `{{…}}` placeholder, write `TODO(spec)` wherever the number would go and say so in the report.
|
||||
|
||||
Orchestrator notes for this run:
|
||||
(To fill: Give the OQ-3 answers and settle open points (a) to (c) below; runs after M8, before M10.)
|
||||
(To fill: Give the OQ-3 answers and the allowances the owner granted for the Kvitt Pi, the Home Assistant Pi, Gitea and Google Drive (D-023); runs after M8, before M10. Open points (a) to (c) are resolved in PLAN-M2c-pi §4.)
|
||||
{{ORCHESTRATOR_NOTES}}
|
||||
|
||||
Essentials (the plan has the detail):
|
||||
|
||||
+3
-3
@@ -4,14 +4,14 @@ You are an Opus implementation agent on Kvitt (repository `/Users/jhag/projects/
|
||||
|
||||
Read PLAN-M3.md and follow it; CLAUDE.md rules apply. SPEC.md wins over both.
|
||||
|
||||
Numbers you may use (from the orchestrator):
|
||||
Numbers you may use (from the orchestrator), for proposed entries in your report only; you never edit `SPEC.md` or `docs/decisions.md` (CLAUDE.md › Orchestration):
|
||||
- Next free decision id: {{NEXT_DECISION}}
|
||||
- Spec version for any spec change: {{SPEC_VERSION}}
|
||||
- Spec version a proposed spec change would get: {{SPEC_VERSION}}
|
||||
- Schema version for any schema change: {{SCHEMA_VERSION}}
|
||||
If a value is still a `{{…}}` placeholder, write `TODO(spec)` wherever the number would go and say so in the report.
|
||||
|
||||
Orchestrator notes for this run:
|
||||
(To fill: Settle the plan's open points (a) to (d) below (M3/M4 coupling first).)
|
||||
(To fill: Overrides only. Open points (a) to (d) are resolved in PLAN-M3 §4, SPEC v0.3, D-015.)
|
||||
{{ORCHESTRATOR_NOTES}}
|
||||
|
||||
Essentials (the plan has the detail):
|
||||
|
||||
+3
-3
@@ -4,14 +4,14 @@ You are an Opus implementation agent on Kvitt (repository `/Users/jhag/projects/
|
||||
|
||||
Read PLAN-M4.md and follow it; CLAUDE.md rules apply. SPEC.md wins over both.
|
||||
|
||||
Numbers you may use (from the orchestrator):
|
||||
Numbers you may use (from the orchestrator), for proposed entries in your report only; you never edit `SPEC.md` or `docs/decisions.md` (CLAUDE.md › Orchestration):
|
||||
- Next free decision id: {{NEXT_DECISION}}
|
||||
- Spec version for any spec change: {{SPEC_VERSION}}
|
||||
- Spec version a proposed spec change would get: {{SPEC_VERSION}}
|
||||
- Schema version for any schema change: {{SCHEMA_VERSION}}
|
||||
If a value is still a `{{…}}` placeholder, write `TODO(spec)` wherever the number would go and say so in the report.
|
||||
|
||||
Orchestrator notes for this run:
|
||||
(To fill: Settle the plan's open points (a) to (c) below.)
|
||||
(To fill: Overrides only. Open points (a) to (c) are resolved in PLAN-M4 §4, SPEC v0.3; M4 lands after M3.)
|
||||
{{ORCHESTRATOR_NOTES}}
|
||||
|
||||
Essentials (the plan has the detail):
|
||||
|
||||
+2
-2
@@ -4,9 +4,9 @@ You are an Opus implementation agent on Kvitt (repository `/Users/jhag/projects/
|
||||
|
||||
Read PLAN-M5.md and follow it; CLAUDE.md rules apply. SPEC.md wins over both.
|
||||
|
||||
Numbers you may use (from the orchestrator):
|
||||
Numbers you may use (from the orchestrator), for proposed entries in your report only; you never edit `SPEC.md` or `docs/decisions.md` (CLAUDE.md › Orchestration):
|
||||
- Next free decision id: {{NEXT_DECISION}}
|
||||
- Spec version for any spec change: {{SPEC_VERSION}}
|
||||
- Spec version a proposed spec change would get: {{SPEC_VERSION}}
|
||||
- Schema version for any schema change: {{SCHEMA_VERSION}}
|
||||
If a value is still a `{{…}}` placeholder, write `TODO(spec)` wherever the number would go and say so in the report.
|
||||
|
||||
|
||||
+3
-3
@@ -4,14 +4,14 @@ You are an Opus implementation agent on Kvitt (repository `/Users/jhag/projects/
|
||||
|
||||
Read PLAN-M6.md and follow it; CLAUDE.md rules apply. SPEC.md wins over both.
|
||||
|
||||
Numbers you may use (from the orchestrator):
|
||||
Numbers you may use (from the orchestrator), for proposed entries in your report only; you never edit `SPEC.md` or `docs/decisions.md` (CLAUDE.md › Orchestration):
|
||||
- Next free decision id: {{NEXT_DECISION}}
|
||||
- Spec version for any spec change: {{SPEC_VERSION}}
|
||||
- Spec version a proposed spec change would get: {{SPEC_VERSION}}
|
||||
- Schema version for any schema change: {{SCHEMA_VERSION}}
|
||||
If a value is still a `{{…}}` placeholder, write `TODO(spec)` wherever the number would go and say so in the report.
|
||||
|
||||
Orchestrator notes for this run:
|
||||
(To fill: Confirm U2 approval, the §9.7 hex spec change, font clearance, and open point (a) below.)
|
||||
(To fill: Confirm U2 approval and that the §9.7 colour change has landed in SPEC. Open points (a) to (c) are resolved in PLAN-M6 §4, SPEC v0.3.)
|
||||
{{ORCHESTRATOR_NOTES}}
|
||||
|
||||
Essentials (the plan has the detail):
|
||||
|
||||
+2
-2
@@ -4,9 +4,9 @@ You are an Opus implementation agent on Kvitt (repository `/Users/jhag/projects/
|
||||
|
||||
Read PLAN-M7a.md and follow it; CLAUDE.md rules apply. SPEC.md wins over both.
|
||||
|
||||
Numbers you may use (from the orchestrator):
|
||||
Numbers you may use (from the orchestrator), for proposed entries in your report only; you never edit `SPEC.md` or `docs/decisions.md` (CLAUDE.md › Orchestration):
|
||||
- Next free decision id: {{NEXT_DECISION}}
|
||||
- Spec version for any spec change: {{SPEC_VERSION}}
|
||||
- Spec version a proposed spec change would get: {{SPEC_VERSION}}
|
||||
- Schema version for any schema change: {{SCHEMA_VERSION}}
|
||||
If a value is still a `{{…}}` placeholder, write `TODO(spec)` wherever the number would go and say so in the report.
|
||||
|
||||
|
||||
+2
-2
@@ -4,9 +4,9 @@ You are an Opus implementation agent on Kvitt (repository `/Users/jhag/projects/
|
||||
|
||||
Read PLAN-M7b.md and follow it; CLAUDE.md rules apply. SPEC.md wins over both.
|
||||
|
||||
Numbers you may use (from the orchestrator):
|
||||
Numbers you may use (from the orchestrator), for proposed entries in your report only; you never edit `SPEC.md` or `docs/decisions.md` (CLAUDE.md › Orchestration):
|
||||
- Next free decision id: {{NEXT_DECISION}}
|
||||
- Spec version for any spec change: {{SPEC_VERSION}}
|
||||
- Spec version a proposed spec change would get: {{SPEC_VERSION}}
|
||||
- Schema version for any schema change: {{SCHEMA_VERSION}}
|
||||
If a value is still a `{{…}}` placeholder, write `TODO(spec)` wherever the number would go and say so in the report.
|
||||
|
||||
|
||||
+2
-2
@@ -4,9 +4,9 @@ You are an Opus implementation agent on Kvitt (repository `/Users/jhag/projects/
|
||||
|
||||
Read PLAN-M7c.md and follow it; CLAUDE.md rules apply. SPEC.md wins over both.
|
||||
|
||||
Numbers you may use (from the orchestrator):
|
||||
Numbers you may use (from the orchestrator), for proposed entries in your report only; you never edit `SPEC.md` or `docs/decisions.md` (CLAUDE.md › Orchestration):
|
||||
- Next free decision id: {{NEXT_DECISION}}
|
||||
- Spec version for any spec change: {{SPEC_VERSION}}
|
||||
- Spec version a proposed spec change would get: {{SPEC_VERSION}}
|
||||
- Schema version for any schema change: {{SCHEMA_VERSION}}
|
||||
If a value is still a `{{…}}` placeholder, write `TODO(spec)` wherever the number would go and say so in the report.
|
||||
|
||||
|
||||
+2
-2
@@ -4,9 +4,9 @@ You are an Opus implementation agent on Kvitt (repository `/Users/jhag/projects/
|
||||
|
||||
Read PLAN-M7d.md and follow it; CLAUDE.md rules apply. SPEC.md wins over both.
|
||||
|
||||
Numbers you may use (from the orchestrator):
|
||||
Numbers you may use (from the orchestrator), for proposed entries in your report only; you never edit `SPEC.md` or `docs/decisions.md` (CLAUDE.md › Orchestration):
|
||||
- Next free decision id: {{NEXT_DECISION}}
|
||||
- Spec version for any spec change: {{SPEC_VERSION}}
|
||||
- Spec version a proposed spec change would get: {{SPEC_VERSION}}
|
||||
- Schema version for any schema change: {{SCHEMA_VERSION}}
|
||||
If a value is still a `{{…}}` placeholder, write `TODO(spec)` wherever the number would go and say so in the report.
|
||||
|
||||
|
||||
+2
-2
@@ -4,9 +4,9 @@ You are an Opus implementation agent on Kvitt (repository `/Users/jhag/projects/
|
||||
|
||||
Read PLAN-M7e.md and follow it; CLAUDE.md rules apply. SPEC.md wins over both.
|
||||
|
||||
Numbers you may use (from the orchestrator):
|
||||
Numbers you may use (from the orchestrator), for proposed entries in your report only; you never edit `SPEC.md` or `docs/decisions.md` (CLAUDE.md › Orchestration):
|
||||
- Next free decision id: {{NEXT_DECISION}}
|
||||
- Spec version for any spec change: {{SPEC_VERSION}}
|
||||
- Spec version a proposed spec change would get: {{SPEC_VERSION}}
|
||||
- Schema version for any schema change: {{SCHEMA_VERSION}}
|
||||
If a value is still a `{{…}}` placeholder, write `TODO(spec)` wherever the number would go and say so in the report.
|
||||
|
||||
|
||||
+2
-2
@@ -4,9 +4,9 @@ You are an Opus implementation agent on Kvitt (repository `/Users/jhag/projects/
|
||||
|
||||
Read PLAN-M7f.md and follow it; CLAUDE.md rules apply. SPEC.md wins over both.
|
||||
|
||||
Numbers you may use (from the orchestrator):
|
||||
Numbers you may use (from the orchestrator), for proposed entries in your report only; you never edit `SPEC.md` or `docs/decisions.md` (CLAUDE.md › Orchestration):
|
||||
- Next free decision id: {{NEXT_DECISION}}
|
||||
- Spec version for any spec change: {{SPEC_VERSION}}
|
||||
- Spec version a proposed spec change would get: {{SPEC_VERSION}}
|
||||
- Schema version for any schema change: {{SCHEMA_VERSION}}
|
||||
If a value is still a `{{…}}` placeholder, write `TODO(spec)` wherever the number would go and say so in the report.
|
||||
|
||||
|
||||
+3
-3
@@ -4,14 +4,14 @@ You are an Opus implementation agent on Kvitt (repository `/Users/jhag/projects/
|
||||
|
||||
Read PLAN-M8.md and follow it; CLAUDE.md rules apply. SPEC.md wins over both.
|
||||
|
||||
Numbers you may use (from the orchestrator):
|
||||
Numbers you may use (from the orchestrator), for proposed entries in your report only; you never edit `SPEC.md` or `docs/decisions.md` (CLAUDE.md › Orchestration):
|
||||
- Next free decision id: {{NEXT_DECISION}}
|
||||
- Spec version for any spec change: {{SPEC_VERSION}}
|
||||
- Spec version a proposed spec change would get: {{SPEC_VERSION}}
|
||||
- Schema version for any schema change: {{SCHEMA_VERSION}}
|
||||
If a value is still a `{{…}}` placeholder, write `TODO(spec)` wherever the number would go and say so in the report.
|
||||
|
||||
Orchestrator notes for this run:
|
||||
(To fill: Confirm the extra `:app` deliverables (PLAN §4 note); name this agent as the one on the phone.)
|
||||
(To fill: Name this agent as the one on the phone. The extra `:app` deliverables are M8's per SPEC §11.2 v0.3.)
|
||||
{{ORCHESTRATOR_NOTES}}
|
||||
|
||||
Essentials (the plan has the detail):
|
||||
|
||||
+2
-2
@@ -4,9 +4,9 @@ You are an Opus implementation agent on Kvitt (repository `/Users/jhag/projects/
|
||||
|
||||
Read PLAN-M9.md and follow it; CLAUDE.md rules apply. SPEC.md wins over both.
|
||||
|
||||
Numbers you may use (from the orchestrator):
|
||||
Numbers you may use (from the orchestrator), for proposed entries in your report only; you never edit `SPEC.md` or `docs/decisions.md` (CLAUDE.md › Orchestration):
|
||||
- Next free decision id: {{NEXT_DECISION}}
|
||||
- Spec version for any spec change: {{SPEC_VERSION}}
|
||||
- Spec version a proposed spec change would get: {{SPEC_VERSION}}
|
||||
- Schema version for any schema change: {{SCHEMA_VERSION}}
|
||||
If a value is still a `{{…}}` placeholder, write `TODO(spec)` wherever the number would go and say so in the report.
|
||||
|
||||
|
||||
+10
-9
@@ -1,8 +1,8 @@
|
||||
# Start prompts
|
||||
|
||||
One ready-to-paste start prompt per plan (`PLAN-<id>.md` at the repository root), plus `ORCHESTRATOR-prompt.md`. Before pasting, the orchestrator fills `{{NEXT_DECISION}}`, `{{SPEC_VERSION}}`, `{{SCHEMA_VERSION}}` (disjoint ranges for agents that run in parallel, CLAUDE.md › Numbering) and `{{ORCHESTRATOR_NOTES}}` (answers to the plan's open points, phone assignment, overrides). `U2.md` also takes `{{OWNER_PICK_AND_COMMENTS}}`. U1 and U2 run in the owner's own Claude session on branch `agent-ux`.
|
||||
One ready-to-paste start prompt per plan (`PLAN-<id>.md` at the repository root), plus `ORCHESTRATOR-prompt.md`. Before pasting, the orchestrator fills `{{NEXT_DECISION}}`, `{{SPEC_VERSION}}`, `{{SCHEMA_VERSION}}` (disjoint ranges for agents that run in parallel, CLAUDE.md › Numbering) and `{{ORCHESTRATOR_NOTES}}` (answers to the plan's open points, phone assignment, overrides). `U2.md` also takes `{{OWNER_PICK_AND_COMMENTS}}`. U1 and U2 run in the owner's own Claude session in `~/orca/workspaces/kvitt/UX-sprint` on branch `UX-sprint`. The numbers are for proposed entries in agents' reports: implementation agents never edit `SPEC.md` or `docs/decisions.md`; a docs agent records what the orchestrator accepts (CLAUDE.md › Orchestration).
|
||||
|
||||
Dependencies follow SPEC §11.1 and §11.2 (v0.2, D-001). Status as of 2026-10-17: M0 done, M1 landed (`c6df2ab`).
|
||||
Dependencies follow SPEC §11.1 and §11.2 (v0.3). Status as of 2026-10-17: M0 done, M1 landed (`c6df2ab`), M2c-dev landed (`c885aba`); M2a and M2b in flight; U1 in the owner's session. The plans' open points are resolved in SPEC v0.3 and recorded in each plan's §4.
|
||||
|
||||
## Dependency order and waves
|
||||
|
||||
@@ -14,10 +14,10 @@ Plans in the same wave can run in parallel (they own disjoint paths, SPEC §14.7
|
||||
| 0 | U1 UX directions | `U1.md` | M0 | everything in waves 0 to 2 (owner's session) |
|
||||
| 1 | M2a Server skeleton and `kvitt-domain` | `M2a.md` | M1 | M2b, M2c-dev, U1/U2 |
|
||||
| 1 | M2b Android skeleton and `:domain` | `M2b.md` | M1 | M2a, M2c-dev, U1/U2 |
|
||||
| 1 | M2c-dev Infra for development | `M2c-dev.md` | M0 (its health check needs M2a's image) | M2a, M2b, U1/U2 |
|
||||
| 1 | M2c-dev Infra for development | `M2c-dev.md` | M0 (its health check needs M2a's image) | done (`c885aba`) |
|
||||
| 1 | U2 UX design spec | `U2.md` | U1 and the owner's pick | M2a, M2b, M2c-dev, wave 2 |
|
||||
| 2 | M3 Server core API | `M3.md` | M2a | M4 (see coupling below), M5, M6 |
|
||||
| 2 | M4 Server sync, audit, push, scheduler | `M4.md` | M2a | M3, M5, M6 |
|
||||
| 2 | M3 Server core API | `M3.md` | M2a | M4 (M4 lands after M3), M5, M6 |
|
||||
| 2 | M4 Server sync, audit, push, scheduler | `M4.md` | M2a; lands after M3 (D-015) | M3, M5, M6 |
|
||||
| 2 | M5 Android data layer | `M5.md` | M1, M2b | M3, M4, M6 |
|
||||
| 2 | M6 Design system | `M6.md` | U2 approved, M2b, the §9.7 colour spec change | M3, M4, M5 |
|
||||
| 3 | M7a Feature onboarding | `M7a.md` | M6 | M7b to M7f, M9 |
|
||||
@@ -34,8 +34,9 @@ Plans in the same wave can run in parallel (they own disjoint paths, SPEC §14.7
|
||||
|
||||
## Constraints the orchestrator must keep in mind
|
||||
|
||||
- **M3 and M4 are coupled** through recurring generation (E-28 generates a due period; §9.5 logic, audit writer and push queue are M4's). Decide the interface before starting both (PLAN-M3 open point a, PLAN-M4 open point b), or land M4's generation function first.
|
||||
- **M2a and M2b need the stub-file decisions** in their notes before starting (PLAN-M2a open points a to f, PLAN-M2b open points a to g): they create files in directories §14.7 gives to later milestones.
|
||||
- **M7a to M7f** need M2b's feature convention (Hilt or not, navigation callbacks) and M6's shared components (ledger rows, expense form fields) settled first.
|
||||
- **M3 and M4** (D-015): M2a provides `next_occurrence_date`, the `AuditWriter`/`PushQueue` traits with no-op implementations and `tasks::start`; M3 writes the recurring generation function and calls the traits; M4 replaces the implementations, its scheduler calls M3's function, and M4 lands after M3.
|
||||
- **M2a and M2b** create shell files and modules in later milestones' paths (D-004); ownership passes on when they land.
|
||||
- **M7a to M7f** follow the feature convention of SPEC §6.2 (D-017) and take the ledger rows and expense editor fields from M6's `:core:design` (D-019).
|
||||
- **M6** starts only after the §9.7 colour change from U2's proposal has landed in SPEC (§11.1).
|
||||
- **Phone:** M2b (one `installDebug`), M5 (only if instrumented tests), M8 and M10 use the phone; only one at a time, named in the notes.
|
||||
- **Outside the repository:** M2c-dev (gcloud, Firebase, secrets in the main checkout), M2c-pi (SSH to the Pi, Gitea, Drive), M8 (dev server on the Mac), M10 and M11 (production) need the owner's allowance in the notes.
|
||||
- **Outside the repository:** M2c-dev (D-022, done), M2c-pi (the Kvitt Pi, the Home Assistant Pi, Gitea, Drive: allowances requested at the start of that sprint, D-023), M8 (dev server on the Mac), M10 and M11 (production) need the owner's allowance in the notes.
|
||||
|
||||
+4
-4
@@ -7,11 +7,11 @@ Read PLAN-U1.md and follow it; CLAUDE.md rules apply. SPEC.md wins over both. Yo
|
||||
Numbers (normally none are needed for UX work): next decision {{NEXT_DECISION}}, spec version {{SPEC_VERSION}}, schema version {{SCHEMA_VERSION}}. If a value is still a `{{…}}` placeholder, write `TODO(spec)` wherever a number would go.
|
||||
|
||||
Setup and limits:
|
||||
- Work on branch `agent-ux` in the worktree `.claude/worktrees/agent-ux`: from the main checkout, `git worktree add .claude/worktrees/agent-ux -b agent-ux main`, then `git reset --hard main` inside it. Do not use any other branch or worktree (an old `UX-sprint` branch exists elsewhere; ignore it).
|
||||
- Work on branch `UX-sprint` in the worktree `~/orca/workspaces/kvitt/UX-sprint` (the owner's separate session); `git rebase main` before reporting. Do not use any other branch or worktree.
|
||||
- Commit only files under `docs/ux/`. Edit nothing else, SPEC.md and CLAUDE.md included.
|
||||
- Deliver 2 or 3 directions per SPEC §13.4 phase 1: HTML in a 411 dp phone frame, the six screens S-4, S-7, S-5, S-9, S-11, S-8 in light and dark, Swedish copy, realistic data for Jacob and Anna, PNG exports, and `docs/ux/directions/README.md` with the comparison and your recommendation.
|
||||
- No external requests except Google Fonts for a font that may be bundled in an Android app. No placeholder text.
|
||||
- No external requests except Google Fonts. The app bundles no font and uses the Material 3 default typeface (D-020). No placeholder text.
|
||||
- Stop and ask before installing any tool (for example a headless browser for PNG export).
|
||||
- Commit on `agent-ux`, `git rebase main`. Never merge, push or remove the worktree.
|
||||
- Commit on `UX-sprint`, `git rebase main`. Never merge, push or remove the worktree.
|
||||
|
||||
Report: end with the report described in PLAN-U1.md §10: branch, head commit hash, files produced with PNG counts, fonts and licences, your recommendation in one line, open questions and spec gaps with section numbers, and the owner's next step ("Review 2-3 directions, pick one, give comments") with the PNG paths.
|
||||
Report: end with the report described in PLAN-U1.md §10: branch, head commit hash, files produced with PNG counts, typography, your recommendation in one line, open questions and spec gaps with section numbers, and the owner's next step ("Review 2-3 directions, pick one, give comments") with the PNG paths.
|
||||
|
||||
+5
-5
@@ -10,10 +10,10 @@ The owner's pick and comments on the U1 directions:
|
||||
{{OWNER_PICK_AND_COMMENTS}}
|
||||
|
||||
Setup and limits:
|
||||
- Work on branch `agent-ux` in `.claude/worktrees/agent-ux`. If that worktree still exists (U1 not landed), continue there and `git rebase main`; otherwise, from the main checkout, `git worktree add .claude/worktrees/agent-ux -b agent-ux main`, then `git reset --hard main` inside it.
|
||||
- Work on branch `UX-sprint` in `~/orca/workspaces/kvitt/UX-sprint` (the owner's separate session); `git rebase main` before reporting.
|
||||
- Commit only files under `docs/ux/`. Edit nothing else; the §9.7 colour change is a proposal file, the orchestrator changes SPEC.md.
|
||||
- Deliver `docs/ux/design-spec.md` (tokens, components, every screen S-1 to S-22 with every §13.3 state or "not applicable"), `docs/ux/strings.csv` (`key,en,sv,notes`, every string), `docs/ux/screens/` PNGs, `docs/ux/colour-tokens-proposal.md`.
|
||||
- Gate: every string key has `en` and `sv`; every screen has all states of §13.3.
|
||||
- Stop and ask before installing any tool. Commit on `agent-ux`, `git rebase main`. Never merge, push or remove the worktree.
|
||||
- Deliver `docs/ux/design-spec.md` (tokens, components, every screen S-1 to S-22 with its list of §13.3 states, each specified or "not applicable"), keys prefixed by feature module (D-017), `docs/ux/strings.csv` (`key,en,sv,notes`, every string), `docs/ux/screens/` PNGs, `docs/ux/colour-tokens-proposal.md`.
|
||||
- Gate: every string key has `en` and `sv`; every screen has every state `design-spec.md` lists for it.
|
||||
- Stop and ask before installing any tool. Commit on `UX-sprint`, `git rebase main`. Never merge, push or remove the worktree.
|
||||
|
||||
Report: end with the report described in PLAN-U2.md §10: branch, head commit hash, gate self-check lines, how each owner comment was addressed, the proposed colour values, fonts and licences, open questions and spec gaps with section numbers, and the owner's next step ("Approve the design spec").
|
||||
Report: end with the report described in PLAN-U2.md §10: branch, head commit hash, gate self-check lines, how each owner comment was addressed, the proposed colour values, typography, open questions and spec gaps with section numbers, and the owner's next step ("Approve the design spec").
|
||||
|
||||
Reference in New Issue
Block a user