A retrospective works when it is structured and still leaves room for honest feedback. The Retro Rulebook takes care of the preparation: it selects a suitable format (Start/Stop/Continue, 4Ls, Sailboat, Mad/Sad/Glad), builds a time-blocked agenda with a check-in and a check-out, formulates open guiding questions for each phase, and delivers a template for collecting and clustering input. The result is an action plan with a maximum of three points, each with an owner and a due date, so the retrospective actually leads somewhere.
\nIt is built for scrum masters, project leads and team leads who prepare sprint, project or quarterly retrospectives on a regular basis and do not want to start from zero every time. It deliberately varies the format when a team runs the same exercise repeatedly, and follows a fixed rule: no evaluation of individual people, no blame, questions stay forward-looking rather than accusatory.
\nWhat it does not do: the skill does not facilitate the retrospective itself, it prepares it. Actually running the conversation, picking up on tension in the room, and deciding when a topic needs more time remain the facilitator's job. The skill also cannot judge whether a proposed action actually addresses the right problem; that stays a matter of team judgment.
\n" }, { "id": "skill-text", "title": "Skill Text", "html": "Copy the prompt below in full into your AI tool. As a file: retro-regelwerk.en.json
\n" } ], "schritte": [ { "nr": 1, "titel": "Provide the retro context", "beschreibung": "Retro type, time period, team size and optionally known topics or a preferred format are provided.", "rolle": "mensch" }, { "nr": 2, "titel": "Select the format and build the agenda", "beschreibung": "A suitable retro format is selected, then a time-blocked agenda with phases is built.", "rolle": "automatisch" }, { "nr": 3, "titel": "Formulate guiding questions", "beschreibung": "Open, constructive questions are developed for each phase: check-in, collection, insights, actions.", "rolle": "automatisch" }, { "nr": 4, "titel": "Prepare templates and the action plan", "beschreibung": "A collection template, clustering instructions and an action template with owner and deadline are added.", "rolle": "automatisch" }, { "nr": 5, "titel": "Finished retro package", "beschreibung": "Agenda, guiding questions, templates and a check-out question are ready, 400 to 800 words in total.", "rolle": "ergebnis" } ], "herausgeber": "Voyage Digital", "version": "2.0", "stand": "2026-07-26", "umsetzung": [ { "titel": "Gather the context", "text": "Time period, team and known topics are gathered." }, { "titel": "Copy the skill", "text": "The skill is copied and the retro package is generated." }, { "titel": "Prepare the board", "text": "A digital or physical board is set up for the session." }, { "titel": "Run the retrospective", "text": "The agenda serves as the guide through the session." }, { "titel": "Track the actions", "text": "The agreed actions are reviewed in the next retrospective." } ], "zutaten": [ "Retro type", "Time period", "Team size", "Topics", "Format" ], "beispielSzenario": "Ahead of a sprint retrospective for a six-person team, the person responsible provides the skill with the sprint summary, known issues and the preferred format, here Start/Stop/Continue. This produces a 45-minute agenda with guiding questions for each phase and a template for capturing the results.", "eingaben": [ { "feld": "Retro type (sprint, project, quarter, team)", "pflicht": true }, { "feld": "Time period being reflected on", "pflicht": true }, { "feld": "Team size", "pflicht": true }, { "feld": "Known issues or successes", "pflicht": false }, { "feld": "Preferred format (Start/Stop/Continue, 4Ls, Sailboat, Mad/Sad/Glad)", "pflicht": false }, { "feld": "Results and open actions from the previous retrospective", "pflicht": false }, { "feld": "Duration of the retrospective", "pflicht": false }, { "feld": "Remote or in person", "pflicht": false } ], "ausgabe": "A time-blocked agenda with phases and method, three to five guiding questions per phase, a collection template for input, clustering instructions, and an action template with owner and deadline, 400 to 800 words in total.", "prompt": "# DESCRIPTION\nCreates a complete retrospective package with agenda, guiding questions, a collection template and concrete improvement actions.\n\n# INPUT\n- Retro type, e.g. sprint, project, quarter, team (required)\n- Time period being reflected on (required)\n- Team size (required)\n- Known issues or successes (optional)\n- Preferred format, e.g. Start/Stop/Continue, 4Ls, Sailboat, Mad/Sad/Glad (optional)\n- Results and open actions from the previous retrospective (optional)\n- Duration of the retrospective (optional)\n- Remote or in person (optional)\n\n# OUTPUT\n- Format: retrospective package\n- Structure:\n 1. Retro agenda: time blocks with phase, method, duration\n 2. Guiding questions: 3 to 5 questions per phase\n 3. Collection template: template for gathering input\n 4. Clustering instructions: how the inputs are grouped\n 5. Action template: concrete improvements with owner and deadline\n 6. Check-out question: closing the retrospective\n- Length: 400 to 800 words\n\n# CONTEXT\n- Global placeholders: COMPANY, INDUSTRY, TARGET AUDIENCE\n- Skill-specific: PM methodology, team values, way of working\n- Domain knowledge: agile retrospectives, facilitation, team dynamics, feedback methods\n- Constraint: no evaluation of individual people, no blame. If details on format, duration or history are missing, this is flagged as an assumption rather than filled in silently.\n\n# WORKING INSTRUCTIONS\n\n## Step 1: Select the retro format\nChoose a suitable format based on context and team maturity.\n### Rules: Start/Stop/Continue works well for standard retrospectives, 4Ls (Liked/Learned/Lacked/Longed for) for project retrospectives. Deliberately vary the format when a team runs the same retrospective for the fifth time.\n### No-gos: Do not always suggest the same format regardless of context.\n\n## Step 2: Build the agenda\nBuild a time-blocked timeline with phases: check-in, gather data, generate insights, define actions, check-out.\n### Rules: Psychological safety is actively established at the start, not assumed.\n### No-gos: Do not skip the actions phase, even when time runs short.\n\n## Step 3: Formulate guiding questions\nDevelop open, constructive questions for each phase.\n### Rules: Questions address both what went well and room for improvement, and are phrased in a forward-looking way (\"What should we do differently?\" instead of \"What went badly?\").\n### No-gos: No leading questions, no blame.\n\n## Step 4: Prepare the action template\nStructure concrete, actionable improvements.\n### Rules: A maximum of three actions per retrospective as a target, each with an owner and a deadline. Actions from the previous retrospective are reviewed as well, where available.\n### No-gos: Do not propose more than five actions; they will not get implemented anyway.\n\n# DEFINITION OF DONE\n[ ] Retro format chosen to fit context and team maturity\n[ ] Agenda with time blocks and phases is in place\n[ ] At least three guiding questions formulated per phase\n[ ] Collection template for input prepared\n[ ] Action template with owner and deadline available\n[ ] Check-in and check-out question defined\n[ ] Psychological safety addressed in the process\n[ ] Maximum of three actions kept as a target\n[ ] Missing details are clearly marked as an assumption, not filled in silently\n[ ] The user is addressed in a professional manner throughout\n\n# CONVERSATION START\nHello, let's prepare your retrospective. I need the following from you:\n1. What type of retro is this? (Sprint, project, quarter, team?)\n2. What time period is being reflected on?\n3. How big is the team?\n4. Optional: known topics, preferred format, duration, remote or in person", "einrichtung": { "intro": "Step-by-step guides for ChatGPT, Claude, Copilot Studio and Langdock.", "plattformen": [ { "plattform": "ChatGPT", "anbieter": "OpenAI", "schritte": [ "Copy the skill text above using the copy button.", "Click your profile picture and select \"Skills\".", "Click \"Create skill\" and paste the copied text as the instruction.", "Adjust inputs, outputs and format where your case requires it.", "Save the skill. It is available in all chats from that point on." ], "doku": { "label": { "de": "OpenAI Dokumentation: Skills in ChatGPT", "en": "OpenAI documentation: Skills in ChatGPT" }, "url": "https://help.openai.com/de-de/articles/20001066-skills-in-chatgpt" } }, { "plattform": "Claude", "anbieter": "Anthropic", "schritte": [ "Copy the skill text above using the copy button.", "Open claude.ai and go to \"Skills\" in your profile.", "Create a new skill and paste the copied text as the instruction.", "The skill works in claude.ai, in Claude Code and through the API.", "Available on the Pro, Max, Team and Enterprise plans." ], "doku": { "label": { "de": "Anthropic Dokumentation: Benutzerdefinierte Skills erstellen", "en": "Anthropic documentation: Creating custom skills" }, "url": "https://support.claude.com/de/articles/12512198-benutzerdefinierte-skills-erstellen" } }, { "plattform": "Copilot Studio", "anbieter": "Microsoft", "schritte": [ "Copy the skill text above using the copy button.", "Open Copilot Studio and create a new agent.", "Paste the copied text as the instruction.", "Connect knowledge sources and tools where needed.", "Publish the agent for yourself or for your organisation." ], "doku": { "label": { "de": "Microsoft Dokumentation: Einen Agent erstellen und bereitstellen", "en": "Microsoft documentation: Create and deploy an agent" }, "url": "https://learn.microsoft.com/de-de/microsoft-copilot-studio/fundamentals-get-started" } }, { "plattform": "Langdock", "anbieter": null, "schritte": [ "Copy the skill text above using the copy button.", "Open the sidebar and click \"Add skill\".", "Paste the copied text directly as the instruction.", "Connect the skill to integrations such as Gmail or Slack where needed.", "Save the skill and release it for yourself or your team." ], "doku": { "label": { "de": "Langdock Dokumentation: Skills", "en": "Langdock documentation: Skills" }, "url": "https://docs.langdock.com/de/product/chat/skills" } } ] }, "itemIcon": "rotate-ccw", "recommended": [ { "slug": "kickoff-briefing", "category": "skill", "name": "The Kickoff Briefing", "teaser": "The Kickoff Briefing turns your project data into a complete kickoff package with agenda, one pager, role matrix and invitation email in a single pass.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "flag" }, { "slug": "okr-stratege", "category": "assistent", "name": "The OKR Strategist", "teaser": "Translates a top-level strategic goal into a complete OKR set with a qualitative objective, measurable key results, concrete initiatives and an alignment check that flags dependencies and risks.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "target" }, { "slug": "workflow-planer", "category": "assistent", "name": "The Workflow Planner", "teaser": "Builds a complete plan from a workflow goal, time frame, and the available resources, with process steps, a resource matrix, risk analysis, and measurable milestones.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "workflow" }, { "slug": "linear", "category": "tool", "name": "Linear", "teaser": "Issue tracking and planning tool for software teams that organizes work into cycles, initiatives and roadmaps, automatically routes customer feedback into prioritized issues, and connects to coding tools through an MCP server and its own AI agents.", "domaene": "Betrieb & Projektmanagement", "logoFile": "linear.svg", "logoEinzug": 0.78 }, { "slug": "plane", "category": "tool", "name": "Plane", "teaser": "Plane is an open source project management tool with issues, cycles, modules and worklogs, available as either a free self-hosted Community Edition or a cloud service, positioning it as an affordable, data-sovereign alternative to Jira and Linear.", "domaene": "Betrieb & Projektmanagement", "logoFile": "plane.png", "logoEinzug": 0.78 }, { "slug": "aufgaben-raster", "category": "skill", "name": "The Task Grid", "teaser": "Reads meeting minutes, emails or other texts and extracts all open tasks, both explicit and implicit, with owners and deadlines.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "list-checks" }, { "slug": "pdf", "category": "skill", "name": "The PDF Workbench", "teaser": "The PDF Workbench bundles the full range of PDF work into one executable skill with real code execution, from merging and splitting to watermarking, encryption, form filling, and OCR on scanned pages.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "file-type-2" }, { "slug": "posteingang-regelwerk", "category": "skill", "name": "The Inbox Rulebook", "teaser": "Sorts a full inbox into a fixed rulebook of category, urgency and reply draft, so you keep the final decision while the system handles the triage.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "inbox" }, { "slug": "tagesabschluss-protokoll", "category": "skill", "name": "The Shutdown Protocol", "teaser": "The Shutdown Protocol actively walks you through every open task at the end of the workday and hands you exactly three pre-prepared priorities to start tomorrow with focus.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "moon" }, { "slug": "uebergabe-paket", "category": "skill", "name": "The Handover Package", "teaser": "Builds a complete handover document from meeting notes, quotes and CRM records for the transition from sales to the delivery team.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "package-check" }, { "slug": "onboarding-strecke", "category": "workflow", "name": "The Onboarding Pipeline", "teaser": "Automates customer onboarding from the CRM status change through to a ready-to-send welcome email, turning a classic small business bottleneck into one clean, repeatable workflow.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "door-open" }, { "slug": "posteingang-route", "category": "workflow", "name": "The Inbox Router", "teaser": "A workflow that automatically classifies incoming emails, applies the matching label, and immediately alerts you when something is urgent.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "inbox" }, { "slug": "status-bruecke", "category": "workflow", "name": "The Status Bridge", "teaser": "A workflow that pulls your project data every week and turns it into a ready status report covering progress, risks and delays, for you to review before it goes out.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "activity" }, { "slug": "team-digest-schleife", "category": "workflow", "name": "The Team Digest Loop", "teaser": "A daily workflow that gathers the important discussions from your team's Slack or Teams channels and turns them into a structured digest of decisions, action items, and updates.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "mails" }, { "slug": "buero-lotse", "category": "assistent", "name": "The Office Navigator", "teaser": "An assistant that guides you through three recurring office tasks, structured brainstorming, ready-to-use communication drafts, and concrete project planning, based on the context knowledge you provide.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "printer" }, { "slug": "projekt-sparringspartner", "category": "assistent", "name": "The Project Sparring Partner", "teaser": "Guides you through every phase of a project with systematic risk analysis, prioritized courses of action for acute problems, and structured lessons learned after completion.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "kanban-square" }, { "slug": "prozess-dokumentierer", "category": "assistent", "name": "The Process Documenter", "teaser": "Captures undocumented business processes through a structured interview and turns them into clear, visual process documentation with steps, decision points and responsibilities.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "route" }, { "slug": "risikomatrix-pruefer", "category": "assistent", "name": "The Risk Matrix Reviewer", "teaser": "Identifies, assesses and prioritizes project risks in a structured risk matrix with preventive and corrective measures.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "grid-3x3" }, { "slug": "statusbericht-kurator", "category": "assistent", "name": "The Status Report Curator", "teaser": "Condenses status meeting notes and the project plan into a structured project status report with a traffic light rating, a milestone and risk overview, and concrete next steps.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "clipboard-check" }, { "slug": "verhandlungs-stratege", "category": "assistent", "name": "The Negotiation Strategist", "teaser": "Analyzes a supplier quote along with its market context and develops a concrete, ready-to-use negotiation strategy with goals, levers, arguments and fallback positions.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "handshake" } ] }