| name | skill-authoring-workflow |
| argument-hint | [source content or skill to update] |
| description | Turn raw PM content into a compliant, publish-ready skill. Use when creating or updating a repo skill without breaking standards. |
| intent | Create or update PM skills without chaos. This workflow turns rough notes, workshop content, or half-baked prompt dumps into compliant `skills/<skill-name>/SKILL.md` assets that actually pass validation and belong in this repo. |
| type | workflow |
| best_for | ["Creating a new repo skill from notes or source material","Updating an existing skill while keeping standards intact","Running the full authoring and validation workflow before commit"] |
| scenarios | ["Help me turn these workshop notes into a new PM skill","I need to update an existing skill without breaking the repo standards","What workflow should I use to author a new skill in this repo?"] |
Purpose
Create or update PM skills without chaos. This workflow turns rough notes, workshop content, or half-baked prompt dumps into compliant skills/<skill-name>/SKILL.md assets that actually pass validation and belong in this repo.
Use it when you want to ship a new skill without "looks good to me" roulette.
Input
Bring the raw material and the intent — rough is fine; the workflow exists to get it the rest of the way:
- Works best with: the source content (notes, transcript, framework, prompt sequence) or the existing skill you want to update
- Also useful: the intended skill type (component/interactive/workflow), target audience, and any naming preference
If you supply this inline with your request (e.g., "turn research/pricing-workshop-notes.md into an interactive advisor"), the workflow starts at Phase 1 with that context — it won't re-ask for what you already gave. If you provide nothing, it opens by asking what content you want to turn into a skill and offers the entry modes from the facilitation protocol.
Example: Use skill-authoring-workflow: convert research/pricing-workshop-notes.md into an interactive pricing advisor.
Key Concepts
Dogfood First
Use repo-native tools and standards before inventing a custom process:
scripts/find-a-skill.shscripts/add-a-skill.shscripts/build-a-skill.shscripts/test-a-skill.shscripts/check-skill-metadata.py
Pick the Right Creation Path
- Guided wizard (
build-a-skill.sh): Best when you have an idea but not final prose.
- Content-first generator (
add-a-skill.sh): Best when you already have source content.
- Manual edit + validate: Best for tightening an existing skill.
Definition of Done (No Exceptions)
A skill is done only when:
- Frontmatter is valid (
name, description, intent, type)
- Section order is compliant (Purpose, Input, Key Concepts, Application, Examples, Common Pitfalls, References)
- Metadata limits are respected (
name <= 64 chars, description <= 200 chars)
