<< All versions

Skill v1.0.0

currentAutomated scan100/100
devos-ing/omni-skills/writing-workflow-skills
──Details
PublishedNovember 4, 2026 at 08:43 AM
Content Hashsha256:10c61461fbef6fa0...
Git SHA0e48d3dced0d
──Files
Files (1 file, 1.6 KB)
SKILL.md1.6 KBactive
SKILL.md · 51 lines · 1.6 KB

name: writing-workflow-skills description: Use when writing or reviewing Omniskills entry skills, local role skills, gates, and handoffs. metadata: version: "1.0.0"


Writing Workflow Skills

Use creating-bundle-skills for the whole bundle. Use this skill to keep one entry skill and its local companions aligned with workflow.json.

Dependency Palette

NeedMatt Pocock skill
Clarify one question at a timemattpocock:grilling
Sharpen terminology and decisionsmattpocock:grill-with-docs
Publish the approved specificationmattpocock:to-spec
Slice vertical ticketsmattpocock:to-tickets
Prototype an uncertain interfacemattpocock:prototype
Implement approved workmattpocock:implement, mattpocock:tdd
Diagnose or reviewmattpocock:diagnosing-bugs, mattpocock:code-review

Declare every selected dependency. Keep model-invoked companion skills such as tdd and code-review installed even when a top-level implement step invokes them.

Entry Skill Contract

An entry skill should state:

  1. The approved input it needs.
  2. The shortest ordered flow.
  3. Each human approval gate and stop condition.
  4. What happens when a dependency or execution capability is missing.
  5. The final evidence, residual risk, and next action.

A local role skill owns one decision or artifact. It should return only:

markdown
-Decision:
-Evidence:
-Risk:
-Handoff:

Keep the skill name aligned with its folder and manifest source. Use exact dependency names, never silently skip a gate, and do not restate the whole workflow inside every local role.

All versions