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 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
Install
npx skills add Dan-Cleary/fdestack --skill integrategit clone --depth 1 https://github.com/Dan-Cleary/fdestack.git /tmp/fdestack
mkdir -p ~/.claude/skills
cp -r /tmp/fdestack/skills/integrate ~/.claude/skills/integratePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# /integrate
Build the production version. Cleanroom rebuild from the customer context files — never from POC code.
## Step 0: Parse inputs
The customer name is the first argument. No optional flags — `/integrate` has one mode (production).
Set `CUSTOMER_NAME`.
## Step 1: Check session marker
```bash
MARKER="/tmp/fdestack-session-$CUSTOMER_NAME"
if [ ! -f "$MARKER" ]; then echo "MARKER_MISSING=true"; fi
MARKER_TS=$(grep '^ts=' "$MARKER" 2>/dev/null | cut -d= -f2)
AGE=$(( $(date +%s) - ${MARKER_TS:-0} ))
[ "$AGE" -lt 43200 ] && [ -n "$MARKER_TS" ] && echo "MARKER_OK=true" || echo "MARKER_STALE_OR_MISSING=true"
```
If missing or stale: "Run /customer-context $CUSTOMER_NAME first." Stop.
## Step 2: Verify prerequisites
```bash
SCOPE_COUNT=$(ls customers/$CUSTOMER_NAME/scope-*.md 2>/dev/null | wc -l | tr -d ' ')
POC_COUNT=$(ls -d customers/$CUSTOMER_NAME/poc 2>/dev/null | wc -l | tr -d ' ')
echo "SCOPE_COUNT=$SCOPE_COUNT POC_COUNT=$POC_COUNT"
```
- `SCOPE_COUNT=0` → REFUSE: "No /scope file. /integrate requires the scope's binary success criteria as its acceptance bar."
- `POC_COUNT=0` → WARN: "No POC found for $CUSTOMER_NAME. /integrate can run without one, but typically /poc proved feasibility first and wrote learnings back to stack.md and decisions.md. Confirm you want to proceed without that signal? (yes / let me run /poc first)"
## Step 3: Hard rule — DO NOT READ THE POC DIRECTORYDetails
- Skill name
integrate- Repository
- Dan-Cleary/fdestack
- Path
skills/integrate/SKILL.md- License
- MIT
- Repo updated
- 19 May 2026
FAQ
What does the Integrate skill do?
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
How do I install the Integrate skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add Dan-Cleary/fdestack --skill integrate. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Integrate popular?
It lives in Dan-Cleary/fdestack, which has 49 GitHub stars and 5 forks.
Related skills
Customer Context
49Dan-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
Discovery
49Dan-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
Engagement Retro
49Dan-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
Learnings
49Dan-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
Scope
49Dan-Cleary/fdestack
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
Triage
49Dan-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
Browse the most popular Claude skills, all marketing, sales & business skills, or write your own with the skills generator.