The /learn workflow captures reusable knowledge and experience accumulated during development, storing them as structured documents in Areas/Learning/.
Commands Overview
/learn [topic-name] # Create a new learning document
Knowledge Capture Flow
Identify topic → Classify category → Create learning file → Update index → Cross-reference
1. Identify the Topic
Summarize the lesson or experience. Determine the category:
- Technical — Git, DevOps, Architecture, CSS, Frameworks
- Process — Workflows, Best Practices, Patterns
- Domain — Business logic, Industry knowledge
2. Create Learning File
Creates a .md file at Areas/Learning/[topic-name].md using the standard template:
# [Lesson Title]
> [Core value summary]
## Context
- Situation or error encountered
- Why the old method was ineffective
## Solution
- Detailed handling method
- Tools or techniques used
## Key Learnings
- Point 1: Technical insight
- Point 2: Process improvement
- Point 3: Important notes
## Code Example (if applicable)
- Code snippet illustrating the solution
3. Update Index
Adds a link to the new lesson in Areas/Learning/README.md under the appropriate category section (e.g., Git, Development, Security, Best Practices).
4. Cross-Reference (Optional)
If the lesson originated from a specific project, adds a reference back in the project’s session log.
Integration Points
| Workflow | Relationship |
|---|---|
/plan | Step 4 scans Areas/Learning/ to avoid past mistakes |
/brainstorm | Option E exits to /learn for cross-project insights |
/end | May trigger /learn for significant discoveries |
/retro | Graduates retrospective beads to learnings |
/inbox | Routes learning-type files to Areas/Learning/ |
→ Workflow /brainstorm — Ideation before planning → Workflow /end — Close session and log progress