Study Loop
Turn exploratory technical learning into a resumable loop. Use the configured Obsidian documentation root as the durable source of truth; keep code changes out of this skill unless the user separately requests implementation.
Configuration
Read <AGENT_HOME>/local-config/study-loop/config.json when present. If absent, use the configured p-task docs root as the default source and create only the study-loop config when needed:
{ "docsRoot": "<absolute-obsidian-collection-root>" }
Never hardcode a personal path in this skill.
Obsidian structure
For a repository or subject named <subject>, use <docsRoot>/<subject>/study/:
00-overview.md: subject, goals, boundaries, and current verified state.10-roadmap.md: ordered learning phases and the next lesson.20-source-map.md: source/module map, key entry points, and durable concepts.30-decisions.md: confirmed learning interpretations or scope decisions.31-open-questions.md: unresolved questions that should shape future study.32-risk-log.md: blockers, misleading assumptions, and validation gaps.plans/: multi-session study plans.records/: one concise record per completed study session.
Create missing files only when the user asks to start tracking a subject. Preserve existing notes and update relevant sections instead of duplicating content.
Study loop
- Resume first: read the overview, roadmap, source map, latest record, and open questions.
- Define a narrow lesson goal, source files or materials, expected understanding, and stopping condition.
- Study from primary project sources. Explain unfamiliar syntax or design using the learner's background and a short concrete trace.
- Record durable findings with evidence locations, remaining questions, risks, and the next lesson.
- Verify understanding with a small code-reading exercise, call-chain trace, or user restatement.
- Write back the result to external docs before ending the session. Update the roadmap when sequencing or current focus changes.
Boundaries
- This skill manages learning state and plans; it does not silently modify the studied repository.
- Distinguish source facts, interpretations, and hypotheses in notes.
- Do not mark a lesson complete without a source location or concrete trace supporting it.
- Questions that change architecture, security, data behavior, or implementation scope belong in
31-open-questions.md and remain unconfirmed until resolved.
1---2name: study-loop-23description: Manage structured source-code learning across sessions by maintaining an external study plan, progress records, questions, and verified next steps. Use when learning a repository, framework, language, or technical system over multiple sessions.4---56# Study Loop78Turn exploratory technical learning into a resumable loop. Use the configured Obsidian documentation root as the durable source of truth; keep code changes out of this skill unless the user separately requests implementation.910## Configuration1112Read `<AGENT_HOME>/local-config/study-loop/config.json` when present. If absent, use the configured p-task docs root as the default source and create only the study-loop config when needed:1314```json15{ "docsRoot": "<absolute-obsidian-collection-root>" }16```1718Never hardcode a personal path in this skill.1920## Obsidian structure2122For a repository or subject named `<subject>`, use `<docsRoot>/<subject>/study/`:2324- `00-overview.md`: subject, goals, boundaries, and current verified state.25- `10-roadmap.md`: ordered learning phases and the next lesson.26- `20-source-map.md`: source/module map, key entry points, and durable concepts.27- `30-decisions.md`: confirmed learning interpretations or scope decisions.28- `31-open-questions.md`: unresolved questions that should shape future study.29- `32-risk-log.md`: blockers, misleading assumptions, and validation gaps.30- `plans/`: multi-session study plans.31- `records/`: one concise record per completed study session.3233Create missing files only when the user asks to start tracking a subject. Preserve existing notes and update relevant sections instead of duplicating content.3435## Study loop36371. Resume first: read the overview, roadmap, source map, latest record, and open questions.382. Define a narrow lesson goal, source files or materials, expected understanding, and stopping condition.393. Study from primary project sources. Explain unfamiliar syntax or design using the learner's background and a short concrete trace.404. Record durable findings with evidence locations, remaining questions, risks, and the next lesson.415. Verify understanding with a small code-reading exercise, call-chain trace, or user restatement.426. Write back the result to external docs before ending the session. Update the roadmap when sequencing or current focus changes.4344## Boundaries4546- This skill manages learning state and plans; it does not silently modify the studied repository.47- Distinguish source facts, interpretations, and hypotheses in notes.48- Do not mark a lesson complete without a source location or concrete trace supporting it.49- Questions that change architecture, security, data behavior, or implementation scope belong in `31-open-questions.md` and remain unconfirmed until resolved.
askairo