Loading...
Loading...
Found 179 Skills
Conduct a retrospective on a coding session.
Facilitate effective sprint retrospectives for continuous team improvement. Use when conducting team retrospectives, identifying improvements, or fostering team collaboration. Handles retrospective formats, action items, and facilitation techniques.
Build Android networking stacks with Retrofit, OkHttp, interceptors, API contracts, and resilient error handling.
Turn a finished, failed, or disappointing work cycle into portable lessons, anti-patterns, quality gates, and next-cycle vocabulary. Use after a build, QA pass, demo, user complaint, or abandoned attempt when the useful output is what the next pass must learn rather than the code itself.
Conduct a project or sprint retrospective by gathering data from status reports and velocity metrics, structuring what went well and what needs improvement, and generating actionable improvement items with owners and due dates. Use at the end of a sprint, after a project phase or milestone, following a significant incident or success, at a quarterly review of ongoing processes, or before starting a similar project to capture lessons learned.
Classify finished pipeline runs from the configured tracker — clean single pass, hard recovery, loop checkpoints, or cause not recorded — and rank what the second passes cost in wall-clock hours. Read-only; hands the top cause to om-prepare-issue. Use for "pipeline retro", "why is our pipeline slow", "what is costing us rework".
Facilitates and documents a team retrospective capturing what went well, what to improve, and action items. Use at the end of sprints, projects, or milestones to reflect and improve team practices.
Automated retrospectives — captures learnings at EPIC completion and on manual invocation. EPIC-scoped retros embed a Retrospective section in the EPIC artifact. Cross-epic and time-based retros produce standalone retro docs. Triggers on: 'retro', 'retrospective', 'post-mortem', 'lessons learned', 'debrief', 'what worked', 'what didn't work', 'what did we learn', 'reflect', or automatically after EPIC terminal transitions.
Final retrospective and self-assessment for participants of Claude Code Lab. Runs four sequential interactive parts — progress audit, best prompt, monthly plan, and feedback — using AskUserQuestion. Triggers on "/lab-retro", "lab retrospective", "claude code lab final", or after completing the 6-week Claude Code Lab cohort.
Post-epic review to extract lessons and assess success. Use when the user says "run a retrospective" or "lets retro the epic [epic]"
Learn from PR outcomes. Analyzes accept/reject patterns and updates contribution lessons. Triggers: "pr retro", "learn from PR", "PR outcome", "why was PR rejected", "analyze PR feedback".
Weekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas.