Scope

Force the wedge question: smallest thing buildable this week that proves the core value. Require binary success criteria. Push vague answers to unknowns.md as HIGH so they surface in every future Session Brief. Proactively invoke this skill after /discovery when the FDE describes a problem they want to solve for the customer, references the wedge or first thing to build, or asks "what should we build first" / "what's the smallest thing". Always run before /poc or /value-frame. Usage: /scope <customer-name> <problem statement> Voice triggers: "scope this out", "what's the wedge", "smallest thin

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add Dan-Cleary/fdestack --skill scope
Manual install
git clone --depth 1 https://github.com/Dan-Cleary/fdestack.git /tmp/fdestack
mkdir -p ~/.claude/skills
cp -r /tmp/fdestack/skills/scope ~/.claude/skills/scope

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# /scope

Force a tight, binary-criteria scope for a customer problem.

## Step 0: Parse inputs

The customer name is the first argument. Everything after it is the problem statement.

If no customer name is provided: ask "Which customer? (e.g. /scope acme <problem statement>)"
If no problem statement is provided: ask "What problem are we scoping? Paste a one-line summary or grab it from the latest discovery file."

Set `CUSTOMER_NAME` from the first argument.

## Step 1: Check session marker

```bash
MARKER="/tmp/fdestack-session-$CUSTOMER_NAME"
if [ -f "$MARKER" ]; then
  MARKER_TS=$(grep '^ts=' "$MARKER" | cut -d= -f2)
  NOW=$(date +%s)
  AGE=$(( NOW - MARKER_TS ))
  if [ "$AGE" -lt 43200 ]; then
    echo "MARKER_OK=true"
  else
    echo "MARKER_STALE=true AGE_H=$(( AGE / 3600 ))"
  fi
else
  echo "MARKER_MISSING=true"
fi
```

If `MARKER_MISSING=true` or `MARKER_STALE=true`:
> Run `/customer-context $CUSTOMER_NAME` first, then retry /scope.
> (Context must be loaded this session to ensure you're working with current information.)

Stop. Do not proceed.

## Step 2: Verify discovery has run

```bash
DISCOVERY_COUNT=$(ls customers/$CUSTOMER_NAME/discovery-*.md 2>/dev/null | wc -l | tr -d ' ')
echo "DISCOVERY_COUNT=$DISCOVERY_COUNT"
```

If `DISCOVERY_COUNT=0`:
> No discovery file found for $CUSTOMER_NAME. /scope needs a discovery first
> so we know what the customer actually said. Run /discovery $CUSTOMER_NAME <transcript>
> or paste call notes, then retry /scope.
Read the full skill on GitHub

Details

Skill name
scope
Path
skills/scope/SKILL.md
License
MIT
Repo updated
19 May 2026

FAQ

What does the Scope skill do?

Force the wedge question: smallest thing buildable this week that proves the core value. Require binary success criteria. Push vague answers to unknowns.md as HIGH so they surface in every future Session Brief. Proactively invoke this skill after /discovery when the FDE describes a problem they want to solve for the customer, references the wedge or first thing to build, or asks "what should we build first" / "what's the smallest thing". Always run before /poc or /value-frame. Usage: /scope <customer-name> <problem statement> Voice triggers: "scope this out", "what's the wedge", "smallest thin

How do I install the Scope skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add Dan-Cleary/fdestack --skill scope. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Scope popular?

It lives in Dan-Cleary/fdestack, which has 49 GitHub stars and 5 forks.

Related skills

Customer Context

49

Dan-Cleary/fdestack

Load a customer's context at the start of every session. Run this before any other FDEstack skill. Reads all 7 context files, surfaces drift since last session, asks what's new, and commits updates. Proactively invoke this skill (do NOT answer customer-specific questions directly) when the user references a customer name in an FDE ops repo without context being loaded this session. Always the first skill in a customer session — every other FDEstack skill requires its session marker. Usage: /customer-context <customer-name> Voice triggers: "load <customer>", "start session with <customer>", "wh

Marketing, Sales & Business

Discovery

49

Dan-Cleary/fdestack

Process any inbound source of customer context — meeting transcript, prior FDE's handoff notes, AE/sales briefing, customer-side RFP response, prior Discovery Workshop output, or your own raw notes. Extracts new stack info, stakeholders, stated problem, real problem, open questions, and context conflicts. Updates customer context files and commits. Proactively invoke this skill (do NOT just summarize) when the user pastes call notes, meeting transcripts, AE briefings, RFP responses, handoff docs, or any inbound document about a customer. Triggers on phrases like "I just had a meeting", "here a

Marketing, Sales & Business

Engagement Retro

49

Dan-Cleary/fdestack

Weekly retrospective for a single customer engagement. Reads commit history, recent discovery/scope/value-frame/poc/integrate files, and current blockers/unknowns. Produces a structured retro: what shipped, what's stuck, what we learned, what's next. Optional cross-customer learnings write-back for patterns worth remembering. Distinct from gstack's /retro (which is engineering-retro per-codebase). Proactively invoke this skill on Fridays or end-of-week, or when the FDE asks "where did the week go", "weekly retro", "what shipped this week", or seems to be wrapping up an engagement phase. Always

Marketing, Sales & Business

Triage

49

Dan-Cleary/fdestack

Cross-customer dashboard. Scan every customers/<name>/ directory, surface the highest-urgency blockers and unresolved unknowns across the FDE's portfolio. Optional filter to one cohort. No session marker required — this skill is the "where do I look first today?" view. Proactively invoke this skill at the start of a session in an FDE ops repo when no specific customer has been named, OR when the FDE asks "where should I look first", "what's most urgent", "what's on my plate today", or any variant of "what should I be working on?". Usage: /triage [active|blocked|all] Voice triggers: "what's urg

Marketing, Sales & Business

Learnings

49

Dan-Cleary/fdestack

Manage ~/.fdestack/learnings.jsonl — the cross-customer pattern library. List, search, prune stale entries, edit incorrect insights, or export the file for sharing with another FDE. No write to customer files; this is meta over the learnings file itself. Proactively invoke this skill when the FDE asks "what have we learned", "what patterns have we seen", "didn't we hit this before", or wants to share/export accumulated insights. Distinct from /customer-context Step 3, which only surfaces the top 3 most recent — /learnings is the full management UI. Usage: /learnings [list | search <kw> | prune

Marketing, Sales & Business

Value Frame

49

Dan-Cleary/fdestack

Translate a scoped process inefficiency into a defensible dollar value with stated assumptions and sensitivity. Forces lever taxonomy, explicit unit economics, and a defensibility check. Vague items get pushed to unknowns.md HIGH so they surface in every future Session Brief until resolved. Proactively invoke this skill after /scope when the FDE asks "is this worth doing", mentions ROI, asks about business case, needs to prepare for an executive conversation about value, or wants to put a dollar number on the work. Especially relevant before executive readouts or renewal calls. Usage: /value-f

Marketing, Sales & Business

Browse the most popular Claude skills, all marketing, sales & business skills, or write your own with the skills generator.