Individual skill
work
Execute an approved wish in dependency order with scoped workers, independent review, bounded repairs, and verified completion.
skills/work/SKILL.md
Source commit 9ed2e1695357402f5eedc1b540f73b638a5bfba7
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 351
- Repository last updated
- Nov 9, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-agents Repository topic
- cli Repository topic
- developer-tools Repository topic
- claude Repository topic
- claude-code Repository topic
- context-engineering Repository topic
- ai-developer-tools Repository topic
- anthropic Repository topic
- automation Repository topic
- autonomous-agents Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 10,463 bytesSKILL.mdcore · 10,463 bytesSKILL.mdcore · 10,463 bytesagents/openai.yamlasset · 228 bytesreferences/exact-path-commit.mddoc · 3,304 bytes
Read excerpt
# Work
Read the wish and require persisted `APPROVED`, or `IN_PROGRESS` for a resume. The coordinator sets `IN_PROGRESS` before execution and owns task completion and review evidence. Documents remain the instruction source.
## Dispatch
Derive ready waves from WISH.md’s Execution Strategy and per-group `depends-on`. A task DB row being `ready` does not prove its dependencies are met; the DAG lives in the document.
Order the work inside a group as tracer bullets: dispatch the thinnest slice that runs end to end first, then widen it. A slice that crosses every layer proves the interfaces exist and tells the next slice what it may assume, while layers finished separately prove nothing until the last one lands.
Delegate each independent group through the active runtime’s native surface, using the plan’s portable role and supported runtime configuration. Inherit the active model unless the user or an evidenced capacity diagnosis authorizes a change. If delegation is unavailable, report that limitation; do not pretend independent review occurred.
Give each worker its goal, deliverables, criteria, validation, dependencies, owned files, relevant context, and stop conditions. Include task identifiers when available. Keep doing independent coordination/integration work while workers run.
