Check if requested changes are within current feature scope. Use when user requests new functionality or changes during implementation that might be scope creep. Compares requests against feature requirements and suggests adding out-of-scope items to backlog.
Checks if requested changes align with current feature scope by comparing against requirements. Use when user requests new functionality during implementation to prevent scope creep and suggest adding out-of-scope items to backlog.
/plugin marketplace add schuettc/claude-code-plugins/plugin install feature-workflow@schuettc-claude-code-pluginsThis skill is limited to using the following tools:
Prevent scope creep by checking if requested changes align with the current feature's requirements.
Invoke this skill when the user:
Do NOT invoke for:
Read: docs/planning/backlog.json
Find the in-progress feature. If none or multiple:
Read: docs/planning/features/[feature-id]/requirements.md
Extract:
Compare the user's request against the requirements:
In Scope if the request:
Potential Scope Creep if the request:
affectedAreasClearly Out of Scope if the request:
If clearly in scope: Proceed without comment. Don't slow down valid work.
If potential scope creep:
This seems outside the current feature scope.
**Current Feature**: [name]
**Original Scope**: [brief summary from requirements]
**Your Request**: [what they asked for]
Options:
1. **Include it** - Add to current feature (may increase effort)
2. **Add to backlog** - Track as separate item: `/feature-capture`
3. **Skip for now** - Focus on original scope first
What would you like to do?
If clearly out of scope:
This is outside the scope of [feature name].
Consider adding it as a separate backlog item:
`/feature-capture`
This keeps the current feature focused and trackable.
Be helpful, not obstructive:
If user decides to expand scope:
Got it. Consider updating the requirements:
docs/planning/features/[id]/requirements.md
This helps track what the feature actually delivers.
This skill works with:
feature-context skill - Uses same requirements.mdbacklog-awareness skill - For checking if idea is already tracked/feature-capture - For adding out-of-scope itemsMaster defensive Bash programming techniques for production-grade scripts. Use when writing robust shell scripts, CI/CD pipelines, or system utilities requiring fault tolerance and safety.