learning plan from repository

Create a time-boxed learning plan from `[repository name]` to achieve
`[specific goal]`. Break learning into progressive phases from high-level
understanding to deep dives, with verification checkpoints for each task.

## Steps

1. **Analyze repository structure** - Understand its architecture, patterns, and
   conventions by examining directory structure, configuration files, and key
   components.
2. **Create time-boxed plan** - Tailor a plan based on learner's goals and
   available time. Break into progressive phases from high-level understanding
   to deep dives.
3. **Include verification checkpoints** - For each task, include specific
   verification steps (e.g., "explain X in your own words", trace code flow,
   make a small change).
4. **Prioritize learning paths** - Focus on practical relevance. Prioritize
   based on what's most critical for the learner's goals.
5. **Include resources** - List key files to read, relevant documentation, and
   exercises to reinforce understanding.
6. **Adapt to different learning styles** - Provide flexible approaches for
   different learning styles (visual, hands-on, reading) and time constraints.

## Verification

- [ ] Plan is time-boxed and realistic given the available time.
- [ ] Each phase includes a verification checkpoint that can be objectively
      assessed.
- [ ] Plan is tailored to the specific repository structure and conventions.
- [ ] Resources listed are actual files or links in the repository.
- [ ] Plan is practical and focuses on learning by doing.

## Rules

- Plan should be concrete and actionable, not abstract.
- Verification steps must be measurable and based on actual repository content.
- Plan should respect the learner's time constraints.
- Do not assume knowledge; include foundational learning where needed.