docs: split wspace skill into protocol and command reference - #23
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
1 participant
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.
What
Reworks the wspace agent skill per the Agent Skills spec (agentskills.io):
skills/wspace/SKILL.mdis now the behavioral protocol: launch hierarchy (pre-seated cwd -> handoff metadata -> root discovery), a 6-step deterministic pipeline, token/context economy rules, and guardrails. Stays under 500 lines; references the command file on demand.skills/wspace/references/COMMANDS.mdholds the tool reference: commands table, worktree creation rules, check status values, and common pitfalls.The skill is self-contained — downstream users install
wspaceonce and get both the protocol and on-demand command reference. No CLI code changes.Verification
deno task cigreen locally (fmt, lint, type-check, 55 tests)