feat(prep): add research directive for constrained third-party deps - #13
Draft
fatih-acar wants to merge 1 commit into
Draft
feat(prep): add research directive for constrained third-party deps#13fatih-acar wants to merge 1 commit into
fatih-acar wants to merge 1 commit into
Conversation
When a feature depends on a third-party library or tool that lacks a required capability, the plan phase's research must now evaluate the dependency's extension mechanism (plugin system, hooks, middleware) and an upstream contribution before designing a workaround, recording the decision in research.md. This steers the pipeline away from overly complex implementations whose only cause is a fillable dependency gap. Applies to speckit.opsmill.auto as well via its delegation to prep. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
Features that depend on a third-party library or tool with a missing capability tend to accumulate overly complex in-repo workarounds, when the dependency's own plugin system — or an upstream contribution — was the intended way to fill the gap. This PR makes the pipeline's research phase evaluate those extension routes before any workaround is designed.
Key Changes
/speckit.opsmill.prepPhase 2 (Plan) now carries a research directive: when a third-party dependency lacks a capability the feature needs, the agent MUST evaluate the dependency's built-in extension mechanism (plugins, hooks, middleware, custom providers) and, failing that, an upstream contribution, before designing around the gap.research.mdas an explicit decision — chosen approach, rationale, and rejected alternatives — so the critique phase and the spec/ask alignment check have something concrete to verify./speckit.opsmill.autoinherits the directive via its delegation to prep; no separate edit needed.[Unreleased]; version bump left for release time.Test Plan
/speckit.opsmill.prepon a feature that depends on a constrained third-party library and checking thatresearch.mdcontains the extension-vs-workaround decision.🤖 Generated with Claude Code