-
Notifications
You must be signed in to change notification settings - Fork 0
readme: consolidate What's-new stack, name engineering-process skills, state delegate-selection order #88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,3 @@ | ||
| ### Changed | ||
|
|
||
| - README: named the engineering-process skills (`decision-map`, `prototype`, `architecture-review`) in the Skill surface enumeration, and stated the delegate-selection order (capability, then availability, then pool-conserving cost rank) in the cost-tiered delegation bullet. What's-new consolidation is deferred to the next release cut, when the changelog fragments are compiled into `CHANGELOG.md` — until then the README stack is the only reader-facing versioned history. |
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When users delegate through the shipped skills, no fixed capability→availability→cost selection currently occurs:
skill-specs/dev-delegate.mdrequires the primary to select one explicit route, whileskill-specs/route.mdstates that automatic worker routing is unavailable and that an unavailable explicit target stops without substitution. Thus this user-facing statement promises current behavior that neither the editable skill policy nor the coordinator provides; describe it as a future policy or add it to the authoritative skill workflow.AGENTS.md reference: AGENTS.md:L9-L12
Useful? React with 👍 / 👎.