Bloom Obsidian Concept Learning

Problem

When learning a concept, output often stops at a one-line definition or jumps into long prose, without a clear progression from “I have heard of it” to being able to explain, use, compare, and extend it. For notes intended for Obsidian, the result can also be over-formatted, inconsistent, or limited to recall questions. This skill is aimed at engineers and knowledge workers who need concept explanations that become reusable, reviewable, lightweight Markdown notes.

How It Works and Where It Applies

It first detects intent. A simple “What is X?” request gets only a definition, plain-language explanation, key example, and next-step prompt. A “turn this into study notes” or “learn systematically” request expands into a fuller note scaffold. The main workflow is:
- Start from a foundation: give a one-line definition and a plain-language explanation before adding structure.
- Progress through Bloom levels: remember, understand, apply, analyze, evaluate, and create act as a depth control, not a rigid checklist.
- Produce Obsidian-friendly Markdown: prefer concise headings, bullets, short paragraphs, and self-check questions over decorative formatting.
- Route by task type: map explanation, comparison, self-test, and systematic learning requests to the smallest useful output instead of forcing every section.

It is best for concept learning, note organization, and layered self-testing; for narrow factual questions, a direct answer is usually enough.