Live
Powered by

Implementation Plan

An OpenClaw CoachLuca Multi-Agent System

Status: Phase-one scaffold implemented; manual dry run and quality review pending Source of truth: planning/proposal.md

1. Implementation Goals

Phase One Goal

Build a stable, usable multi-agent coaching system with one coordinator and four specialists, clear ownership boundaries, durable daily records, and coordinator-owned daily and weekly reporting.

Definition of Done for First Pass

Phase one is done when all items below are true:

  • The coordinator and four specialists are set up with separate workspaces and clear role boundaries.
  • Shared doctrine and per-agent bootstrap files exist and are internally consistent.
  • Foundational planning records exist and are maintained by the coordinator.
  • Specialists produce daily working logs with meaningful domain content.
  • The coordinator produces daily and weekly team reports and athlete notes.
  • Communication boundaries are enforced: only Coach Luca communicates directly with the athlete.
  • All coaching and athlete materials are contained inside the profile workspace.
  • Manual quality review confirms reporting quality before broader automation is enabled.

2. Scope

Included in Phase One

  • Coordinator: Coach Luca
  • Specialists: endurance, nutrition agent, recovery, strength
  • Shared doctrine and per-agent bootstrap files
  • Coordinator-owned planning inputs (goals, priorities, race schedule, travel schedule)
  • Nutrition intake workflow for nutrition items
  • Specialist daily working logs
  • Coordinator daily and weekly team and athlete reporting
  • Heartbeat for specialist upkeep checks
  • Coordinator cron for phase-one reporting cadence after manual validation

Deferred to Later Phases

  • Performance-analyst agent
  • Monthly coordinator reporting in live cadence
  • Expanded automation beyond phase-one cadence
  • Additional specialist roles beyond approved list

3. Workspace and File Structure

All coaching and athlete materials must remain inside the OpenClaw profile workspace only.

Intended Structure Under Profile Root

  • shared
    • doctrine and cross-agent reference material
  • planning
    • proposal and implementation planning documents
  • intake
    • coordinator-managed inbound materials and planning inputs
  • athlete
    • coordinator-owned official outputs: team reports (internal) and athlete notes (external)
  • team/coach-luca
    • coordinator bootstrap files, working synthesis logs, synthesis reference files
    • note: formal team reports live in athlete/team-reports/, not here
  • team/endurance
    • specialist bootstrap and daily working files
  • team/nutrition agent
    • specialist bootstrap, nutrition working files, nutrition records
  • team/recovery
    • specialist bootstrap and daily working files
  • team/strength
    • specialist bootstrap and daily working files

Containment Rule

  • No coaching-related file may be stored, duplicated, copied, or moved outside the profile workspace root.
  • This includes records, logs, reports, images, templates, schedules, and planning materials.

4. Agent Structure

Coordinator: Coach Luca

Role:

  • Single integration point and final decision authority.
  • Sole communication interface with the athlete.

Owns:

  • Intake triage and specialist routing.
  • Final integrated recommendations.
  • Athlete planning record maintenance.
  • Team reports and athlete-facing reports.

Not allowed to do:

  • Bypass documented ownership rules.
  • Delegate direct athlete communication to specialists.

Specialist: endurance

Role:

  • Training structure, progression, session design, and session review.

Owns:

  • Endurance domain recommendations and daily working log.

Not allowed to do:

  • Send athlete-facing recommendations directly.
  • Make final cross-domain decisions.

Specialist: nutrition agent

Role:

  • Daily fueling, on-bike fueling, hydration, recovery nutrition, and nutrition intake estimation.

Owns:

  • Nutrition recommendations, nutrition records, and daily working log.

Not allowed to do:

  • Send athlete-facing recommendations directly.
  • Make final cross-domain decisions.

Specialist: recovery

Role:

  • Readiness interpretation, fatigue flags, recovery status.

Owns:

  • Recovery recommendations and daily working log.

Not allowed to do:

  • Send athlete-facing recommendations directly.
  • Make final cross-domain decisions.

Specialist: strength

Role:

  • Gym programming, activation, and in-season strength support.

Owns:

  • Strength recommendations and daily working log.

Not allowed to do:

  • Send athlete-facing recommendations directly.
  • Make final cross-domain decisions.

5. Communication Rules

  • Only Coach Luca sends direct messages to the athlete.
  • Only Coach Luca receives direct athlete responses and inbound media.
  • Coach Luca is also the intake point for operator requests and scheduled system triggers.
  • Specialists communicate internally to Coach Luca only.
  • Cross-domain conflicts are escalated to Coach Luca for final decision.
  • Athlete-facing outputs are unified and coordinator-authored, not specialist-delivered.

6. Documents and File Ownership

Shared References

  • Shared doctrine and team-wide reference guidance
  • Maintained as shared materials, read across agents

Coordinator-Owned Documents

  • Athlete planning record
  • Race and travel schedule record
  • Goals and priority events record
  • Team reports (daily, weekly, monthly cadence ownership)
  • Athlete-facing notes (daily, weekly, monthly cadence ownership)
  • Intake tracking and routing notes

Specialist-Owned Working Files

  • Daily specialist working logs
  • Domain-specific working notes
  • Nutrition-owned nutrition records and nutrition observations

Ownership Rule

  • Every file has one owner.
  • Non-owners may read where allowed, but do not write to owner-managed files.

7. Planning Inputs

The following are foundational coordinator-maintained planning inputs:

  • Athlete goals
  • Priority events
  • Race schedule
  • Travel schedule

