Skip to content
cccskills
FreePublished on GitHub

course-builder

[Content] Use when a workflow step or the user asks for course material: Bloom objectives, modules, lessons, exercises and assessments.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md7.9 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Quick Summary

Goal: Build a learner-ready course with Bloom-aligned objectives, progressive modules, lessons, practice, and assessments so learners achieve and demonstrate intended outcomes.

Summary:

  • Purpose: Turn user/research scope into a template-compliant course with aligned outcomes, practice, and assessments.
  • Main flow: Phase 0 detect course context; (1) define audience, prerequisites, duration, outcomes; (2) map objectives to Bloom; (3) structure modules → lessons → exercises → assessments.
  • Continue: (4) develop each lesson's duration, concept, explanation, examples, exercise, assessment; (5) create module knowledge checks + comprehensive final; (6) review alignment, evidence, progression, prerequisites.
  • Gates/output: Create TaskCreate tasks before work; map every objective to Bloom; cite every factual claim inline [N]; use the enforced template; write docs/knowledge/courses/{descriptive-slug}.md; no modes/flags specified.

Workflow:

  1. Define scope — Target audience, prerequisites, duration, objectives
  2. Map objectives — Align to Bloom's taxonomy
  3. Structure curriculum — Modules → Lessons → Exercises → Assessments
  4. Develop content — Per lesson: concept, explanation, examples, exercise
  5. Create assessments — Knowledge checks + final assessment
  6. Review pedagogy — Alignment, progressive difficulty, prerequisite chains

Key Rules:

  • Every objective maps to a Bloom's taxonomy level; include at least one Apply-level objective.
  • Build progressive complexity; each module builds on previous prerequisites.
  • Derive lesson depth, examples, exercises, and assessment format from learner context and objectives; do not fill templates mechanically.
  • Use enforced template .claude/templates/course-outline-template.md.
  • Every factual claim and number in the content ends with an inline [N] citation mapped to a Resources & References row (Title, URL, Author/Org, Date, Tier). Factual claims rest on 2+ independent sources; a single-source claim is marked unverified and held below 60% confidence. Exercises, assessment items and constructed examples are course design, not factual claims.

Critical thinking: Be skeptical; reason sequentially; trace evidence for every claim; state confidence percentages; ideas >80%.

Contents

Course Builder

Phase 0: Detect Course Context

Classify course type, learner level, delivery mode, and constraints before choosing depth, examples, exercises, or assessment formats; ask for missing inputs or state assumptions.

Bloom's Taxonomy Reference

LevelVerb ExamplesAssessment Type
RememberDefine, list, recall, identifyMultiple choice, fill-in-blank
UnderstandExplain, describe, summarize, interpretShort answer, paraphrase
ApplyUse, implement, solve, demonstrateProblem sets, exercises
AnalyzeCompare, contrast, examine, differentiateCase studies, analysis papers
EvaluateJudge, critique, assess, justifyDebates, reviews, peer assessment
CreateDesign, construct, produce, developProjects, portfolios, presentations

Step 1: Define Learning Scope

Gather from user or research (in a research run, read the evidence base tmp/research/_evidence-{slug}.md that web-research --chain=deep-dive returned and cite its sources): Target audience — who + background; Prerequisites — prior knowledge; Duration — total hours/weeks; Desired outcomes — learner capabilities after course.

Step 2: Map Objectives to Bloom's

Assign a Bloom's level to each desired outcome:

  • Start lower: Remember → Understand; progress higher: Apply → Analyze → Evaluate → Create; ensure at least one objective at Apply level or above.

Step 3: Structure Curriculum

Organize 3-8 modules per course:

  • 2-5 lessons/module; module-specific learning objectives; modules build through a prerequisite chain.

Step 4: Develop Lesson Content

For each lesson, provide: (1) Duration — estimated time; (2) Concept — core idea in 1-2 sentences; (3) Explanation — theory, context, why it matters; (4) Examples — 2-3 real-world illustrations; (5) Exercise — hands-on practice activity; (6) Assessment — how to verify learning.

Step 5: Create Assessments

