writing-workflow-skills

1# Writing Workflow Skills
2 
3The authoring checklist for workflow skills in `packages/pi-thinkrail-workflow`. It carries the *what
4to do*; every *why* — the concept model, the three roles, the meta-rules cited as "(rule N)" below —
5lives once in the workflow-system spec beside this directory, **`skills/SPEC.md`**. Read that spec
6first; where this checklist and that spec disagree, the spec wins.
7 
8**Workspace guard.** This checklist edits `packages/pi-thinkrail-workflow` in the thinkrail repo. If
9that package is not in the current workspace (a ThinkRail-managed project, where these skills are a
10read-only staged cache), the family cannot be extended from here: say so in one line and stop — the
11terminal state for foreign workspaces.
12 
13## Design (before writing)
14 
15- [ ] Read `skills/SPEC.md`: concept model, the three roles, meta-rules 1–15.
16- [ ] Scope the skill to one externally reachable workflow — or, for a concept, one topic (rule 1).
17      Internal forks, branches, stages, and shared tails are sibling docs, planned with the choice
18      rules in the doc (or spine) before the fork; a doc is promoted to its own skill when it needs
19      independent addressability (an external caller, a genuine self-trigger, or a direct entry point
20      such as a `/skill:` command seed) — never for shape or size alone.
21- [ ] Pick the role (rule 2): **router** (classification rules + handoffs, nothing else), **worker**
22…