curriculum-architect

Creating a consistent curriculum structure for a Quarto lecture course requires generating a `_curriculum.md` backbone file. This file serves as a single source of truth for chapter modules, learning objectives, and terminology conventions to prevent content drift.

Tracking learning objectives and chapter status in Markdown involves maintaining a dedicated curriculum file. You can apply targeted updates to mark chapters as planned, active, or final, ensuring course-wide coherence without restarting the entire planning process.

Updating lecture planning documents without rewriting the curriculum is done through targeted updates. You can revise individual chapter themes, register newly created modules, and adjust learning objectives directly within the existing Markdown structure.

Curriculum-architect does not require any external dependencies to generate course workflows. It operates independently to interview authors, read existing briefing inputs, and output a plain Markdown curriculum file for downstream use.

Yes, you can use existing wiki inputs and chapter cues to initialize a new curriculum file. The system reads these available sources during the INIT mode to automatically generate the complete initial chapter and module structure.

Lecture course terminology drifts between chapters when there is no single source of truth. Establishing required terminology conventions within a central Markdown curriculum file ensures downstream skills and chapters remain aligned.