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). 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
Install
npx skills add Dan-Cleary/fdestack --skill engagement-retrogit clone --depth 1 https://github.com/Dan-Cleary/fdestack.git /tmp/fdestack
mkdir -p ~/.claude/skills
cp -r /tmp/fdestack/skills/engagement-retro ~/.claude/skills/engagement-retroPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# /engagement-retro
Weekly per-customer retrospective. Honest snapshot of what happened, what's stuck, what we learned.
## Step 0: Parse inputs
The customer name is the first argument.
Optional flag: `--since <YYYY-MM-DD>`. Default: 7 days ago (`$(date -v-7d +%Y-%m-%d)` on macOS / `$(date -d '7 days ago' +%Y-%m-%d)` on Linux).
Set `CUSTOMER_NAME` and `SINCE_DATE`.
## Step 1: Check session marker
Same gate as /scope / /discovery / /poc / /integrate / /value-frame:
```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/stale: "Run /customer-context $CUSTOMER_NAME first." Stop.
## Step 2: Collect activity since SINCE_DATEDetails
- Skill name
engagement-retro- Repository
- Dan-Cleary/fdestack
- Path
skills/engagement-retro/SKILL.md- License
- MIT
- Repo updated
- 19 May 2026
FAQ
What does the Engagement Retro skill do?
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
How do I install the Engagement Retro skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add Dan-Cleary/fdestack --skill engagement-retro. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Engagement Retro 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
Integrate
49Dan-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
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
Reverse Engineering Business Logic
47meirm/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.
Browse the most popular Claude skills, all marketing, sales & business skills, or write your own with the skills generator.