Conduct retrospectives on product or experiment loops and update state files.
npx skills add https://github.com/october-academy/agnt --skill retro-october-academy
Please help me install this Agent Skill. Skill: retro Source: https://github.com/october-academy/agnt/tree/main/skills/retro Command: npx skills add https://github.com/october-academy/agnt --skill retro-october-academy
Helps teams and solo builders perform structured retrospectives on an experiment or product loop by collecting context, prompting targeted reflection, and producing an actionable next-actions summary without manual state bookkeeping.
Start a retrospective loop by invoking the retro workflow, answer the guided questions, and confirm the Next Actions to update state and journey-brief.
High-intent search queries and answers about installing and using this skill.
A structured retrospective for an experiment loop is conducted by reading state.json and journey-brief.md, prompting targeted reflection questions, and summarizing verdicts into actionable next steps. The process handles CONTINUE, PIVOT, and KILL branching while automatically updating your state files.
You can update state.json and journey-brief.md after a product loop by running an automated retrospective workflow that applies default schema rules, increments loops_completed, and records chosen next actions. If a KILL verdict is selected, it performs an artifact reset to clean the directory.
If the MCP submit_practice tool is unavailable, the retrospective workflow queues a pending sync event locally instead of failing. This ensures your learnings are captured and can be submitted to MCP automatically once the tool becomes accessible again.
Handling CONTINUE, PIVOT, or KILL verdicts in agile state management is best done through guided reflection that branches execution logic based on the chosen verdict. The workflow records the decision, updates Next Actions, and triggers a KILL-to-A artifact reset when a KILL scenario is selected.
Artifacts need to be reset in a product retrospective workflow when a KILL verdict is chosen during the guided reflection. This KILL-to-A artifact reset cleans the state configuration, allowing you to start a fresh experiment loop without leftover configuration conflicts.
No, the retro workflow does not require manual state bookkeeping for journey-brief updates. It automatically reads existing context, enforces default schema rules, increments loops_completed, and writes the updated Next Actions directly to state.json and journey-brief.md.
october-academyGenerate a unified design system document with color, typography, and component rules.
october-academySynchronize local Agentic30 state and pending events via MCP.
october-academyPlan and execute a 7-day launch strategy across channels and milestones.
rezosndGenerate styled Excel workbooks with formulas, charts, and data validation.
