Skip to content

Commit 2a6ce7d

Browse files
scenario-based skill tweak
1 parent befaa1e commit 2a6ce7d

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

  • .github/skills/learning-path-structure-review

.github/skills/learning-path-structure-review/SKILL.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,11 +17,11 @@ Use this skill when a Learning Path needs a structural review. Focus on whether
1717
- Additional resources and next steps live in `_index.md` `further_reading`, not in `_next-steps.md`.
1818
- `_next-steps.md` remains minimal and respects `FIXED, DO NOT MODIFY` template comments.
1919
4. Review the instructional shape:
20-
- The title and opening frame one developer task/job-to-be-done.
20+
- The title and opening of the Learning Path frame one developer task/job-to-be-done.
2121
- The introduction gives context, user goal, and practical value.
2222
- Prerequisites are explicit and linked when useful.
2323
- Learning objectives are measurable, action-oriented, and limited to three or four bullets.
24-
- Sections progress logically through prepare, configure, use, and validate phases, with each section ideally focusing on one job-to-be-done.
24+
- Sections progress logically through prepare, configure, use, and validate phases, with each section ideally focusing on one job-to-be-done. Flag nebulous sections with titles such as "working with x" or "managing y" that include multiple tasks that shouldn't be grouped together (e.g. creating and deleting a VM, or creating a VM and security group rules in the same section).
2525
- Validation steps prove the learner reached the promised outcome.
2626
- The conclusion or next-step guidance names what the learner can do next.
2727
5. Review `further_reading`:

0 commit comments

Comments
 (0)