القائمة
Scores feature worthiness and enforces branch-size limits against overengineering. Use when evaluating whether a feature belongs in the current scope or branch.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Detects AI-generated writing patterns in prose. Use when reviewing docs for slop, vague language, or identity leaks before publishing.
Audits Rust code for unsafe blocks, ownership issues, and Cargo dependency risks. Use when reviewing Rust code or before merging Rust changes.
Recommends context compression strategies for bloated or quota-heavy sessions. Use when context feels sluggish or quota burns faster than expected.
Guide minimal code via a decision ladder with full safety, edge, and negative-case coverage. Use when adding code, choosing a dependency, or auditing a diff.
Optimizes context window via MECW principles and memory tiering. Use when context exceeds 30% or before long multi-step tasks.
Generates or remediates documentation with human-quality writing. Use when creating new docs, rewriting AI-generated content, or applying style profiles.
| name | scope-guard |
| description | Scores feature worthiness and enforces branch-size limits against overengineering. Use when evaluating whether a feature belongs in the current scope or branch. |
| alwaysApply | false |
| category | workflow-methodology |
| tags | ["anti-overengineering","scope","YAGNI","prioritization","backlog"] |
| dependencies | [] |
| tools | [] |
| usage_patterns | ["feature-evaluation","scope-validation","threshold-monitoring","backlog-management"] |
| complexity | intermediate |
| model_hint | standard |
| estimated_tokens | 2500 |
| modules | ["modules/decision-framework.md","modules/github-integration.md","modules/anti-overengineering.md","modules/branch-management.md","modules/baseline-scenarios.md"] |
| role | library |
The cheapest feature is the one you never build. Scope-guard weighs each proposed feature against its value, its cost, and the branch budget, so only what is earned ships.
scope-guard:worthiness-scored)scope-guard:backlog-compared)scope-guard:budget-checked)scope-guard:decision-documented)Prevents overengineering by both Claude and human during the brainstorm, plan, and execute workflow. Forces explicit evaluation of every proposed feature against business value, opportunity cost, and branch constraints.
Core Belief: Not all features deserve implementation. Most ideas should be deferred to backlog until proven necessary.
Three Pillars:
Use the Worthiness formula:
(Business Value + Time Criticality + Risk Reduction) / (Complexity + Token Cost + Scope Drift)
Verification: Run the command with --help flag to verify availability.
See decision-framework.md for details.
Thresholds:
Compare against docs/backlog/queue.md:
Default: 3 major features per branch
If at capacity, must drop existing feature, split to new branch, or justify override.
Watch for Yellow/Red zones:
See branch-management.md for monitoring.
scope-guard:worthiness-scored)Score each factor (1, 2, 3, 5, 8, 13):
Details: decision-framework.md
scope-guard:backlog-compared)docs/backlog/queue.md for existing itemsscope-guard:budget-checked)Count current features in branch. If at budget (default: 3), new feature requires:
scope-guard:decision-documented)Record outcome:
scope-guard:github-issue-created completedocs/backlog/queue.md with issue linkIMPORTANT: Deferral is NOT complete until a GitHub issue exists. This prevents context loss when branches are merged or abandoned.
Key Principles:
See anti-overengineering.md for full rules and red flags.
**Verification:** Run the command with `--help` flag to verify availability.
docs/backlog/
├── queue.md # Active ranked queue
└── archive/
├── ideas.md # Deferred feature ideas
├── optimizations.md # Deferred performance work
├── refactors.md # Deferred cleanup
└── abstractions.md # Deferred patterns
Verification: Run the command with --help flag to verify availability.
When deferring, add to docs/backlog/queue.md:
| Rank | Item | Worthiness | Added | Branch/Epic | Category |
|------|------|------------|-------|-------------|----------|
| 1 | [New item description] | 1.8 | 2025-12-08 | current-branch | idea |
Verification: Run the command with --help flag to verify availability.
Re-rank by Worthiness Score after adding.
At end of brainstorming, before documenting design:
Self-invoke prompt: "Before documenting this design, let me evaluate the proposed features with scope-guard."
Before finalizing implementation plan:
Self-invoke prompt: "Before finalizing this plan, let me verify scope with scope-guard."
Periodically during execution:
Self-invoke prompt: "This branch has grown significantly. Let me check scope-guard thresholds."
When evaluating a feature, create these todos:
scope-guard:worthiness-scoredscope-guard:backlog-comparedscope-guard:budget-checkedscope-guard:github-issue-created (MANDATORY if deferring - blocks step 5)scope-guard:decision-documentedNote: Step 4 (github-issue-created) is REQUIRED when deferring items. You cannot mark decision-documented complete without first completing github-issue-created for deferrals.
superpowers:brainstorming - Ideation workflow this guardssuperpowers:writing-plans - Planning workflow this validatesimbue:review-core - Review methodology patternimbue:karpathy-principles - Compact four-principle synthesis covering scope, simplicity, surgical edits, and verifiable goalsdocs/quality-gates.md#skill-level-quality-gate-composition for the full gate-skill federation graph