Menu
Alice's couch-to-5K retrospective with training reflections and progress tracking.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Framework for managing project file context after retros/planning. Trigger after weekly retro + planning complete, after monthly retro + planning complete, or when context feels bloated. Also triggers with "context curation", "clean up project files", "archive old summaries", "what can we remove". Uses fractal compression with fold-before-archive pattern.
Framework for starting new daily chat with gentle context loading from previous session's summary. Use when user says "good morning", starts new chat with minimal prompt, or explicitly requests morning brief. Loads most recent summary and generates scannable brief. Optimized for low cognitive load during morning wakeup. Includes contemplation thread reopening from summary. Extend with personal metrics and protocols.
Framework for planning at any time scale (daily, weekly, monthly, quarterly, yearly). Trigger with "plan my day", "weekly planning", "monthly planning", "[month] planning" (e.g., "january planning", "december planning"), "plan for [period]", or "let's plan [period]". Identifies constraints FIRST, then suggests priorities. Uses Level 0-3 success framework. Inputs vary by scale - daily uses yesterday summary, weekly uses weekly retro, monthly uses monthly retro, etc.
Framework for retrospectives at any time scale (daily, weekly, monthly, quarterly, yearly). Trigger with "daily retro", "weekly retro", "monthly retro", "[month] retro" (e.g., "december retro", "january retro"), "retro for [month]", or "end of month review". Answers three questions - what worked, what didn't, how to improve. Inputs vary by scale - daily uses raw logs, weekly uses daily summaries, monthly uses weekly retros, etc. Fractal compression pattern.
Framework for creating session summary documents. Use when user says "daily summary", "generate summary", or similar. Provides structured markdown template with date verification, filename patterns, and formatting guidelines. Supports range-based naming for sessions spanning calendar boundaries. Extend with personal metrics and domain-specific content.
Initial project setup for goal coaching system. Use when user says "set up my project", "configure my coaching project", "initialize my goals", or when starting a fresh coaching project with no existing Project-Goals.md. Guides user through conversational setup (one question at a time), generates Project-Goals.md artifact, and introduces daily/weekly workflow trigger phrases.
| name | retrospective-alice-personal |
| description | Alice's couch-to-5K retrospective with training reflections and progress tracking. |
| metadata | {"extends":"retrospective-base"} |
This skill extends retrospective-base with running training-specific context.
Note: This is an EXAMPLE showing how to adapt the retrospective framework for couch-to-5K training. Replace with your own domain terminology.
TZ='America/New_York' date '+%A, %B %d, %Y - %I:%M %p %Z'
# Show week being reviewed (includes previous Sunday)
for day in 9 10 11 12 13 14 15; do
TZ='America/New_York' date -d "2025-11-$day" '+%A, November %d, 2025'
done
Training Context: Brief context about training phase or race schedule (e.g., "Week 4 of couch-to-5K, building endurance")
When describing capacity/progress trends, use these training-specific modes:
When identifying patterns in "What Worked" or "What Didn't Work":
Common experiments in running context:
When comparing across timeframes, attend to:
Use training-specific trajectory descriptions:
Celebrate wins specific to running:
Challenges specific to running:
Pair with running-appropriate experiments:
Even in difficult training weeks, appreciate:
This personal skill provides running/fitness domain language and examples.
The base skill provides:
Together they create a complete running training-focused weekly retrospective.
Adapt this example: Replace running terminology with YOUR domain (learning, business, creative work, etc.)