| name | course-methodology-playbook |
| description | Reusable course-development methods, review heuristics, historical conventions, playbooks, or packaged guidance extracted from prior course discussions and project practice. |
| license | Proprietary |
| compatibility | Designed for OpenCode. Assumes repo-local `.opencode/skills` discovery and standard read/edit/bash tools; optional scripts should run through a repo-local uv environment; requires uv and Python 3.11+. |
| metadata | {"pack":"opencode-course-skills"} |
Purpose
Capture and reuse methods that repeatedly work in course development.
When to use
Activate when the user asks for:
- methodology
- handbook
- playbook
- standard approach
- reusable process
- historical course-development know-how
- packaging prior discussion into a reusable rule set
Method extraction model
When turning prior work into methodology:
- identify repeated successful pattern
- separate principle from one-off detail
- define trigger conditions
- define default procedure
- list common failure modes
- provide reusable templates or checklists
Output forms
- one-page method note
- workflow playbook
- review handbook
- decision matrix
- reusable checklist
- trigger examples
Gotchas
- Do not mistake one project preference for a universal rule.
- Do not make methodology too generic to be operational.
- Do not store historical noise that does not change future behavior.
- Do not collapse QA, QC, pedagogy, and project management into one vague doctrine.
See:
references/course-methodology.mdassets/method-note-template.md
