tability-qbr-pack-builder

Imported from tabilityio/tability-skills (tability-qbr-pack-builder/SKILL.md). Install upstream with npx skills add tabilityio/tability-skills --skill tability-qbr-pack-builder. Copyright stays with the author.

Tability QBR Pack Builder

Create an evidence-led QBR storyline without flattening unlike outcome metrics.

Workflow

1. Confirm the workspace, quarter, audience, presentation length, and plan scope. Use tability_get_workspace for timezone and retain source date and number conventions.
2. Resolve the quarter plan with tability_search_plans, then read tability_get_plan_content. If comparison with a prior quarter is requested, resolve it separately.
3. Read objectives and outcomes with tability_list_objectives_for_plan and tability_list_outcomes_for_plan when the plan snapshot lacks required detail.
4. For each material outcome, inspect check-in history across the quarter. Read comments on the latest check-in and any check-in used to support a turning point.
5. Read relevant initiatives with tability_list_initiatives_for_plan or tability_search_initiatives. Inspect the latest initiative comment and replies for delivered work, blockers, and decisions.
6. Build an evidence matrix containing baseline, latest value, target, confidence, evidence date, movement, and source. Mark absent baselines or stale updates.
7. Shape the narrative: quarter intent, results, drivers, misses, lessons, strategic decisions, and next-quarter implications.
8. Draft the pack using the output contract. Include source notes on each section or slide.

Analysis rules

• Preserve every outcome’s native score format; never add or average percentages, counts, currency, and milestones.
• Separate achieved results from completed activity.
• Attribute causality only when recorded evidence supports it; otherwise label it as a hypothesis.
• Show both strong and weak evidence. Never treat missing updates as success.
• Create a presentation file when the user requests a QBR pack or deck and presentation generation is supported; provide a complete Markdown slide-ready outline when the user asks for an outline or presentation generation is unavailable.
• Default to read-only Tability access. Confirm before any write.

Presentation and artifacts

Honor an explicitly requested format. Treat a request for a QBR pack or deck as presentation-native: create the presentation when supported, using charts, timelines, and decision layouts only where the evidence warrants them. Otherwise return the complete Markdown slide-ready outline. Use a document or PDF only when requested.

Give every slide a message-led headline, concise interpretation, native units, accessible labels, evidence dates, and source notes. Never aggregate unlike metrics or use generated imagery as analytical evidence. Render and visually verify the complete deck for clipping, readability, labels, legends, and factual consistency, and report only files actually created.

Output contract

Produce an 8–12 section pack:

1. Title, scope, and reporting window
2. Executive summary
3. Quarter intent and strategic context
4. Outcome scorecard
5. Material wins and evidence
6. Misses, risks, and unresolved dependencies
7. Initiative delivery and business effect
8. Lessons and hypotheses
9. Decisions required
10. Next-quarter priorities and measures
11. Evidence gaps and appendix sources

For each section, provide the headline, recommended visual, three to five supporting points, and source notes.

Read references/sample-output.md for a compact example.