sm:invalidate-score

Score interview assumptions as validated, invalidated, or open with pull signals.

5|2|Updated Mar 8, 2026
One-click install
npx skills add https://github.com/mnfst-ai/Stage_Manager_Skills --skill sm-invalidate-score
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sm:invalidate-score
Source: https://github.com/mnfst-ai/Stage_Manager_Skills/tree/main/plugins/stage-manager/skills/invalidate-score
Command: npx skills add https://github.com/mnfst-ai/Stage_Manager_Skills --skill sm-invalidate-score

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps builders turn messy interview notes into actionable clarity by scoring assumptions as validated, invalidated, or open and by surfacing whether any form of pull appeared during conversations.

Core Features & Use Cases

  • Assumption Scoring: Reads an account of one or more invalidation interviews and assigns each original assumption a verdict: Validated, Invalidated, or Open.
  • Pull Signal Identification: Names observed pull signal types (lean-in, reach, referral, emotion, behavior, time) and highlights their implications for the foundation assumption.
  • Next-Step Guidance: Provides a concise foundation verdict and recommended follow-ups such as running further interviews, revising the assumption, or proceeding to build.
  • Use Case: A builder returns from three customer calls unsure whether demand exists; use this Skill to synthesize the accounts, reveal any pull, and decide whether to proceed or re-test.

Quick Start

Use /sm:invalidate-score to analyze an interview account and return scored assumptions with identified pull signals and a clear foundation verdict.

Frequently Asked Questions about sm:invalidate-score

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

FAQPage Schema
How do I score assumptions from customer interviews?

To score assumptions from customer interviews, process the interview accounts to assign each assumption a verdict of validated, invalidated, or open based on the evidence provided. This synthesis reveals pull and surfaces next steps.

What is a pull signal in customer research?

A pull signal in customer research is an observed indicator of demand, categorized into types like lean-in, reach, referral, emotion, behavior, or time. Identifying these signals during assumption scoring highlights implications for your foundation.

How do I synthesize multiple invalidation interviews?

To synthesize multiple invalidation interviews, input the combined accounts to evaluate each assumption across all conversations. This process detects overall pull signals, assigns per-assumption scores, and generates a foundation verdict with recommended next actions.

What should I do after scoring interview assumptions?

After scoring interview assumptions, review the structured verdict and recommended next actions. Depending on the evidence and pull signals, you should run further interviews, revise the assumption, or proceed to build the product.

Can I analyze customer research notes to decide whether to proceed or re-test?

Yes, you can analyze customer research notes to decide whether to proceed or re-test by synthesizing the accounts to reveal demand. The output provides a clear foundation verdict and recommended follow-ups based on detected pull signals.