decision-normalization

Name: decision-normalization
Availability: InStock
Author: wlee075

Normalize PM decision responses into RESOLVED or UNRESOLVED requirement statements.

Updated Apr 16, 2026

Search Tags:#requirements #clarification #decision #normalization #unresolved #product-management #resolved

Ready to run

npx skills add https://github.com/wlee075/chatbot --skill decision-normalization

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: decision-normalization
Source: https://github.com/wlee075/chatbot/tree/main/skills/decision_normalization
Command: npx skills add https://github.com/wlee075/chatbot --skill decision-normalization

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Normalize a PM response into a canonical, implementable requirement statement — or mark it unresolved.

Core Features & Use Cases

Formalizes PM decisions into RESOLVED statements or UNRESOLVED signals for clarification cycles.
Enforces the two-output contract and faithfulness to the PM's input; supports flow with Clarification Controller and Decision Normalizer.
Provides guardrails to avoid invention or synthesis of details beyond what was stated.

Quick Start

Provide a PM decision answer and let the system output a concise, implementable RESOLVED statement or UNRESOLVED.

Frequently Asked Questions about decision-normalization

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

FAQPage Schema

How do I normalize product management decisions into implementable requirements?▼

To normalize product management decisions, you provide the PM decision response to generate a canonical, implementable requirement statement or mark it unresolved. This enforces a two-output contract, outputting either RESOLVED or UNRESOLVED to formalize the decision.

What is a RESOLVED or UNRESOLVED output contract in decision clarification cycles?▼

A RESOLVED or UNRESOLVED output contract is a binary framework that formalizes PM decisions. RESOLVED outputs a concise, implementable requirement statement, while UNRESOLVED signals the need for further clarification, ensuring decisions are explicitly codified without ambiguity.

How do I log PM decisions without adding fabricated details or assumptions?▼

To log PM decisions without adding fabricated details, the normalization process enforces strict faithfulness to the PM's original input. It provides guardrails that forbid inventing or synthesizing details beyond what was explicitly stated, preserving the integrity of the decision log.

Can I integrate decision normalization with an existing Clarification Controller workflow?▼

Yes, you can integrate decision normalization with a Clarification Controller. The system is specifically designed to support workflow flows with the Clarification Controller and Decision Normalizer to manage clarification cycles and log binary or explicit selections.

When should I mark a product management decision as UNRESOLVED during requirement codification?▼

You should mark a product management decision as UNRESOLVED when the PM's input lacks sufficient clarity for implementation. This signals the clarification cycle to continue, ensuring no requirements are forced through normalization without explicit, actionable details.