guarding-scope

Included with Lifetime

$97 forever

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.

General

What this skill does

# Scope Guard

Prevent scope creep by checking if requested changes align with the current feature's requirements.

## When to Use

Invoke this skill when the user:
- Requests new functionality while implementing a feature
- Asks to add something that seems tangential
- Proposes changes not in the original requirements
- Says "while we're at it, let's also..."

**Do NOT invoke for:**
- Bug fixes in feature code
- Refactoring within scope
- Clarifying existing requirements
- Implementation details of planned features

## Instructions

### Step 1: Identify Current Feature

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.

### Step 2: Load Requirements

Read `docs/features/[id]/idea.md`

Extract: problem statement, affected areas, proposed solution hints.

Also read `docs/features/[id]/plan.md` for:
- Implementation steps (what was planned)
- Technical decisions made

### Step 3: Analyze the Request

**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.

### Step 4: Respond

- **In scope**: Proceed without comment
- **Potential creep**: Flag it, offer options (include, add to backlog, skip)
- **Out of scope**: Suggest `/feature-capture`

Be helpful, not obstructive. Respect user's decision.

## Example

**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?
```

## Integration Notes

This skill works with:
- `checking-backlog` skill - For checking if idea is already tracked
- `/feature-capture` - For adding out-of-scope items

Files: 1

Size: 2.6 KB

Complexity: 12/100

Category: General

Source: https://github.com/schuettc/claude-code-plugins/tree/main/feature-workflow/skills/guarding-scope

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts