Promote implement-plan-evolution to implement-plan, fix versioning#10
Merged
Conversation
- implement-plan-evolution becomes the new implement-plan (orchestrator model with TDD + bugmagnet + test-desiderata delegation) - Remove old implement-plan skill and its workspace (7 evals, 3 iterations) - Keep evolution evals as the new implement-plan-workspace (5 evals, 2 iterations) - Remove duplicate version fields from marketplace.json (plugin.json is the single source of truth per official docs) - Bump stepwise-core to v1.4.0
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.
Summary
versionfields frommarketplace.json. Per official docs,plugin.jsonis the single source of truth; setting version in both places causes silent conflictsTest plan
make testpasses (49/49)implement-plan-evolutionoutside historical transcripts/stepwise-core:implement-planworks