Use when reviewing UI for accessibility — WCAG 2.2 AA, keyboard nav, focus, ARIA, contrast, screen-reader semantics — even on 'is this a11y-OK?' or 'mach das barrierefrei'.
The English summary is being prepared. Showing the original description.
Use when qualifying or disqualifying a single deal — MEDDIC slots with evidence, inversion test, disqualification heuristic. Triggers on 'is this deal real', 'should we walk away'.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Do NOT use to design pipeline stages (route to
pipeline-strategy), construct the forecast call (route to
forecast-accuracy), or build cross-deal pattern libraries (out of
scope — this skill is single-deal qualification, one cycle).
docs/contracts/mental-models.md § 30.mental-models.md § 9.mental-models.md § 13.context-spine.Latest call notes, last three buyer messages, named contacts and
their org roles, current stage, age in stage, and the
stage-definitions.md from pipeline-strategy. Without exit
criteria you cannot test whether the deal earned its current stage.
For each slot, write the claim plus the evidence (a buyer artefact, a recording, a forwarded email, a board agenda) — not "rep believes".
Write the one sentence that, if true, kills the deal. If no sentence is true, the deal is qualified for its stage. If a sentence is true and there is no countermeasure planned, the deal moves to disqualified-pending-evidence.
Disqualify if any two of:
Disqualification is not failure; it is recovered selling time.
For slots still open, set the trigger and deadline: "<slot> re-qualified when <buyer artefact> arrives by <date>." If the date passes without the artefact, the slot reverts to unfilled and Step 3 runs again.
Hand the MEDDIC card, the inversion sentence, and the re-qualification
triggers to the rep for the next buyer interaction and to
forecast-accuracy for the
forecast call. A deal with two or more unfilled MEDDIC slots cannot
be commit, regardless of $ value or stage.
WHEN to use this
WHEN NOT to use this
pipeline-strategy.forecast-accuracy.funnel-analysis.meddic-card.md — six slots, one claim per slot with evidence link or quote. Unfilled slots flagged.inversion-sentence.md — the one reason this deal will not close; countermeasure (or "none — disqualify").requalification-triggers.md — per-slot trigger + deadline + revert behaviour.Mid-market deal, $ 180 k ACV, stuck at Proposal for 47 days.
forecast-accuracy moves the deal out of commit until the slots fill.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when reviewing UI for accessibility — WCAG 2.2 AA, keyboard nav, focus, ARIA, contrast, screen-reader semantics — even on 'is this a11y-OK?' or 'mach das barrierefrei'.
The English summary is being prepared. Showing the original description.
Use when defining or auditing the activation event — aha-moment selection, retention correlation, falsifiable definition. Triggers on 'what is our aha moment', 'redefine activation'.
The English summary is being prepared. Showing the original description.
Use when capturing an architectural decision — file naming, next ADR number, Status / Context / Decision / Consequences, index regen; fires even without saying 'ADR'.
The English summary is being prepared. Showing the original description.
Adversarial critique — devil's advocate, stress-test, honest teardown ('poke holes', 'be brutal', 'was hältst du davon'); explicit request only. Routine code or design review → code-review.
The English summary is being prepared. Showing the original description.
Use when reading, creating, or updating agent documentation, module docs, roadmaps, or AGENTS.md. Understands the full .augment/, agents/, and copilot-instructions structure.
The English summary is being prepared. Showing the original description.
Use for an adversarial red-team / blue-team / auditor review of an AI agent's CONFIG + behaviour (rules, skills, MCP, hooks, permissions) — attack-chain → defensive-gap list, not a code audit.
The English summary is being prepared. Showing the original description.