the-custodian/workplans/CUST-WP-0017-scope-md-agent-and-coverage.md

id, type, title, domain, status, owner, topic_slug, created, updated, state_hub_workstream_id

id	type	title	domain	status	owner	topic_slug	created	updated	state_hub_workstream_id
CUST-WP-0017	workplan	SCOPE.md — Repo Scope Analyst Agent + Ecosystem Coverage	custodian	done	custodian	custodian	2026-03-17	2026-03-17	5e0ca777-ee3f-4a83-a742-92e86768a01d

CUST-WP-0017 — SCOPE.md: Repo Scope Analyst Agent + Ecosystem Coverage

Goal

Add the scope-analyst kaizen agent, wire the SCOPE.md template into project scaffolding, and populate SCOPE.md for every accessible registered repo across all five domains.

Background

15 repos are registered with the state-hub across 5 domains. None have a SCOPE.md file. A SCOPE.md provides fast orientation for humans and agents: what the repo is, when it's relevant, and where it fits. The scope-analyst agent automates producing these files.

Tasks

T01 — Add scope-analyst agent to kaizen-agentic

id: CUST-WP-0017-T01
status: done
priority: high
state_hub_task_id: "73932a84-8d1d-4f0a-8d66-e9b9a9f66d9f"

• Fix missing category field in agent-project-management.md (was causing ValueError)
• Create kaizen-agentic/agents/agent-scope-analyst.md with embedded template
• Add scope-analyst row to category table in kaizen-agentic/.claude/rules/architecture.md
• Copy to the-custodian/agents/agent-scope-analyst.md
• Commit in kaizen-agentic repo

T02 — Infrastructure: template + scaffolding + docs

id: CUST-WP-0017-T02
status: done
priority: high
state_hub_task_id: "51834e5c-c970-41bb-819b-75bf5a263182"

• Create state-hub/scripts/project_rules/scope.template
• Prepend @SCOPE.md to claude-md.template
• Update register_project.sh to copy scope.template → SCOPE.md on new registration
• Add scope-analyst row to state-hub/mcp_server/TOOLS.md
• Commit in the-custodian

T03 — SCOPE.md for custodian-domain repos

id: CUST-WP-0017-T03
status: done
priority: high
state_hub_task_id: "7f7b8a54-c866-4b9e-9acc-8f2af074fe2a"

Repos:

• the-custodian → /home/worsch/the-custodian/SCOPE.md
• kaizen-agentic → /home/worsch/kaizen-agentic/SCOPE.md
• ops-bridge → /home/worsch/ops-bridge/SCOPE.md
• activity-core → /home/worsch/activity-core/SCOPE.md

T04 — SCOPE.md for netkingdom repos

id: CUST-WP-0017-T04
status: done
priority: medium
state_hub_task_id: "a0ac87c5-efb8-4b6f-ae4f-1c924a4324f8"

Repos:

• key-cape → /home/worsch/key-cape/SCOPE.md
• net-kingdom → /home/worsch/net-kingdom/SCOPE.md

T05 — SCOPE.md for railiance repos

id: CUST-WP-0017-T05
status: done
priority: medium
state_hub_task_id: "aec409aa-0c2c-49d5-a413-c6191310219f"

Repos:

• railiance-apps → /home/worsch/railiance-apps/SCOPE.md
• railiance-cluster → /home/worsch/railiance-cluster/SCOPE.md
• railiance-enablement → /home/worsch/railiance-enablement/SCOPE.md
• railiance-infra → /home/worsch/railiance-infra/SCOPE.md
• railiance-platform → /home/worsch/railiance-platform/SCOPE.md

T06 — SCOPE.md for markitect repos + flag marki-docx

id: CUST-WP-0017-T06
status: done
priority: medium
state_hub_task_id: "69b36f5d-3992-48a0-bee9-14dc344c290d"

• markitect_project → /home/worsch/markitect_project/SCOPE.md
• marki-docx → flag_for_human (path /home/tegwick/marki-docx not accessible from this machine)

Verification

1. get_kaizen_agent("scope-analyst") via MCP → returns full agent instructions
2. list_kaizen_agents(category="project-management") → shows scope-analyst
3. New repo registered with make register-project → SCOPE.md stub created at root
4. All accessible repos (13) have SCOPE.md; marki-docx flagged for human