Generate role-specific retro interview answers and write them to markdown files.
npx skills add https://github.com/cosmicdreams/claude-plugins --skill interviews
Please help me install this Agent Skill. Skill: interviews Source: https://github.com/cosmicdreams/claude-plugins/tree/main/retro/skills/interviews Command: npx skills add https://github.com/cosmicdreams/claude-plugins --skill interviews
It standardizes how each sprint agent documents their retro interview right before shutdown, ensuring the team-lead has consistent, complete coverage to generate session reports.
analysis-reports/retro-session/<YYYY-MM-DD>+<sprint-name>/interviews/.When you receive the message “Shutdown imminent,” use the role-specific 6-question interview prompts to write your interview to analysis-reports/retro-session/<YYYY-MM-DD>+<sprint-name>/interviews/<your-role>.md and then reply “Ready to shut down.”
High-intent search queries and answers about installing and using this skill.
To standardize sprint retro interviews, use a role-specific six-question prompt set that generates three common answers and three role-tailored answers, ensuring complete lessons-learned documentation before agent shutdown.
The required file path for markdown retro interview reports is `analysis-reports/retro-session/<YYYY-MM-DD>+<sprint-name>/interviews/<your-role>.md`, ensuring deterministic output placement for later coverage verification.
An agent confirms handoff readiness by replying "Ready to shut down" to the team-lead after successfully writing the markdown interview file, which closes the readiness confirmation loop and allows the shutdown to proceed.
Trigger agent self-documentation for a kanban retrospective when receiving a "Shutdown imminent" message, when manually triggering the process, or when verifying that retro interview coverage exists after a sprint concludes.
Role-specific retro interviews use three common questions plus three tailored questions based on the agent's role, such as implementer, reviewer, qa-validator, process-engineer, or team-lead, ensuring relevant documentation.
If retro interview coverage is missing after a sprint, you can manually trigger self-documentation to verify coverage exists, ensuring the team-lead has the consistent markdown reports needed to generate complete session reports.
TeoSlayerDeploy a four-agent brand protection system with scanner, classifier, enforcer, and dashboard roles.
Emz1998Generate sprint reports with goals, completed work, blockers, and velocity.
midsphere-aiCoordinate multiple agents into unified workflows with SwarmNode and RalphNode.
bang9Document whip runs as structured Markdown case studies under .whip/lesson-learn/.