learning-goallisted

# /learning-goal — state the target Maintains `goal.md` in the project root: the one statement of what the user needs to be able to do. Everything downstream judges relevance against it — `/catalog` marks a required topic nothing covers as a gap, and material that fits no required topic as out of scope. The name is `learning-goal`, not `goal`: this plugin ships into environments that may already have a skill called `goal`. ## Steps 1. Read `goal.md` if it exists. Its shape is the contract below. 2. Take whatever the user gave you — prose, a pasted job ad or module handbook, a URL, or any mix. **Fetch what you were given links to** and read it. A brief is a statement of the target, so do **not** register it in `sources.yaml`; a user who wants the syllabus itself carded registers it with `/sources`. 3. Distil it into required topics grouped by area (see below). 4. If `goal.md` already exists, reconcile rather than overwrite — see *Re-runs*. 5. Write `goal.md`, then show the areas and their topics back as a short tree and point at the next step. ## The file ```markdown --- goal: 'One line: what being ready looks like' kind: exam # exam | meeting | interview | self-study depth: working # awareness | working | expert updated: 2026-08-18 # today, ISO --- # Learning goal One to three sentences on what being ready actually looks like. ## Required topics ### <Area> - A topic somebody pursuing this goal has to know - Another one ### <Ano