Repository navigation
docs: add planner and worker coordination skills - #2206
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add concise planner and worker skills with one shared coordination protocol. The planner guides changes to the worker’s plan with refutable reasoning; the worker progresses autonomously. Routine heartbeats receive a short ACK, while questions, notable developments, and required gates trigger substantive review.
The protocol covers separate plan ownership, timestamped step/message links, configurable 2–3 minute heartbeats, evidence scope, and unavailable execution. It preserves existing plan/review requirements. Total documentation is about 1,023 words across three files.
Validation: both skill validators, relative links, and whitespace checks pass. Earlier drafts received 12 independent simulated scenarios plus five targeted plan/heartbeat scenarios. The final shortened text was checked against those behavioral requirements; no live deployment validation is claimed.
Only these three new Markdown files are included; unrelated checkout changes remain untouched.