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

1. Determine the workstream:
2. planning
3. outline/syllabus
4. lesson content
5. labs/exercises
6. learner materials
7. instructor materials
8. QA review
9. QC remediation and reporting

10. repository/directory organization

11. Decide whether the request is:

12. create from scratch
13. modify existing material
14. review/critique
15. normalize/restructure

16. generate deliverable package

17. Produce or update a minimal execution frame before drafting:

18. target audience
19. training objective
20. delivery format
21. expected duration/lesson count
22. prerequisite knowledge
23. required outputs
24. quality bar

25. explicit constraints from the user

26. Route to the most relevant specialized skill:

27. development-plan-governance
28. course-outline-design
29. course-content-authoring
30. course-lab-design
31. learner-materials
32. instructor-reference-materials
33. course-quality-assurance
34. course-quality-control-reporting
35. course-directory-structure
36. reference-document-review
37. markdown-course-writing

38. drawio-course-diagrams

39. Keep outputs aligned:

40. naming
41. chapter numbering
42. terminology
43. difficulty progression
44. artifact locations
45. QA status

Output rules

• Prefer Markdown unless the user explicitly asks for another format.
• Keep a stable hierarchy: project -> module -> lesson -> artifact.
• Separate objective, content, activity, deliverable, and quality gate.
• When reviewing, distinguish clearly between:
• factual issue
• structural issue
• pedagogical issue
• execution issue
• formatting issue

... (完整 SKILL.md 中还有 17 行)