Customer Context

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

Install

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

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

From the SKILL.md

# /customer-context

Load and update a customer's context. Run this at the start of every customer session.

## Step 0: Parse customer name

The customer name is the first argument after the skill invocation. If no name is
provided, ask: "Which customer? (e.g. /customer-context acme)"

Set CUSTOMER_NAME from the argument. All file paths below use this name.
The ops repo root is the current working directory — all paths are relative to it.

## Step 1: Ops repo safety check

Run:
```bash
git remote -v 2>/dev/null | head -4
[ -d customers/ ] && ls customers/ | head -3 || echo "NO_CUSTOMERS_DIR"
```

If `NO_CUSTOMERS_DIR` appears AND there are git remotes that don't look like a
personal ops repo (e.g., remote URL contains a company/project name that matches
obvious customer patterns), print:

> Warning: I don't see a `customers/` directory here. Are you sure you're in your
> FDE ops repo (e.g. ~/fde-ops/) and not inside a customer's codebase? Committing
> customer context here could expose internal notes to the customer's team.
> Type "yes" to proceed anyway, or cd to your ops repo first.

Wait for confirmation before continuing if this warning fires.

## Step 2: Check session marker freshness
Read the full skill on GitHub

Details

Skill name
customer-context
Path
skills/customer-context/SKILL.md
License
MIT
Repo updated
19 May 2026

FAQ

What does the Customer Context skill do?

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

How do I install the Customer Context skill?

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

Is Customer Context popular?

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

Related skills

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

Integrate

49

Dan-Cleary/fdestack

Production-grade implementation. Reads scope.md + stack.md + decisions.md + value-frame.md. EXPLICITLY DOES NOT READ customers/<name>/poc/ — that directory is throwaway. POC discoveries reach /integrate via the learnings write-back that /poc performs into stack.md and decisions.md. Proactively invoke this skill after /poc has run AND its learnings write-back is complete when the FDE says "let's productionize", "time to integrate", "build the real thing", or "cleanroom rebuild". Refuse to run if no /poc exists yet — surface the gap rather than building blind. Usage: /integrate <customer-name> V

Marketing, Sales & Business

Reverse Engineering Business Logic

47

meirm/reverse-engineering-skill

Reverse engineers business logic from source code by extracting operational business truth. Use when user asks to understand what the system actually does, analyze business rules, extract domain logic, infer workflows from code, explain state transitions, or identify decision logic. Works with API views (Django, FastAPI, etc.), domain models, background tasks, and multi-step workflows.

Marketing, Sales & Business

Refine Business Logic for Implementation

47

meirm/reverse-engineering-skill

Rewrites vague business logic into deterministic, testable rules by separating policy from mechanism, normalizing terminology, and defining explicit state machines. Use when preparing BL for code implementation, making BL executable, or normalizing ambiguous requirements.

Marketing, Sales & Business

Derive Acceptance Criteria From Business Logic

47

meirm/reverse-engineering-skill

Converts trusted business logic into product-owner-grade acceptance criteria and developer-ready tasks using Given/When/Then scenarios. Use when creating user stories, preparing for sprints, or turning BL into executable requirements.

Marketing, Sales & Business

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