agent-study-note-playbook

Create or review structured study notes from narrative, case-based, parable, dialogue, puzzle, or problem-framing sources where the learning unit is misframing → reframing → consequence → reader application. Do not use for ordinary expository textbooks, technical pattern catalogs, or technical essay collections whose primary unit is claim → reasoning → practice/context; use the corresponding textbook or technical-essay workflow.

Create or review structured study notes from technical essay collections, engineering blogs, opinionated practice books, industry criticism, and experience-based software or engineering writing where the learning unit is claim → reasoning → anecdote/context → practice or applicability limit. Do not use for systematic textbook taxonomies or for problem-framing sources whose lesson depends on misframing → reframing → consequence.

Review textbook-style Markdown learning notes for semantic usefulness. Use for concept, method, pattern, antipattern, chapter, and review notes that should explain why an idea matters, when to use it, inputs/outputs, examples, pitfalls, relationships, and self-check prompts. Do not use for narrative problem-framing notes, technical essay notes, Markdown linting, Obsidian link checks, or final pack submission gates.

Final gate for structured study-note packs. In textbook-full-gate mode, verify textbook note-type contracts, deterministic checker results, representative semantic learning quality, tags, wikilinks, corruption scans, and publish/sync readiness. For narrative or technical-essay packs, use only explicit shared-mechanical-only mode after their workflow semantic review; do not apply textbook headings or textbook semantic checks.

Create or refresh structured textbook study notes from books, PDFs, OCR text, or existing Markdown packs. Use for expository or technical textbook sources whose durable learning units are stable concepts, methods, processes, patterns, antipatterns, or chapter-level explanations within a systematic taxonomy. Do not use as the primary workflow for narrative, case-based, parable, dialogue, puzzle, problem-framing, technical-essay, blog, industry-criticism, or argument-first sources; use the corresponding narrative or technical-essay workflow.