Session kit template · Mother orchestrator
Template riusabile per future sessioni Claude Code orchestratore (Mother + opzionali Child paralleli).
Files in questo template
| # | File | Cosa | Personalizzare |
|---|---|---|---|
| 00 | 00-preflight-check.sh |
Pre-flight check 30sec · detecta drift kit→repo · output GREEN/YELLOW/RED | Variabili top del file (EXPECTED_BASELINE_BRANCH, EXPECTED_BASELINE_HEAD, EXPECTED_MONOREPO, ecc.) |
| 01 | 01-mother-brief-template.md |
Template brief Mother (XML tags task_spec/reasoning_map/planning_map · model_recommendation · risk register · acceptance · handover) | Goal + scope + constraints + stakeholder per la sessione specifica |
| 02 | 02-child-brief-template.md |
Template brief Child standalone (deliverable · time budget · decision matrix autonomous · acceptance · self-improvement loop) | Scope packages assegnati + tools authorized + tempo budget |
| 10 | 10-kickoff-paste-template.md |
Template prompt copia-incolla in Mother session · ACK 5-line + Fase 0 sequence | Path file kit · pre-flight gate command · time budget realistico |
| 20 | 20-foreground-singleturn-modes.md |
OBBLIGATORIO READ · Option A (full-kit background-parallel) vs Option B (foreground scope-reduced) vs Option C (mini-only) | Mother decide quale Option attivare dopo pre-flight |
Workflow Mother nuova sessione
1. Pasta `10-kickoff-paste-*` in Claude Code aperto su repo target
2. Mother PRIMA AZIONE: `bash ops/sessions/<this-kit>/00-preflight-check.sh`
- Exit 0 → procedi con kit come scritto
- Exit 1 → flag drift al founder + procedi con time-boxed correzioni
- Exit 2 → STOP + AskUserQuestion (Option A/B/C)
3. Mother SECOND AZIONE: leggi `20-foreground-singleturn-modes.md` + decide modalità (single-turn foreground vs background-parallel · scope-reduced vs full-kit)
4. Mother ACK 5-line + 🚀 START Fase 0
Quando creare un nuovo session kit
Trigger:
- Task >4h con multi-package/multi-system change
- Architettura nuova (es. PMS foundation 2026-05-16) o refactor cross-layer
- Co-presenza Mother + ≥1 Child paralleli giustificata
- Output deve essere autonomous-mergeable post-CI (auto-merge v2 authorization applicable)
NON serve session kit per:
- Single-file fix
- Doc update
- Routine task <2h
- BOS updates standard (chunks markdown)
Genesi del template
2026-05-17 · da lesson learned sessione PMS foundation 2026-05-16:
- Kit pre-generato può divergere prima execution → pre-flight check obbligatorio
- Auto-merge v2 deve distinguere "additive packages/* nuovi" da "build-manager/lockfile/deploy-target change" → secondo livello gating
- "8h Mother+Child paralleli" è realistico per agent background, non foreground single-turn → modes pre-definite
Vedi ops/operating-protocol-orchestrator.md § Lessons-Learned (entry 2026-05-17).