Skill: Draft Student Learning Targets
Description
Generates well-formed Student Learning Targets (SLTs) for a course or module based on topic, audience, and learning goals. Follows education research best practices and Andamio protocol conventions.
Instructions
Path Resolution
Resolve file paths based on your execution context:
- Plugin context (
${CLAUDE_PLUGIN_ROOT} is set): Read knowledge from ${CLAUDE_PLUGIN_DATA}/knowledge/ (user data), falling back to ${CLAUDE_PLUGIN_ROOT}/knowledge/ (seed data). Read research from ${CLAUDE_PLUGIN_ROOT}/knowledge/research/.
- Clone/symlink context (default): Read knowledge from
knowledge/ relative to the project root (research is at knowledge/research/).
Pre-Execution Knowledge Check
Before drafting SLTs, read the knowledge base for patterns that should influence your work. If any knowledge file does not exist, skip it and proceed without prior patterns — note "No prior data available" in output.
Read knowledge/slt-patterns/verb-bank.yaml
- Note effective verbs by Bloom's level
- Prefer verbs with high success_count
Read knowledge/slt-patterns/quality-issues.yaml
- Note problematic patterns to avoid
- Especially avoid patterns with high frequency
Surface knowledge to user (if relevant patterns exist):
### Tips from Previous Courses
**Effective verbs at this level:** compare, distinguish, implement (12 successes)
**Patterns to avoid:** "understand X" (flagged 8 times), task-focused phrasing
The user will describe a course or module they want to create. Gather the following information (ask if not provided):
- Topic: What is the course/module about?
- Audience: Who are the learners? What's their background?
- Learning goals: What should learners be able to do after completing this?
- Module count: How many modules? (Default: 3-4)
- SLTs per module: How many SLTs per module? (Default: 2-4)
Always read knowledge/research/slt-research-report.md for full research context before drafting.
The SLT Formula
Every SLT must follow this structure:
I can + [measurable verb] + [specific outcome] + [observable evidence/context]
Examples:
- Weak: "I can understand blockchain" (unmeasurable, vague)
- Better: "I can explain what a blockchain is" (measurable, but no evidence)
- Strong: "I can compare a Portable Access Token to a traditional platform account by identifying at least two differences in ownership, portability, and revocability" (measurable verb, specific outcome, observable evidence)
Verb Selection (Bloom's Taxonomy)
Use verbs that match the cognitive level appropriate for the content:
| Level |
Verbs |
When to Use |
| Remember |
list, name, identify, recall |
Foundational facts, terminology |
| Understand |
explain, describe, summarize, compare |
Conceptual understanding |
| Apply |
use, demonstrate, implement, execute |
Procedural skills |
| Analyze |
distinguish, examine, compare, contrast |
Breaking down complex topics |
| Evaluate |
judge, justify, critique, assess |
Making judgments |
| Create |
design, construct, develop, produce |
Building something new |
Progression principle: Early modules should include more Remember/Understand/Apply. Later modules can include Analyze/Evaluate/Create.
Verbs to Avoid
Never use these unmeasurable verbs:
- understand, know, learn, appreciate, be aware of, become familiar with
These cannot be assessed. Replace with specific, observable actions.
Output Format
Generate SLTs in this exact format:
# SLTs: [Course Name]
## Module 1: [Module Title]
- 1.1: I can [verb] [specific outcome] [evidence/context].
- 1.2: I can [verb] [specific outcome] [evidence/context].
- 1.3: I can [verb] [specific outcome] [evidence/context].
## Module 2: [Module Title]
- 2.1: I can [verb] [specific outcome] [evidence/context].
- 2.2: I can [verb] [specific outcome] [evidence/context].
## Module 3: [Module Title]
- 3.1: I can [verb] [specific outcome] [evidence/context].
- 3.2: I can [verb] [specific outcome] [evidence/context].
- 3.3: I can [verb] [specific outcome] [evidence/context].
Guidelines
One capability per SLT. If an SLT has "and" connecting two different skills, split it.
Make it assessable. Ask: "Could a teacher design an assignment to verify this?" If not, rewrite.
Write for the learner. SLTs should make learners curious, not anxious. Name tools and frameworks, but leave implementation details to the lessons.
Build progression. Module 1 SLTs should be achievable early. Later modules can build on earlier ones.
2-4 SLTs per module is ideal. More than 5 per module suggests the module should be split.
Consider the assignment. Each module needs one assignment that can assess all its SLTs. If the SLTs don't fit a coherent assignment, reorganize.
Mark optional modules. If a module is optional/advanced, note it in the title: "Module 4: [Title] (Optional)"
Quality Checklist
Before outputting, verify each SLT:
After Drafting
Suggest the user:
- Review and refine the SLTs with their team
- Run
/assess-slts to get quality feedback
- Create
00-course.md with lesson types and assignments based on the finalized SLTs
1---2name: draft-slts3description: Draft Student Learning Targets for a new course or module.4license: MIT5---6
7# Skill: Draft Student Learning Targets
8
9## Description
10
11Generates well-formed Student Learning Targets (SLTs) for a course or module based on topic, audience, and learning goals. Follows education research best practices and Andamio protocol conventions.
12
13## Instructions
14
15### Path Resolution
16
17Resolve file paths based on your execution context:
18
19- **Plugin context** (`${CLAUDE_PLUGIN_ROOT}` is set): Read knowledge from `${CLAUDE_PLUGIN_DATA}/knowledge/` (user data), falling back to `${CLAUDE_PLUGIN_ROOT}/knowledge/` (seed data). Read research from `${CLAUDE_PLUGIN_ROOT}/knowledge/research/`.
20- **Clone/symlink context** (default): Read knowledge from `knowledge/` relative to the project root (research is at `knowledge/research/`).
21
22### Pre-Execution Knowledge Check
23
24Before drafting SLTs, read the knowledge base for patterns that should influence your work. **If any knowledge file does not exist, skip it and proceed without prior patterns — note "No prior data available" in output.**
25
261. **Read `knowledge/slt-patterns/verb-bank.yaml`**
27 - Note effective verbs by Bloom's level
28 - Prefer verbs with high success_count
29
302. **Read `knowledge/slt-patterns/quality-issues.yaml`**
31 - Note problematic patterns to avoid
32 - Especially avoid patterns with high frequency
33
343. **Surface knowledge to user** (if relevant patterns exist):
35 ```markdown
36 ### Tips from Previous Courses
37
38 **Effective verbs at this level:** compare, distinguish, implement (12 successes)
39 **Patterns to avoid:** "understand X" (flagged 8 times), task-focused phrasing
40 ```
41
42---
43
44The user will describe a course or module they want to create. Gather the following information (ask if not provided):
45
461. **Topic**: What is the course/module about?
472. **Audience**: Who are the learners? What's their background?
483. **Learning goals**: What should learners be able to do after completing this?
494. **Module count**: How many modules? (Default: 3-4)
505. **SLTs per module**: How many SLTs per module? (Default: 2-4)
51
52Always read `knowledge/research/slt-research-report.md` for full research context before drafting.
53
54### The SLT Formula
55
56Every SLT must follow this structure:
57
58**I can + [measurable verb] + [specific outcome] + [observable evidence/context]**
59
60Examples:
61- Weak: "I can understand blockchain" (unmeasurable, vague)
62- Better: "I can explain what a blockchain is" (measurable, but no evidence)
63- Strong: "I can compare a Portable Access Token to a traditional platform account by identifying at least two differences in ownership, portability, and revocability" (measurable verb, specific outcome, observable evidence)
64
65### Verb Selection (Bloom's Taxonomy)
66
67Use verbs that match the cognitive level appropriate for the content:
68
69| Level | Verbs | When to Use |
70|-------|-------|-------------|
71| **Remember** | list, name, identify, recall | Foundational facts, terminology |
72| **Understand** | explain, describe, summarize, compare | Conceptual understanding |
73| **Apply** | use, demonstrate, implement, execute | Procedural skills |
74| **Analyze** | distinguish, examine, compare, contrast | Breaking down complex topics |
75| **Evaluate** | judge, justify, critique, assess | Making judgments |
76| **Create** | design, construct, develop, produce | Building something new |
77
78**Progression principle**: Early modules should include more Remember/Understand/Apply. Later modules can include Analyze/Evaluate/Create.
79
80### Verbs to Avoid
81
82Never use these unmeasurable verbs:
83- understand, know, learn, appreciate, be aware of, become familiar with
84
85These cannot be assessed. Replace with specific, observable actions.
86
87### Output Format
88
89Generate SLTs in this exact format:
90
91```markdown
92# SLTs: [Course Name]
93
94## Module 1: [Module Title]
95
96- 1.1: I can [verb] [specific outcome] [evidence/context].
97- 1.2: I can [verb] [specific outcome] [evidence/context].
98- 1.3: I can [verb] [specific outcome] [evidence/context].
99
100## Module 2: [Module Title]
101
102- 2.1: I can [verb] [specific outcome] [evidence/context].
103- 2.2: I can [verb] [specific outcome] [evidence/context].
104
105## Module 3: [Module Title]
106
107- 3.1: I can [verb] [specific outcome] [evidence/context].
108- 3.2: I can [verb] [specific outcome] [evidence/context].
109- 3.3: I can [verb] [specific outcome] [evidence/context].
110```
111
112### Guidelines
113
1141. **One capability per SLT.** If an SLT has "and" connecting two different skills, split it.
115
1162. **Make it assessable.** Ask: "Could a teacher design an assignment to verify this?" If not, rewrite.
117
1183. **Write for the learner.** SLTs should make learners curious, not anxious. Name tools and frameworks, but leave implementation details to the lessons.
119
1204. **Build progression.** Module 1 SLTs should be achievable early. Later modules can build on earlier ones.
121
1225. **2-4 SLTs per module is ideal.** More than 5 per module suggests the module should be split.
123
1246. **Consider the assignment.** Each module needs one assignment that can assess all its SLTs. If the SLTs don't fit a coherent assignment, reorganize.
125
1267. **Mark optional modules.** If a module is optional/advanced, note it in the title: "Module 4: [Title] (Optional)"
127
128### Quality Checklist
129
130Before outputting, verify each SLT:
131
132- [ ] Starts with "I can"
133- [ ] Uses a measurable verb (not understand/know/learn)
134- [ ] Has a specific outcome (not vague)
135- [ ] Includes observable evidence or context
136- [ ] Can be assessed through an assignment
137- [ ] Is appropriate for the stated audience
138- [ ] Fits the cognitive progression (Bloom's levels build across modules)
139
140### After Drafting
141
142Suggest the user:
1431. Review and refine the SLTs with their team
1442. Run `/assess-slts` to get quality feedback
1453. Create `00-course.md` with lesson types and assignments based on the finalized SLTs