Curriculum update

Curriculum Update

Maintain structured learning paths that track what the developer should learn over time. Insert new concepts in prerequisite order, create new paths when needed, and update confidence scores.

Configuration

Read config.json from the ai-dev-os skill directory. If configured is false or the file is missing, STOP and tell the user:

"Please run /configure-ai-dev-os to set up your Obsidian vault path and Linear team."

• Obsidian vault: Use the obsidian_vault_path value from config.
• Curriculum folder: curriculum/

Input

• Concept extraction report (detected concepts with dispositions)
• Lesson generation summary (lessons created, prerequisite gaps)

Procedure

Step 1: Read existing curricula

1. Call mcp__obsidian__obsidian_list_notes on the curriculum/ folder.
2. For each curriculum file, call mcp__obsidian__obsidian_read_note to read its contents.
3. Build a map of: curriculum name -> ordered list of concepts -> confidence levels.

Step 2: Classify new concepts into curricula

For each new or updated concept from the extraction report:

1. Determine which curriculum path it belongs to based on:

   • Concept category (reliability, data, architecture, performance, security, etc.)
   • Prerequisites (a concept should appear after its prerequisites)
   • Related concepts already in a curriculum

2. If a fitting curriculum exists -> add the concept in the correct position (after its prerequisites, before concepts that depend on it).

3. If no fitting curriculum exists -> create a new curriculum file.

Step 3: Update existing curriculum files

For each curriculum that needs updates:

1. Use mcp__obsidian__obsidian_search_replace to insert the new concept in the correct position.
2. Format each concept entry as:

   N. [[concept name]] — confidence: X.X
   

3. Ensure prerequisite ordering is maintained.

Step 4: Create new curriculum files (if needed)

If a new curriculum path is needed:

1. Create curriculum/<topic-slug>.md with:

---
type: curriculum
topic: [Topic Name]
created: [today ISO 8601]
updated: [today ISO 8601]
---

# [Topic Name]

## Learning Path

1. [[concept A]] — confidence: 0.0
2. [[concept B]] — confidence: 0.0
3. [[concept C]] — confidence: 0.2

## Suggested Next Topics
- [related area 1]
- [related area 2]

2. Call mcp__obsidian__obsidian_update_note to write the file.

Step 5: Update confidence scores

For concepts that were just worked on (appeared in the current ticket diff):

1. Read current confidence from concept note frontmatter.
2. Increase confidence by 0.1-0.2 (encountering a concept in practice increases understanding).
3. Update via mcp__obsidian__obsidian_manage_frontmatter.
4. Update the corresponding curriculum entry to reflect the new confidence.

Do not exceed 1.0. Do not decrease confidence unless explicitly requested.

Gotchas

• Prerequisite ordering is inferred — it can be wrong. The user should review curriculum files periodically.
• Confidence scores only increase (by 0.1-0.2 per encounter). They never decrease automatically.

Output

## Curriculum Update Summary

### Updated Curricula
| Curriculum | Concepts Added | Concepts Updated |
|-----------|---------------|-----------------|

### New Curricula Created
| Curriculum | Topic | Initial Concepts |
|-----------|-------|-----------------|

### Confidence Updates
| Concept | Old | New |
|---------|-----|-----|