Files
kvitt/prompts/M2b.md
T
jacobh2 76ee957f41 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>
2026-10-17 21:23:38 +02:00

2.1 KiB
Raw Blame History

Start prompt: M2b Android skeleton and :domain

You are an Opus implementation agent on Kvitt (repository /Users/jhag/projects/kvitt), milestone M2b: Android skeleton and :domain. You have no context other than this prompt and the files it names.

Read PLAN-M2b.md and follow it; CLAUDE.md rules apply. SPEC.md wins over both.

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 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: 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):

  • First step: from the main checkout, git worktree add .claude/worktrees/agent-m2b -b agent-m2b main; work only there, on branch agent-m2b; then copy the git-ignored files the plan names.
  • Edit only the Gradle root files, android/build-logic/**, android/core/model/**, android/domain/**, android/core/fakes/**, the :app shell (PLAN §4); anything else is a contract request to the orchestrator.
  • Gate: PATH=/opt/homebrew/opt/openjdk@25/bin:$PATH ../tools/gradle-serial.sh check in android/. 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.

Report: end with the report described in PLAN-M2b.md §10: branch, head commit hash, gate result lines, versions chosen with sources, numbering used, how the orchestrator notes were applied, HUMAN steps outstanding (worded for relay), contract requests, open questions and spec gaps with section numbers.