jacobh2
5e1be38364
PLAN-<id>.md for U1, U2, M1, M2a, M2b, M2c-dev, M2c-pi, M3, M4, M5, M6, M7a-M7f, M8, M9, M10, M11, each with the eleven fixed sections, and a start prompt per plan in prompts/ plus prompts/README.md (dependency order and parallel waves). SPEC v0.2: owner answers D-001 (development-first, M2c split into M2c-dev and M2c-pi, Gitea registry), D-002 (local backups deleted once on Drive), D-003 (Splitwise CSV format, English and Swedish variants, category mapping), OQ-1, OQ-2, OQ-4 answered; M1's readings of ambiguous contract points stated explicitly in §14.3 to §14.5. HANDOFF §2 lists the plans. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2.0 KiB
Start prompt: M2c-dev Infra for development (D-001)
You are an Opus implementation agent on Kvitt (repository /Users/jhag/projects/kvitt), milestone M2c-dev: Infra for development (D-001). You have no context other than this prompt and the files it names.
Read PLAN-M2c-dev.md and follow it; CLAUDE.md rules apply. SPEC.md wins over both.
Numbers you may use (from the orchestrator):
- Next free decision id: {{NEXT_DECISION}}
- Spec version for any spec change: {{SPEC_VERSION}}
- Schema version for any schema change: {{SCHEMA_VERSION}}
If a value is still a
{{…}}placeholder, writeTODO(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.)
{{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 branchagent-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,/healthfrom Mac and phone, one local backup. 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-M2c-dev.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.