Menu
Pauses development mode to teach a technical concept at three increasing levels of complexity, tailored to a technical PM audience. Use when the user wants to understand something they encountered while building.
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
Updates all project documentation after code or skill changes. Always reads actual implementation before writing. Covers README, CHANGELOG, docs/, AGENTS.md, memory files, and skills-info.md. Use after completing any feature, fix, refactor, or skill update.
Compacts the current conversation into a handoff document so a fresh agent can continue the work. Saves to the OS temp directory, not the workspace. Pass an optional argument describing what the next session will focus on.
Documents the process, methodology, and decisions of the current session as a reproducible narrative. Saves to spec/process/ in the workspace so the journey can be understood and recreated by others.
Scaffolds a new project by conducting an interview to collect metadata and generating standard repository documentation files from the framework templates. Use when setting up a new repository.
Run this after /hyper-tutorial-run to turn tutorial failures into a structured, constraint-aware goal prompt. Interviews the user about their goal and what may/may not be changed, then generates a paste-ready prompt for a new Claude Code fix session. Does NOT re-run tutorial commands.
Generates a markdown tutorial from an integration test or user-provided files through iterative LLM + human collaboration. Tutorials are saved to tutorials/<name>/ with organized supporting files.
| name | learning-opportunity |
| description | Pauses development mode to teach a technical concept at three increasing levels of complexity, tailored to a technical PM audience. Use when the user wants to understand something they encountered while building. |
This skill pauses development mode and shifts into teaching mode — delivering a concept at three increasing levels of complexity, peer-to-peer, without oversimplification.
/hyper-learning-opportunity [concept]./hyper-learning-opportunity [topic].Technical PM with mid-level engineering knowledge. Understands architecture, can read code, ships production apps. Not a senior engineer, but not a beginner. Apply the 80/20 rule — focus on concepts that compound. Don't oversimplify, but prioritize practical understanding over academic completeness.
Begin by using AskUserQuestion to check how deep the user wants to go:
What depth of explanation do you want?
- Option A: Conceptual overview (Level 1 only) — what it is and why it exists
- Option B: Practical walkthrough (Levels 1–2) — concepts + mechanics + trade-offs
- Option C: Full deep dive (all 3 levels) — including implementation details and senior-engineer perspective
After delivering each level, use AskUserQuestion before advancing:
Ready to continue to the next level?
- Option A: Yes, continue — move to the next level
- Option B: Explain more here — go deeper on this level before advancing