Usage model:

  • Coach Luca maintains these as current source-of-truth planning records.
  • Specialists treat them as active planning inputs that shape domain recommendations, not passive reference material.
  • Any meaningful update from athlete communication is reflected by Coach Luca in these records.
  • The planning record should influence training structure, nutrition planning, recovery planning, strength programming, reporting priorities, and tradeoff decisions.

8. Nutrition Intake Workflow

Plan-level workflow:

  1. Athlete sends nutrition items and optional context to Coach Luca.
  2. Coach Luca routes items to nutrition agent.
  3. Nutrition reviews each item and estimates likely intake pragmatically.
  4. Nutrition stores nutrition-related records inside nutrition-owned workspace files.
  5. Nutrition logs observations, assumptions, and planning-relevant implications in daily log.
  6. Coach Luca incorporates nutrition outputs into integrated planning and reports.

Constraints:

  • Estimates are treated as estimates.
  • All related files remain inside profile workspace containment.

9. Logging and Reporting

Specialist Logging

  • Daily specialist working logs are required in phase one.
  • Logs capture recommendations, watch items, unresolved questions, and notable changes.

Coordinator Reporting Ownership

  • Team reports are coordinator-owned. Purpose: internal record of reasoning, decisions, tradeoffs, and risks.
  • Athlete notes are coordinator-owned. Purpose: concise, actionable external guidance derived from coordinator synthesis — not raw specialist output.

Cadence Ownership by Phase

  • Phase one: daily and weekly coordinator reporting is active.
  • Phase two: monthly coordinator reporting is added.

10. Bootstrap Files and Shared Doctrine

Required Per-Agent Bootstrap Set

Each agent needs its own bootstrap identity and instruction set, including:

  • AGENTS
  • SOUL
  • IDENTITY
  • USER
  • MEMORY
  • TOOLS
  • HEARTBEAT

Coordinator boundary note:

  • The coordinator may keep a heartbeat file as bootstrap metadata, but heartbeat-driven upkeep behavior is specialist-owned in phase one.
  • Coordinator scheduled reporting remains cron-owned.

Shared vs Unique

  • Shared across agents: doctrine and team-level rules.
  • Unique per agent: role identity, domain constraints, local memory, and working instructions.

Coordination Requirement

  • Shared doctrine must be reflected consistently across agent bootstrap files.
  • Role boundaries are enforced by instructions and per-agent skill scoping/allowlists.

11. Automation Approach

Heartbeat

  • Purpose: approximate in-session upkeep and periodic checks.
  • Primary use in phase one: specialist reminders and working-log hygiene.

Cron

  • Purpose: precise scheduled reporting and isolated task runs.
  • Primary use in phase one: coordinator reporting cadence after manual validation.

Automation Gate

  • Athlete-facing automation is enabled progressively.
  • Manual quality review must pass before broader automation is considered complete.

12. Implementation Sequence

Step 1: Structure Setup

  • Create/confirm profile-root directory structure and agent workspaces.
  • Confirm containment rule is represented in shared doctrine and plan artifacts.

Step 2: Bootstrap and Doctrine

  • Create coordinator and specialist bootstrap files.
  • Align shared doctrine across all agents.
  • Confirm role boundaries and communication gateway rules are explicit.

Step 3: Core Records

  • Create coordinator-owned planning input documents.
  • Create team and athlete report templates.
  • Create specialist daily log templates.

Step 4: Workflow Wiring

  • Establish coordinator routing flow to specialists.
  • Establish nutrition intake routing and recording workflow.
  • Confirm file ownership and write boundaries.

Step 5: Manual Dry Run

  • Run daily operations manually for at least one cycle.
  • Produce specialist logs and coordinator daily/weekly outputs.
  • Review quality, coherence, and ownership compliance.

Step 6: Controlled Automation Enablement

  • Enable heartbeat for specialist upkeep checks.
  • Enable coordinator cron for approved phase-one cadence.
  • Continue manual review during early automated cycles.

13. Validation and Review

Implementation is ready when the following checks pass:

Structure Review

  • Required folders, bootstrap files, and core documents exist in expected locations.
  • All coaching and athlete materials are contained inside profile workspace.

Ownership Review

  • Every major document has a clear owner.
  • No cross-agent unauthorized writes are present.

Communication-Boundary Review

  • Only Coach Luca handles direct athlete communication.
  • Specialists route through coordinator without direct athlete messaging.

Reporting Review

  • Specialist daily logs are populated with meaningful content.
  • Coordinator daily and weekly outputs are coherent, actionable, and internally consistent.
  • Team reports and athlete notes are clearly differentiated: team reports contain internal reasoning and risk; athlete notes are concise and do not expose internal deliberation.

Automation Review

  • Heartbeat and cron are used according to role.
  • Manual quality gate was completed before automation expansion.

Skill-Scope Review

  • Per-agent skill visibility and allowlists match defined domain boundaries.
  • No specialist has active skill scope that enables out-of-domain authority.

14. Open Questions and Assumptions

Assumptions

  • Coach Luca remains the sole athlete communication gateway.
  • Phase-one monthly reporting remains deferred to phase two.
  • Human operator is available for manual quality review and doctrine alignment.

Questions to Verify During Implementation

  • Are specialist templates concise enough to support daily use without drift?
  • Are planning input updates frequent enough to keep specialist recommendations current?
  • Is report quality stable before increasing automation reliance?