pitch

Generates a Markdown stakeholder briefing with metrics, architecture diff, and intent fulfillment.

8|9|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/vibercoder79/KI-Masterclass-Koerting- --skill pitch-vibercoder79
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pitch
Source: https://github.com/vibercoder79/KI-Masterclass-Koerting-/tree/main/code-crash%20framework/pitch
Command: npx skills add https://github.com/vibercoder79/KI-Masterclass-Koerting- --skill pitch-vibercoder79

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Creates a reliable, evidence-based stakeholder pitch briefing by collecting metrics, architecture changes, and intent fulfillment so you do not have to assemble the story manually.

Core Features & Use Cases

  • Stakeholder-ready evidence briefing: Produces a single Markdown file at pitch/PITCH-XX.md with the exact sections stakeholders expect for a pitch.
  • Architecture diff since last pitch: Computes what changed in ARCHITECTURE_DESIGN.md by comparing against the previous pitch timestamp (or summarizes full state for the first pitch).
  • Intent fulfillment scoring: Measures progress against success criteria from related intents and includes per-intent scores (with null when not unambiguously measurable).
  • Demo-path proposal: Suggests a user-journey-style demo path (operator-editable) based on change intensity and intent relevance.
  • Read-only governance separation: Never writes to the learning loop (L3/journal/learnings.db), keeping this skill strictly for pitch preparation.

Quick Start

Run the pitch skill by asking for the stakeholder briefing when you want to present sprint progress: “prepare pitch for Sprint X with intents INTENT-3 and INTENT-5”.

Frequently Asked Questions about pitch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prepare an evidence-based stakeholder briefing for a sprint review?

A stakeholder pitch briefing combines sprint metrics, architecture diffs, and intent fulfillment scores into a single Markdown file. It provides a factual cheat sheet and a guided demo path, eliminating the need to manually assemble the presentation story.

What is architecture diff computation and how does it work for sprint presentations?

Architecture diff computation compares the current ARCHITECTURE_DESIGN.md state against the previous pitch timestamp. It identifies structural changes since the last stakeholder update, or summarizes the full architecture state if it is the initial pitch.

How do I measure intent fulfillment for a stakeholder pitch?

Intent fulfillment scoring measures sprint progress against predefined success criteria from related intents. The assessment includes per-intent scores to show stakeholder progress, returning null values when criteria cannot be unambiguously measured.

Can I generate a demo path proposal from sprint metrics and architecture changes?

Yes, a demo path proposal is generated based on change intensity and intent relevance. It suggests a user-journey-style demonstration flow for stakeholders, which the operator can edit before the actual sprint presentation.

What is the best way to format sprint updates for stakeholders without using slides?

The best way to format sprint updates without slides is generating a Markdown briefing at pitch/PITCH-XX.md. This output provides a factual cheat sheet containing metrics, architecture diffs, and intent fulfillment scores for stakeholder review.

Does the stakeholder pitch process write to the learning loop database?

No, the stakeholder pitch process maintains read-only governance separation and never writes to the learning loop database. It strictly reads environment configurations and local sources to produce pitch preparation artifacts without modifying learning data.