fdestack

Claude Code skill pack for forward-deployed engineers — customer context, discovery, scope, value framing, POC, integration. Git-backed, no service deps.

Works with

Claude

View on GitHub

46 GitHub stars (46)

Steady at 46 stars — no new stars in the 16 days since Sep 30.

9 skills (9 skills found in its SKILL.md files)
4 forks (4 forks)
4mo ago last update (Last updated 4mo ago)

Install

Skills CLI

npx skills add Dan-Cleary/fdestack

Asks which skills and agents to install. Just one: npx skills add Dan-Cleary/fdestack --skill customer-context — add -g for every project.

Claude Code

git clone https://github.com/Dan-Cleary/fdestackcp -r "fdestack/skills/customer-context" ~/.claude/skills/

Copies the customer-context skill into ~/.claude/skills/ for every project (use .claude/skills/ for one project). Repeat for the other skills listed below.

Plugin

/plugin marketplace add Dan-Cleary/fdestack

Run inside Claude Code if the repository ships a plugin marketplace, then pick plugins from /plugin.

Skills can run code on your machine — read the SKILL.md first.

What it does

Filter skills

In the author's own words, from each skill's SKILL.md.

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 fir…
skills/customer-context/SKILL.md on GitHub (opens in a new tab)
discovery

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 summa…
skills/discovery/SKILL.md on GitHub (opens in a new tab)
engagement-retro

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)…
skills/engagement-retro/SKILL.md on GitHub (opens in a new tab)
integrate

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 p…
skills/integrate/SKILL.md on GitHub (opens in a new tab)
learnings

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 s…
skills/learnings/SKILL.md on GitHub (opens in a new tab)
poc

Build a throwaway proof-of-concept. Speed over quality. Hardcoded values OK, ugly code OK, no error handling beyond crash prevention. This code is NEVER going to production — /integrate will rebuild fresh. The skill's most important step is the learnings write-back at the end, which routes discoveries to stack.md / decisions.md / learnings.jsonl so /integrate can use them without ever reading POC…
skills/poc/SKILL.md on GitHub (opens in a new tab)
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 b…
skills/scope/SKILL.md on GitHub (opens in a new tab)
triage

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…
skills/triage/SKILL.md on GitHub (opens in a new tab)
value-frame

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 abou…
skills/value-frame/SKILL.md on GitHub (opens in a new tab)

Review before you install

A skill is a set of instructions and scripts your agent will follow, and it can run code on your machine. Read the SKILL.md and any scripts first — this listing is not a security review.

Encoders & Decoders

Hash Generators

Code Formatters

HTML Tools

JavaScript Tools

Network Tools

Database Tools

Development Tools

Miscellaneous Tools

fdestack