gestion-alcance-scope

Adjust domain modeling granularity and temporal perspective between As-Is and To-Be states.

Updated Dec 26, 2025

Search Tags:#stakeholder alignment #scope management #process modeling #granularity #domain storytelling #as-is vs to-be

Ready to run

npx skills add https://github.com/imaginabit/Agente-Domain-Storytelling --skill gestion-alcance-scope

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gestion-alcance-scope
Source: https://github.com/imaginabit/Agente-Domain-Storytelling/tree/main/skills/gestion-alcance-scope
Command: npx skills add https://github.com/imaginabit/Agente-Domain-Storytelling --skill gestion-alcance-scope

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you precisely define and adjust the scope of your domain modeling efforts, ensuring the right level of detail and temporal perspective (current vs. future) are used, preventing over- or under-modeling and managing stakeholder expectations effectively.

Core Features & Use Cases

Granularity Adjustment: Switch between high-level "bird's-eye view" (coarse-grained) and detailed "underwater" (fine-grained) perspectives.
Temporal Perspective Management: Clearly distinguish between the current process (As-Is) and the desired future process (To-Be).
Use Case: During a workshop, you start with a high-level overview of a sales process. When developers ask for implementation details, you can seamlessly zoom into the fine-grained steps of the proposal generation phase, then zoom back out for the executive summary.

Quick Start

Use the gestion-alcance-scope skill to help define the scope for modeling the current customer onboarding process.

Frequently Asked Questions about gestion-alcance-scope

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

FAQPage Schema

How do I define the right granularity for domain storytelling and process modeling?▼

To manage scope effectively, distinguish between the As-Is current process state and the To-Be future state. Separating these temporal perspectives ensures accurate baseline documentation while aligning stakeholder expectations for future process improvements.

How do I adjust process modeling scope dynamically during a stakeholder workshop?▼

Dynamic scope adaptation allows you to zoom into fine-grained steps when developers request implementation specifics, then zoom back out to a high-level executive summary. This keeps stakeholder alignment by matching detail levels to the project phase and audience.

What is the best way to prevent over-modeling when documenting an as-is process?▼

The best way to prevent over-modeling is to explicitly define your modeling scope by setting the appropriate granularity. Starting with a high-level bird's-eye view of the as-is process ensures you capture essential workflow without unnecessary underwater detail.

Can I switch between high-level and fine-grained perspectives for the same domain model?▼

Yes, you can seamlessly switch between high-level and fine-grained perspectives for the same domain model. Adjusting the modeling scope on the fly allows you to address specific audience requirements during a workshop without losing the overall process context.