Run a five-question retrospective conversation and save it to retros/<feature-name>.md.
npx skills add https://github.com/CasaPerks/casaflow --skill retro-casaperks
Please help me install this Agent Skill. Skill: retro Source: https://github.com/CasaPerks/casaflow/tree/main/team/skills/retro Command: npx skills add https://github.com/CasaPerks/casaflow --skill retro-casaperks
The retro skill captures hard-won lessons after a feature ships so teams improve their spec-writing, codebase understanding, and AI-assisted development practices instead of losing insights after merge.
Run the command /casaflow:retro "feature-name" to generate a five-question retrospective and save it to retros/feature-name.md.
High-intent search queries and answers about installing and using this skill.
Run a retrospective conversation after merging work to capture structured knowledge. The skill guides you through five questions about spec changes and codebase discoveries, saving the captured learning as a durable markdown artifact under retros/feature-name.md.
A feature shipping retrospective captures hard-won lessons after merge to improve spec-writing and AI-assisted development. You need one after finishing and merging a feature to prevent losing valuable team insights and codebase discoveries.
Document flag rollout behavior by triggering the flag-aware follow-up section during your retrospective. When the referenced spec indicates a flag decision, the skill adds targeted questions about rollout behavior, sunset accuracy, and whether to retire the flag.
Yes, you can scan retrospectives for recurring themes because the skill persists output under retros/feature-name.md and performs cross-retro pattern scanning. This identifies recurring themes across multiple stored artifacts to build durable team knowledge.
The retrospective references a spec to add targeted flag rollout questions when the spec is flag-decision enabled. You run it after finish/merge workflows, making a completed or merged spec the typical prerequisite for accurate knowledge capture.
The best way to turn shipped work into durable artifacts is a staged Q&A retrospective requiring real answers. It captures surprises and concrete rules for next time, persisting the structured output as a markdown file under the retros directory.
royhenengelGenerate a handoff document capturing task progress and remaining work.
tarunccetConverts team feedback and sprint metrics into a markdown retro with prioritized action items.
adiytharpansaSynthesizes fragmented conversations, memories, and learning records into connected insights and patterns.
tygwanAutomate collection of learnings, ADRs, and retrospective insights via /feedback commands.