Per module: Knowledge check — 3-5 questions covering key concepts; questions align with module's Bloom's level. Final: Comprehensive assessment — covers all modules; Mix of Bloom's levels — at least 1 question per level taught.

Step 6: Review Pedagogy

Verify objective/activity/assessment alignment, evidence for content claims, labelled assumptions, progressive difficulty, and prerequisite chain; state confidence.

Output

Write to docs/knowledge/courses/{descriptive-slug}.md using enforced template from .claude/templates/course-outline-template.md. List every cited source in Resources & References with Title, URL, Author/Org, Date and Tier; every [N] resolves to a row and every row is cited.


[IMPORTANT] Create small tasks with TaskCreate before work, including a final review task.

Closing Reminders

IMPORTANT MUST ATTENTION Goal: Build a learner-ready course with Bloom-aligned objectives, progressive modules, lessons, practice, and assessments so learners achieve and demonstrate intended outcomes. IMPORTANT MUST ATTENTION Course flow: Phase 0 detect context; (1) define scope; (2) map every objective to Bloom; (3) structure 3-8 modules with 2-5 lessons and prerequisite links; (4) develop each lesson's duration, concept, explanation, examples, exercise, and assessment; (5) create 3-5-question module checks plus a comprehensive final with every taught Bloom level; (6) review alignment, evidence, assumptions, progression, and prerequisites.

IMPORTANT MUST ATTENTION Gate/output: create TaskCreate tasks before work and a final review task; cite every factual claim inline [N] mapped to a Resources & References row (Title, URL, Author/Org, Date, Tier), with a single-source claim marked unverified below 60% confidence; use enforced .claude/templates/course-outline-template.md; write docs/knowledge/courses/{descriptive-slug}.md; no modes/flags specified.

IMPORTANT MUST ATTENTION use user/research evidence, label assumptions, and state confidence; NEVER fabricate course facts.

Anti-Rationalization:

EvasionRebuttal
"Course is simple"Wrong assumptions waste time; apply the full flow.
"This fact is common knowledge"Cite it [N] to a Resources & References row; with one source, mark it unverified below 60%.
"Just do it"Create task tracking first; skip depth only when justified, never skip tracking.

[TASK-PLANNING] MUST ATTENTION Before acting, analyze scope; create small TaskCreate tasks, cite every factual claim inline [N] to a Resources & References row, and complete a final quality review.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

[Documentation] Use when generating, smart-merging or refactoring the root AI context (CLAUDE.md, AGENTS.md) and its Claude/Codex projections. Config file only: project-config.

The English summary is being prepared. Showing the original description.

duc01226/EasyPlatform12Updated Oct 18, 2026

[Code Quality] Use when a workflow step or the user asks for AI code or plan review: LLM calls, prompts, agents, RAG, evals and guardrails. --mode={code|plan}; --report-only is read-only.

The English summary is being prepared. Showing the original description.

duc01226/EasyPlatform12Updated Oct 18, 2026

[Architecture] Use when a workflow step or the user asks for architecture design, compliance review, scalability grading or whole-project audit via --mode={design|review|scalability|full}.

The English summary is being prepared. Showing the original description.

duc01226/EasyPlatform12Updated Oct 18, 2026

[Content] Use when a workflow step or the user asks for product/feature ideation with ranked opportunities and validation tests. --mode={roadmap|scope}.

The English summary is being prepared. Showing the original description.

duc01226/EasyPlatform12Updated Oct 18, 2026

[Content] Use when a workflow step or the user asks for business viability: Business Model Canvas, financials, risks and go-to-market recommendation.

The English summary is being prepared. Showing the original description.

duc01226/EasyPlatform12Updated Oct 18, 2026

[Code Quality] Use when a workflow step or the user asks for a focused code-change review: staged, unstaged, branch diff or simple pull request. --fix-loop fixes and re-reviews. Complex pull request: workflow-review-changes; rationale: why-review.

The English summary is being prepared. Showing the original description.

duc01226/EasyPlatform12Updated Oct 18, 2026

See all skills by duc01226

Report a problem with this skill