course-development-orchestrator¶
所属包: course
Drive course projects end to end — plans, outlines, content, labs, learner/instructor materials, QA, QC, and release decisions. Also triggers for broad course development or curriculum requests.
兼容性: Designed for OpenCode. Assumes repo-local .opencode/skills discovery
Purpose¶
Coordinate course development work across the other course skills in this pack. Use this as the default entry skill when the user asks for broad course design, course revision, course production, or course project management.
When to activate¶
Activate when the user asks for any of the following in a broad or mixed way:
- build or revise a training course
- design a curriculum, syllabus, or teaching plan
- prepare course content, labs, learner handouts, or teacher notes
- review course quality, readiness, consistency, or delivery risk
- organize a course project repository or artifact set
If the request is narrow and clearly belongs to one specialized skill, let that skill lead. This skill should then act as a coordinator only.
Default workflow¶
- Determine the workstream:
- planning
- outline/syllabus
- lesson content
- labs/exercises
- learner materials
- instructor materials
- QA review
- QC remediation and reporting
-
repository/directory organization
-
Decide whether the request is:
- create from scratch
- modify existing material
- review/critique
- normalize/restructure
-
generate deliverable package
-
Produce or update a minimal execution frame before drafting:
- target audience
- training objective
- delivery format
- expected duration/lesson count
- prerequisite knowledge
- required outputs
- quality bar
-
explicit constraints from the user
-
Route to the most relevant specialized skill:
development-plan-governancecourse-outline-designcourse-content-authoringcourse-lab-designlearner-materialsinstructor-reference-materialscourse-quality-assurancecourse-quality-control-reportingcourse-directory-structurereference-document-reviewmarkdown-course-writing-
drawio-course-diagrams -
Keep outputs aligned:
- naming
- chapter numbering
- terminology
- difficulty progression
- artifact locations
- QA status
Confirmation gates (Gate 1 / Gate 2)¶
Two interaction gates refine the default workflow between requirements gathering (step 3, execution frame) and downstream production (step 4, routing). They are refinements of the existing flow — the quality gates defined in the project AGENTS.md (§8) remain unchanged, and these gates do not replace them.
Gate 1 — 执行帧澄清 (execution-frame clarification)¶
Before finalizing the execution frame (workflow step 3):
- Ask at most 3 rounds of clarifying questions, ONE question per round (use the question tool).
- Select questions from
references/clarification-bank.md, grouped by course type (standard-training / workshop / k12 / vocational). - Always offer an explicit skip option; if the user skips, record the clarification as
skippedand proceed with stated assumptions. - Once the frame is confirmed, persist the course type to
docs/00-project/course-type.yaml(fieldtype:, e.g.type: standard-training) so thatqa_scan.pycheck #9 can validate the outline against the matching constraints preset.
... (完整 SKILL.md 中还有 38 行)