macro-plan-create

Create a macro plan

Operate non-interactively. Do not ask the athlete questions, approve the plan, or generate exact workouts.

Preconditions

Require:

• an approved baseline VDOT bound in approval state;
• a confirmed goal and profile constraints;
• a complete enough synchronized history to establish recent run exposure;
• no active plan; use the plan-renewal procedure to review and close it first;
• an immutable macro-planning context for the exact evidence date and intended start Monday;
• a target date that fits a contiguous Monday-Sunday plan horizon.

Return a blocking checklist if any item is absent.

Methodology selection

Read docs/coaching/methodology.md. The controlled registry resolves the matching source-only record and its exact SHA-256. Select one conceptual methodology reference for the complete plan. The plan remains coach-designed from athlete evidence and constraints:

• daniels for VDOT-anchored, purpose-specific running across race distances;
• pfitzinger for experienced marathon preparation with adequate running frequency and durable volume;
• fitzgerald_80_20 when reliable intensity evidence and disciplined low-intensity volume are central;
• first is unavailable until edition-specific pace and schedule tables are verified and encoded.

Do not claim an edition-specific progression, pace, long-run share, recovery cycle, or taper rule from these conceptual records. The draft records only the identifier and an athlete-specific rationale; the registry binds the source and labels the authority coach_designed_conceptually_informed.

Workflow

1. Inspect:

   poetry run resilio approvals status
   poetry run resilio profile get
   poetry run resilio plan status
   poetry run resilio dates today
   

   Create the evidence gate if the plan-renewal procedure has not already produced it:

   poetry run resilio plan create-macro-context \
     --evidence-as-of <DATE> \
     --start <PLAN_START_MONDAY>