skills.rest
SensLiao
SensLiaoCOMMUNITY
Explore all skills by this author →
GitHub

i2r-elicitation-mode

Classify evidence and map assumptions by risk during I2R intake and context stages.

Updated May 28, 2026
Search Tags:#product development#evidence classification#risk mapping#i2r#intake and context
One-click install
npx skills add https://github.com/SensLiao/Claude-code-setting --skill i2r-elicitation-mode
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: i2r-elicitation-mode
Source: https://github.com/SensLiao/Claude-code-setting/tree/main/skills/i2r-elicitation-mode
Command: npx skills add https://github.com/SensLiao/Claude-code-setting --skill i2r-elicitation-mode

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of accurately classifying evidence and mapping assumptions during the intake and context stages of I2R, ensuring that stated behaviors are distinct from assumed generics and that risks are properly assessed.

Core Features & Use Cases

  • Evidence Classification: Differentiates between stated past-behavior evidence and assumed generics.
  • Risk Mapping: Maps assumptions by risk, allowing for informed decision-making.
  • Use Case: When processing raw ideas or clarification answers before writing intake or context JSON files, this Skill helps classify evidence and identify the most critical assumptions.

Quick Start

Use the i2r-elicitation-mode skill to classify evidence and map assumptions for your I2R intake and context stages.

Frequently Asked Questions about i2r-elicitation-mode

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

FAQPage Schema
How do I classify evidence and map assumptions during product development intake?▼

Evidence classification in I2R intake separates stated past-behavior evidence from assumed generics, enabling accurate risk mapping for early-stage product development and riskiest assumption identification.

What is the best way to identify riskiest assumptions from raw product ideas?▼

Identify riskiest assumptions by mapping assumed generics from raw ideas against stated past-behavior evidence, generating risk assessments that prioritize critical assumptions for product development decisions.

How do I separate stated past-behavior evidence from assumed generics in I2R?▼

Separate stated past-behavior evidence from assumed generics by processing raw clarification answers, classifying observed facts while isolating unverified assumptions to generate structured intake and context JSON files.

When do I need evidence classification for early-stage product development?▼

You need evidence classification when processing raw ideas or clarification answers before writing intake or context JSON files, ensuring assumptions are properly assessed for riskiest decision-making in product development.

Can I use i2r-elicitation-mode for risk mapping before writing context JSON files?▼

Yes, you can use i2r-elicitation-mode for risk mapping before writing context JSON files, as it classifies evidence and maps assumptions during I2R intake and context stages to identify critical risks.

Related Skills

Explore More Product & Management Skills→
dformosodformoso

define

Guide product development defining phases by mapping assumptions and framing hypotheses.

Community
Advanced
0xUrsanomics0xUrsanomics
2

premortem

Simulate future failure states to identify risks and hidden assumptions in strategic plans.

Community
Advanced
tarunccettarunccet
5

brainstorm-experiments-new

Design pretotype experiments and XYZ hypotheses to validate product concepts.

Community
Intermediate
officebeatsofficebeats
8

prioritize-assumptions

Prioritize product assumptions using an Impact × Risk matrix and suggest validation experiments.

Community
Intermediate