efactory-discovery-engine

Generates Lean Inception and DDD discovery documents with Mermaid diagrams for product workshops.

Updated Jul 13, 2026
One-click install
npx skills add https://github.com/eencinasq/cripto-pos --skill efactory-discovery-engine-eencinasq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: efactory-discovery-engine
Source: https://github.com/eencinasq/cripto-pos/tree/main/.kiro/skills/efactory-discovery-engine
Command: npx skills add https://github.com/eencinasq/cripto-pos --skill efactory-discovery-engine-eencinasq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Structuring early product discovery is chaotic: personas, journeys, domain models, and MVP scope often end up scattered across inconsistent files. This Skill runs ASDD Discovery Phases -1/0 as a two-track workshop (Lean Inception + Domain-Driven Design) and produces a canonical, reviewable documentation folder. ## Core Features & Use Cases - Two-track discovery output: Generates lean-inception.md (all 9 Lean activities), ddd.md (ubiquitous language, bounded contexts, events, aggregates), diagrams.md (Mermaid only), intent-draft.md, and slices.md for large modules under docs/discovery/<slug>/. - Mermaid diagram library: Provides ready templates for the Phase 0 gate, MVP canvas, context map, EventStorming-lite, sequencer waves, and aggregate invariants. - Anti-duplication rules: Forbids scattered *-personas.md/*-features.md files and premature .kiro/specs/ intent files, enforcing a single canonical layout. - Use Case: A team kicking off a new crypto POS module asks the agent to run deep discovery with slug merchant-payments; the Skill creates the full discovery folder with Lean activities, DDD context map, and an intent draft ready for Product Owner approval. ## Quick Start Ask the agent to run deep discovery for your product with a chosen slug, entry mode, and size class, writing the two-track Lean Inception and DDD folder into docs/discovery/<slug>/ in your execution repo.

Frequently Asked Questions about efactory-discovery-engine

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

FAQPage Schema
How do I run a Lean Inception workshop with an AI agent?▼

Invoke the discovery skill with your product name, a slug, entry mode (IMPROVEMENT or NEW_PRODUCT), and size class. It generates all 9 Lean Inception activities as prose in lean-inception.md plus matching Mermaid diagrams in diagrams.md under docs/discovery/<slug>/.

What files does the discovery folder layout require?▼

The canonical layout requires README.md with the Phase 0 gate diagram, lean-inception.md, ddd.md, diagrams.md, and intent-draft.md. LARGE_MODULE discoveries also add slices.md for slice decomposition; separate persona or feature files are forbidden.

How do I document bounded contexts and domain events for a new module?▼

The DDD track produces ddd.md covering ubiquitous language, bounded contexts, EventStorming-lite domain events, and aggregates with invariants, plus a context map using relationship patterns like Customer-Supplier and Conformist.

When should I use SLICE mode instead of LARGE_MODULE discovery?▼

Use SLICE mode for small improvements touching a single capability; LARGE_MODULE applies when there are 3 or more capabilities or 2 or more bounded contexts. LARGE_MODULE requires slices.md and forbids a monolithic .kiro/specs/ intent file.

Can discovery output go directly into .kiro/specs/?▼

No. Discovery writes only intent-draft.md in docs/discovery/<slug>/. The Product Owner companion skill creates per-slice APPROVED intent.md files under .kiro/specs/<slice>/ after the Phase 0 gate passes.