facilitacion-knowledge-crunching

Facilitate Domain Storytelling sessions by detecting logical gaps and documenting pain points.

Updated Dec 26, 2025
One-click install
npx skills add https://github.com/imaginabit/Agente-Domain-Storytelling --skill facilitacion-knowledge-crunching
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: facilitacion-knowledge-crunching
Source: https://github.com/imaginabit/Agente-Domain-Storytelling/tree/main/skills/facilitacion-knowledge-crunching
Command: npx skills add https://github.com/imaginabit/Agente-Domain-Storytelling --skill facilitacion-knowledge-crunching

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you refine domain stories by actively identifying logical gaps (plot holes), systematically recording variations with annotations, and pinpointing user frustrations (pain points) within a process.

Core Features & Use Cases

  • Plot Hole Detection: Identify and question missing steps or logical leaps in a narrative.
  • Annotation System: Record variations, errors, assumptions, and pain points separately to keep the main story clean.
  • Pain Point Identification: Detect and document user frustrations, inefficiencies, and problems in the current process.
  • Knowledge Crunching: Extract tacit knowledge, implicit rules, and expert insights.
  • Use Case: During a Domain Storytelling workshop, use this Skill to ensure the documented process is complete, accurate, and captures all critical user feedback and potential issues.

Quick Start

Use the facilitacion-knowledge-crunching skill to identify plot holes in the provided process description.

Frequently Asked Questions about facilitacion-knowledge-crunching

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

FAQPage Schema
How do I identify plot holes during a Domain Storytelling session?

To identify plot holes during a Domain Storytelling session, this Skill employs active listening and targeted questioning to uncover missing steps and logical leaps. It systematically records these variations as structured annotations to maintain narrative clarity.

What is the best way to document user pain points and process variations?

The best way to document user pain points and process variations is through a structured annotation system. This approach records errors, assumptions, and user frustrations separately, keeping the main domain story clean while capturing critical process feedback.

Can I use knowledge crunching to extract tacit information from domain experts?

Yes, you can use knowledge crunching to extract tacit information from domain experts. The Skill facilitates targeted questioning during storytelling to extract implicit rules and expert insights, ensuring critical domain knowledge is captured accurately.

How do I maintain narrative clarity when capturing complex domain details?

To maintain narrative clarity when capturing complex domain details, the Skill utilizes structured annotation techniques. By separating variations, errors, and assumptions from the core narrative, it prevents the main story from becoming cluttered with extraneous information.

When do I need facilitated domain storytelling for process analysis?

You need facilitated domain storytelling for process analysis when you must uncover hidden insights, refine existing narratives, and pinpoint user frustrations. It is essential for systematically documenting process variations and identifying logical gaps in complex workflows.