From feature-workflow
Checks if user requests align with current feature scope by reading docs/features files. Flags scope creep during implementation and suggests backlog or /feature-capture for out-of-scope items.
npx claudepluginhub schuettc/claude-code-plugins --plugin feature-workflowThis skill is limited to using the following tools:
Prevent scope creep by checking if requested changes align with the current feature's requirements.
Prevents feature creep with checklists for validating user needs, measuring impact, assessing complexity, defining MVPs, and managing scope in software projects.
Interactively adds features, ideas, or requirements to project backlog by prompting for details, creating docs/features/[id]/idea.md with YAML frontmatter, validating duplicates from DASHBOARD.md, and optionally staging git changes.
Evaluates feature necessity via worthiness scoring, backlog checks, and branch size limits before implementation to prevent overengineering. Useful in brainstorm-plan-execute workflows.
Share bugs, ideas, or general feedback.
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/features/DASHBOARD.md and look at the In Progress section to find the active feature.
If none or unclear, skip scope check - don't block the user.
Read docs/features/[id]/idea.md
Extract: problem statement, affected areas, proposed solution hints.
Also read docs/features/[id]/plan.md for:
In Scope - Implements the problem statement, reasonable extension of the feature, bug fix, or implementation detail.
Potential Scope Creep - New functionality not related to problem statement, affects other areas beyond what's listed, would require updating the plan significantly.
Clearly Out of Scope - Unrelated to problem statement, better as its own feature.
/feature-captureBe helpful, not obstructive. Respect user's decision.
User: "While we're adding dark mode, let's also add notification preferences"
Response:
This seems outside the current feature scope.
**Current Feature**: Dark Mode Toggle
**Original Scope**: Theme switching with light/dark modes
**Your Request**: Notification preferences
Options:
1. **Include it** - Add to current feature (increases scope)
2. **Add to backlog** - Track separately: `/feature-capture`
3. **Skip for now** - Focus on dark mode first
What would you like to do?
This skill works with:
checking-backlog skill - For checking if idea is already tracked/feature-capture - For adding out-of-scope items