generated from coulomb/repo-seed
Add the 9-file .claude/rules set (repo-identity, session-protocol, first-session, workplan-convention, stack-and-commands, architecture, repo-boundary, credential-routing, agents), adapted to binect-chrome: slug, agent name, BCHROME-WP- workplan prefix, shared communication topic. stack/architecture/repo-boundary filled with this repo's real content. Rewrite CLAUDE.md to the @-import structure mirroring binect-js (prior prose migrated into the rule files), retaining an inline Kaizen reference. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
1.4 KiB
1.4 KiB
First Session Protocol
Triggered when get_domain_summary("communication") shows no workstreams.
The project is registered but work has not yet been structured.
Step 1 — Read, don't write
~/the-custodian/canon/projects/communication/project_charter_v0.1.md— purpose, scope~/the-custodian/canon/projects/communication/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 workstreams to Bernd Propose 1–3 workstreams — each a coherent strand, weeks to months, anchored to a roadmap phase. Wait for approval before creating.
Step 4 — Create workplan file first, then DB record (ADR-001)
workplans/BCHROME-WP-NNNN-<slug>.md ← write this first
Then register in the hub:
create_workstream(topic_id="36c7421b-c537-4723-bf75-42a3ebc6a1dc", title="...", owner="...", description="...")
create_task(workstream_id="<id>", title="...", priority="high|medium|low")
Step 5 — Record the setup
add_progress_event(
summary="First session: structured communication into N workstreams, M tasks",
event_type="milestone",
topic_id="36c7421b-c537-4723-bf75-42a3ebc6a1dc",
detail={"workstreams": [...], "tasks_created": M}
)