Work Unit Protocol

A work unit is one scope-bounded outcome with a measurable completion criterion. This skill is the rhythm each unit follows — from kickoff through closing report.

Phases

1. Kickoff

• Scope stated in one sentence with a measurable completion criterion.
• Scan existing tooling (installed plugins, skills, commands, agents, MCPs) — never re-build.
• Identify dependencies and blocked-by relationships.
• If creating or modifying a library, confirm no parallel module already exists.

2. Plan

• List artifacts to be produced with paths.
• List tests to be written (success path / idempotent / WhatIf / error).
• Identify library modules to extend vs. create. Default: extend.
• Note any policy files (policies/*.json) that must stay in sync.