reframe

Validate complex problems before PDCA planning using a 5-phase, 21-question challenge protocol.

2|1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/solitasroh/mcukit --skill reframe-solitasroh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: reframe
Source: https://github.com/solitasroh/mcukit/tree/main/skills/reframe
Command: npx skills add https://github.com/solitasroh/mcukit --skill reframe-solitasroh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reframe provides a disciplined, phase-driven approach to validate complex feature problems before entering PDCA planning, reducing risk and misalignment.

Core Features & Use Cases

  • Structured problem framing across five phases
  • Domain-aware evaluation: MCU/MPU/WPF contexts
  • Pre-mortem, assumption mapping, and MECE guidance to shape plan

Quick Start

Invoke /reframe <feature> to start the problem validation flow before PDCA planning.

Frequently Asked Questions about reframe

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

FAQPage Schema
How do I validate complex problem framing before starting PDCA planning?

You validate complex problems before PDCA planning by applying a structured 5-phase, 21-question challenge protocol that guides problem framing, demand reality, pre-mortem, assumption mapping, and MECE decomposition.

What is assumption mapping and how does it reduce risk in feature scoping?

Assumption mapping reduces risk in feature scoping by identifying and evaluating underlying hypotheses before development. It operates within a structured validation workflow to ensure outputs align with PDCA planning.

Can I use MECE decomposition for ambiguity-rich scenarios in MCU and WPF development?

Yes, you can use MECE decomposition for ambiguity-rich scenarios in MCU, MPU, and WPF development. The validation protocol applies domain-aware evaluation to ensure structured decomposition aligns with feature scoping.

How do I run a pre-mortem analysis for a new feature idea?

You run a pre-mortem analysis for a new feature idea by invoking the validation flow, which integrates pre-mortem considerations alongside assumption mapping and MECE decomposition to anticipate failures before PDCA planning.

When should I use a structured problem validation protocol instead of direct PDCA planning?

You should use a structured problem validation protocol instead of direct PDCA planning when facing ambiguity-rich scenarios or complex MCU, MPU, and WPF feature ideas that require disciplined problem framing and assumption mapping to reduce misalignment.