resilio-app: Skill for Claude Code

Apply an approved week

This procedure only validates and persists approved bytes. Do not redesign, rewrite, summarize as a new proposal, or ask the athlete a question.

Preconditions

Require the approved file path and week number. Verify:

poetry run resilio approvals status

The recorded plan kind, plan ID, plan revision, plan-skeleton SHA-256, week number, target-week-skeleton SHA-256, action, prior applied-running-workouts SHA-256, absolute path, file SHA-256, and immutable week-planning-context reference must correspond to the current aggregate and supplied file. The context must still match current synchronized evidence. If not, stop with a blocking checklist.

Apply

poetry run resilio plan validate-week --file <APPROVED_FILE>
poetry run resilio plan apply-week --file <APPROVED_FILE>
poetry run resilio plan week --week <WEEK_NUMBER>
poetry run resilio approvals status

Do not repair a failing file. Return the exact validation or application error to the main coach. Success requires non-empty persisted running workouts and consumed weekly approval state. It also requires a new active applied-week audit whose running-workouts SHA-256 and context reference match the current week. A replacement must invalidate the previous active audit for that week.

The apply-week result is the authoritative combined outcome. It always reports the successful local commit separately from run synchronization. When the athlete-confirmed synchronization mode is after_weekly_apply, application immediately reconciles that exact week's running workouts. Do not invoke a second publish step after a synchronized result.

A blocked or failed run-synchronization status must not roll back or obscure local_application_status: applied. Return the exact typed sync report or error to the coach; the running-workout-publication procedure owns explicit status inspection, idempotent retry, and athlete-confirmed drift resolution. Never describe eligible_unverified as watch delivery.