generated from coulomb/repo-seed
tegwick
ea1fd23481
- project_rules templates: rename workstream->workplan in prose; registration guidance is now file-first + fix-consistency C-06 (manual create_workplan/ create_workstream calls create duplicates); progress examples use workplan_id; legacy field names (state_hub_workstream_id) annotated - update_agent_instruction_files: never overwrite filled-in stack-and-commands/repo-boundary/architecture rules (TODO-marker guard) - mcp_server: add_progress_event accepts workplan_id (preferred) with workstream_id kept as legacy alias, mirroring create_task Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
43 lines
1.6 KiB
Plaintext
43 lines
1.6 KiB
Plaintext
## First Session Protocol
|
||
|
||
Triggered when `get_domain_summary("{DOMAIN}")` shows **no workplans**.
|
||
The project is registered but work has not yet been structured.
|
||
|
||
**Step 1 — Read, don't write**
|
||
- `~/the-custodian/canon/projects/{DOMAIN}/project_charter_v0.1.md` — purpose, scope
|
||
- `~/the-custodian/canon/projects/{DOMAIN}/roadmap_v0.1.md` — planned phases
|
||
- Scan repo root: README, directory structure, existing code or docs
|
||
|
||
**Step 2 — Survey in-progress work**
|
||
Look for TODOs, open branches, half-finished files. Note done vs. started but incomplete.
|
||
|
||
**Step 3 — Propose workplans to Bernd**
|
||
Propose 1–3 workplans — each a coherent strand, weeks to months, anchored to a
|
||
roadmap phase. **Wait for approval before creating.**
|
||
|
||
**Step 4 — Write the workplan file; fix-consistency registers it (ADR-001)**
|
||
```
|
||
workplans/{WP_PREFIX}-NNNN-<slug>.md ← write this, commit it
|
||
```
|
||
Then register by running the consistency check — do **not** call
|
||
`create_workplan`/`create_task` (or legacy `create_workstream`) yourself;
|
||
manual registration duplicates what C-06 creates from the file:
|
||
```bash
|
||
statehub fix-consistency --repo {REPO_SLUG}
|
||
```
|
||
C-06 creates the hub workplan + tasks and writes `state_hub_workstream_id` /
|
||
`state_hub_task_id` back into the file (legacy field names, kept for
|
||
compatibility — they hold workplan/task IDs).
|
||
|
||
**Step 5 — Record the setup**
|
||
```
|
||
add_progress_event(
|
||
summary="First session: structured {DOMAIN} into N workplans, M tasks",
|
||
event_type="milestone",
|
||
topic_id="{TOPIC_ID}",
|
||
detail={"workplans": [...], "tasks_created": M}
|
||
)
|
||
```
|
||
|
||
<!-- Delete or archive this file once past first session -->
|