refactor: split skill-standard into workflow and strategy standards#11
Open
ZHOUKAILIAN wants to merge 1 commit into
Open
refactor: split skill-standard into workflow and strategy standards#11ZHOUKAILIAN wants to merge 1 commit into
ZHOUKAILIAN wants to merge 1 commit into
Conversation
Affected: skill-standard/SKILL.md, workflow-skill-standard/SKILL.md, strategy-skill-standard/SKILL.md
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.
Why
The original
skill-standardacted like a universal rubric, but execution-oriented skills and reasoning-oriented skills have different contracts, failure modes, and completion signals. Using one standard for both creates distortion.What changed
skill-standardas a meta-routing standardworkflow-skill-standardstrategy-skill-standardIntent
Files
skill-standard/SKILL.mdworkflow-skill-standard/SKILL.mdstrategy-skill-standard/SKILL.mdNotes
This PR is about framework clarity, not runtime behavior changes.