suboss87/FDEOps / skills/scope
scope
VerifiedAssess a new customer request against agreed scope, trade-offs and ownership. Use when an engagement expands or a custom feature needs a commitment decision.
| File | Kind | Size |
|---|---|---|
| .fde-generated.json | config | 457 B |
| SKILL.md | skill md | 1.3 KB |
| agents/openai.yaml | config | 185 B |
| references/hold-scope.md | markdown | 6.8 KB |
| references/task-context.md | markdown | 6.6 KB |
SKILL.md
View on GitHub---
name: scope
description: Assess a new customer request against agreed scope, trade-offs and ownership. Use when an engagement expands or a custom feature needs a commitment decision.
---
# scope
<!-- Generated by bin/generate-skills.js; edit the canonical references and catalog. -->
## Purpose
A scope decision with trade-offs and ownership.
Before investigating or acting:
1. Read [the task context contract](references/task-context.md).
2. Read [the method](references/hold-scope.md).
Load further references only when the task needs them. Everything linked is included in this skill; no other skill pack is required.
## Principles
- Work directly from the supplied permitted context. Standalone work does not require an engagement folder or initialization. Record filenames in the method are optional persistence destinations when no engagement is bound.
- If called by @fde, reuse its current sanitized packet and scope. Do not restart setup, discovery or questions already answered.
- The task context contract controls persistence and authority in both modes. Preserve unknowns and distinguish implementation, verification, deployment and acceptance.
- Use the customer's repository instructions and available tools. Report a missing capability or unrun check honestly; do not claim that installing a skill provisions infrastructure.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |