$npx -y skills add omnigentx/jarvis --skill retrospectiveProtocol for writing sprint retrospective lessons learned
| 1 | # Retrospective Skill |
| 2 | |
| 3 | The sprint is complete. Write your retrospective lessons learned. |
| 4 | |
| 5 | ## Output |
| 6 | |
| 7 | Write your retrospective to: `retrospective/<your_agent_name>_lessons.md` |
| 8 | |
| 9 | ## Template |
| 10 | |
| 11 | ```markdown |
| 12 | # Retrospective — <Your Agent Name> |
| 13 | |
| 14 | ## What Went Well |
| 15 | - <Specific things that worked effectively> |
| 16 | - <Reference actual work done, files created, decisions made> |
| 17 | |
| 18 | ## What Could Be Improved |
| 19 | - <Specific challenges encountered> |
| 20 | - <Things that slowed you down or caused rework> |
| 21 | |
| 22 | ## Suggestions for the Team |
| 23 | - <Process improvements> |
| 24 | - <Communication improvements> |
| 25 | - <Tool or workflow suggestions> |
| 26 | |
| 27 | ## Key Learnings |
| 28 | - <Technical insights gained during this sprint> |
| 29 | - <Patterns to reuse in future sprints> |
| 30 | - <Anti-patterns to avoid> |
| 31 | |
| 32 | ## Action Items for Next Sprint |
| 33 | | # | Action | Owner | |
| 34 | |---|--------|-------| |
| 35 | | 1 | <specific improvement> | <agent name> | |
| 36 | ``` |
| 37 | |
| 38 | ## Guidelines |
| 39 | |
| 40 | - **Be specific** — reference actual files, decisions, and outcomes from the workspace |
| 41 | - **Be honest** — constructive criticism helps the team improve |
| 42 | - **Be actionable** — every "could be improved" should have a suggestion |
| 43 | - **Read others' work** — check workspace files to understand what the full team accomplished |
| 44 | - **Don't blame** — focus on processes, not people |