gabrielmoreira Learn-Anything Roadmap
"I want to learn X" fails without a map — people drown in resources, learn things in the wrong order, or quit before the payoff. This builds a staged roadmap: the fundamentals that everything else builds on, the sequence that keeps you from overwhelm, the milestones that prove you're getting somewhere, and the stuff you can safely skip — tuned to your actual goal, not a generic curriculum.
What This Skill Produces
- A staged path — fundamentals → building blocks → real application, in an order where each stage enables the next
- The high-leverage first things — the 20% that unlocks 80%, learned first
- What to skip — the rabbit holes, dead-ends, and "learn this someday" stuff that isn't needed for your goal
- Milestones — concrete checkpoints that prove progress (you can now do X)
- Resource types per stage — the best kind of resource for each stage (not a link dump)
- A realistic timeline — honest about how long each stage takes for your available time
Required Inputs
Ask for these if not provided:
- What & why — the skill, and what you actually want to do with it (learning to code a game ≠ to get a job)
- Your level — total beginner or some background
- Time — hours per week and any deadline
- Your learning style — hands-on, structured courses, reading, video
- Depth — dabble, get competent, or go deep
Framework: Fundamentals First, Sequenced, Measured
- Anchor to the real goal. What you want to do determines the path — target that, not a comprehensive curriculum you won't finish.
- Master fundamentals before breadth. Identify the core concepts everything builds on and front-load them; skipping fundamentals collapses later.
- Sequence to avoid overwhelm. Order topics so each builds on the last — learning in the wrong order is why people quit.
- Cut the non-essential. Name what to skip for this goal — most "you should also learn" advice is scope creep.
- Set milestones. Concrete "you can now do X" checkpoints maintain motivation and measure real progress.
- Match resource to stage. Beginners need structure; intermediates need practice and projects; advanced need depth and feedback.
Output Format
Roadmap: [skill] · goal [x] · [time/week] · [level]
Stage 1 — Fundamentals: [core concepts] · milestone: [you can now X] · best via [resource type]. Stage 2 — Building blocks: [next] · milestone: […] · via […]. Stage 3 — Real application: [apply it] · milestone: […] · via […].
Learn first (highest leverage): [the unlocking 20%]. Skip for now: [rabbit holes / non-essential for your goal]. Realistic timeline: [per stage, for your hours].
Quality Checks
- Path is anchored to the person's real goal, not a generic curriculum
- Fundamentals are front-loaded before breadth
- Topics are sequenced so each builds on the last
- Names what to skip for this goal
- Has concrete milestones per stage
- Matches resource types to stages and gives a realistic timeline
Anti-Patterns
- A resource dump with no sequence or stages.
- Comprehensive curriculum the person won't finish.
- Breadth before fundamentals.
- No milestones to measure progress.
- Ignoring the real goal and teaching everything.
Example Trigger Phrases
- "How do I learn to code? Make me a roadmap."
- "I want to learn guitar — where do I start and in what order?"
- "Learning plan for getting good at public speaking."
- "Roadmap to learn data analysis for my job."
- "I want to get into woodworking — stage it for me."