Add agent-workflow skill skeleton

skills/agent-workflow/references/reporting.md

@@ -0,0 +1,28 @@
+# Reporting templates
+
+## Worker -> main
+- status: accepted | blocked | milestone | done | failed
+- summary: one-line result
+- evidence: commit / PR / log / session trace
+- risk: blocker or caveat
+- next: recommended next action
+
+## Main -> user
+- who
+- status
+- output
+- next
+
+## Examples
+
+### launch failure
+- who: qa_worker
+- status: blocked (launch failure)
+- output: dispatch accepted but no worker trace/session history appeared
+- next: re-dispatch or switch worker
+
+### milestone
+- who: promo_worker
+- status: in_progress
+- output: README links added and release draft created
+- next: review and merge remaining repo updates

skills/agent-workflow/references/state-machine.md

@@ -0,0 +1,25 @@
+# Minimal state machine
+
+## States
+- planned
+- dispatching
+- in_progress
+- blocked
+- reviewing
+- done
+
+## Typical flow
+1. `planned`
+2. `dispatching`
+3. `in_progress`
+4. `reviewing`
+5. `done`
+
+## Failure shortcuts
+- `dispatching` + no worker trace within 10 minutes -> `blocked (launch failure)`
+- `in_progress` + ETA exceeded with no milestone -> `blocked (stalled)`
+
+## Notes
+- Keep the state machine small.
+- Avoid adding extra states unless repeated real-world failures demand them.
+- State changes should be backed by evidence, not optimism.