engagement-retro - Weekly retro for a single customer engagement
Produces a weekly retro for a customer engagement by analyzing commit history, recent artifacts, and current blockers.
Tags
Updated: 2026-09-18Capabilities
Typical Inputs
Typical Outputs
What this skill does
- Collect activity history and commits
- Read engagement context and state
- Prompt FDE with retrospective questions
- Generate markdown retro report
- Save cross-customer learnings to file
- Update unknowns file with new items
- Commit retro files to git
Inputs
- Customer name
- Optional start date parameter
- Session marker file
- Customer state markdown files
- Git commit history
- FDE retrospective responses
Outputs
- Structured retro markdown file
- Updated unknowns markdown file
- Cross-customer learnings in JSONL file
- Git commit of retro changes
- Console summary output
Requirements
- Active session marker created by customer-context
- Git repository and user configuration
- Shell environment with standard unix utilities