Teach workflow skills in specialist playbooks #144
Reference in New Issue
Block a user
Delete Branch "codex/wizard-skill-playbooks"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Why
The specialist automation still assumed stale repo boundaries and generic habits. This makes the automation itself a coaching surface for better wizard behavior.
Blocking review: this edits paused cron definitions and adds skill names in cron/jobs.json that are not established source-of-truth here. Given the current automation cleanup, we should not mutate dormant cron state with unverified workflow knobs. Rebase after the automation surface is stabilized and keep the playbook-only changes separate from cron rewiring.
Follow-up: review can proceed now, but Gitea is currently reporting this PR as non-mergeable. The file scope is still narrow and review-worthy:
cron/jobs.jsonplus the specialist playbooks. Review focus should be whether the automation now teaches verification, escalation, and boundary awareness instead of generic backlog churn.b25aa6bdf4to9ae39362b3Rebased onto current
main, resolved the drift against the new local-inference/runtime changes, and re-pushed. This PR is mergeable again.Addressed in
d1f252b. I dropped thecron/jobs.jsonrewiring from this PR so it is back to playbook-only scope. The dormant cron state is no longer part of this review.