@tailor-platform/erp-kit 0.3.0 → 0.4.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@tailor-platform/erp-kit",
-  "version": "0.3.0",
+  "version": "0.4.1",
   "description": "Opinionated ERP toolkit for building business applications on Tailor Platform",
   "license": "MIT",
   "bin": {
@@ -35,12 +35,13 @@
   "devDependencies": {
     "@tailor-platform/function-kysely-tailordb": "0.1.3",
     "@tailor-platform/function-types": "0.8.2",
-    "@tailor-platform/sdk": "1.25.1",
+    "@tailor-platform/sdk": "1.25.2",
     "@types/mdast": "^4.0.4",
     "@types/node": "^25.1.0",
+    "@typescript-eslint/parser": "^8.57.0",
     "eslint": "10.0.3",
     "kysely": "0.28.11",
-    "tsdown": "0.21.2",
+    "tsdown": "0.21.3",
     "typescript": "^5.7.3",
     "vitest": "^4.0.0",
     "@tailor-platform/eslint-config": "0.0.1"
@@ -48,7 +49,7 @@
   "peerDependencies": {
     "@tailor-platform/function-kysely-tailordb": "0.1.3",
     "@tailor-platform/function-types": "0.8.2",
-    "@tailor-platform/sdk": "1.25.1",
+    "@tailor-platform/sdk": "1.25.2",
     "kysely": "0.28.11"
   },
   "engines": {

package/skills/erp-kit-app-1-requirements/SKILL.md

@@ -10,7 +10,7 @@ Create Tier 1-2 documentation: Requirements, Actors, and Business Flows.
 ## Workflow Phases
 
 ```
-GATHER → CLARIFY → CREATE → VALIDATE
+GATHER → CLARIFY → CREATE → STORY EXTRACTION → VALIDATE
 ```
 
 ### Phase 1: Gather
@@ -26,15 +26,14 @@ Focus on "what" the application should do, not "how" it will be implemented.
 
 ### Phase 2: Clarify
 
-Use AskUserQuestion to clarify undefined requirements:
+Use AskUserQuestion to clarify undefined requirements. Focus on business-level scope and workflows — not platform capabilities like authentication.
 
-| Category          | Example Questions                              |
-| ----------------- | ---------------------------------------------- |
-| Authentication    | External IdP / Password / Out of scope?        |
-| User Operations   | Direct creation / Email invitation / Both?     |
-| Roles             | Fixed roles (Admin/User) / Custom roles?       |
-| User Self-Service | View only / Profile edit / Password change?    |
-| Lifecycle         | Create only / Full lifecycle (activate/deact)? |
+| Category         | Example Questions                                                            |
+| ---------------- | ---------------------------------------------------------------------------- |
+| Scope            | Which steps are MVP-essential? Any steps that can be deferred?               |
+| Edge Cases       | How far to handle cancellation, rejection, or mid-flow abandonment?          |
+| Actor Boundaries | Are approver and executor separate? What is each actor's operational scope?  |
+| Business Rules   | Which steps are automated vs manual? What conditional branches exist?        |
 
 Ask 3-4 questions at a time using multiSelect where appropriate.
 
@@ -62,7 +61,9 @@ erp-kit app generate doc business-flow {FLOW_NAME} -p {APP_ROOT}/{APP_NAME}
     README.md                                ← Tier 1 (from app init)
     docs/
       actors/{actor-name}.md                 ← Tier 2 (from generate doc actors)
-      business-flow/{flow-name}/README.md    ← Tier 2 (from generate doc business-flow)
+      business-flow/{flow-name}/
+        README.md                              ← Tier 2 (from generate doc business-flow)
+        story/{actor}--{story-name}.md         ← Tier 2 (from Phase 3b story extraction)
 ```
 
 **Schema constraints:** See [erp-kit-app-shared/references/schema-constraints.md](../erp-kit-app-shared/references/schema-constraints.md) for H1 heading rules, naming conventions, and requirements structure.
@@ -71,12 +72,37 @@ erp-kit app generate doc business-flow {FLOW_NAME} -p {APP_ROOT}/{APP_NAME}
 
 **Business flow `## Stories` section:**
 
-At Tier 2, story files do not exist yet. Use `- TBD` as a placeholder to avoid broken link violations. Replace with actual story links in `/erp-kit-app-3-plan`.
+Use `- TBD` as a placeholder during flow creation. These will be replaced with actual story links in Phase 3b below.
+
+### Phase 3b: Story Extraction
+
+After creating business flows, extract and create story documentation.
+
+1. **Collect** all business flow docs: glob `<APP_ROOT>/docs/business-flow/*/README.md`
+2. **Dispatch story extraction agents** — one Agent per business flow (parallelize if possible). Each agent:
+   - Reads the prompt template from [references/story-extraction.md](references/story-extraction.md)
+   - Replace `{{APP_NAME}}` with the resolved app name
+   - Replace `{{ACTOR_DOCS}}` with the actor doc file paths
+   - Replace `{{BUSINESS_FLOW_DOCS}}` with ONLY the single business flow doc for that agent
+   - Dispatch the agent with the filled prompt
+
+3. **Scaffold & populate** story docs from agent results:
+
+```bash
+# For each story identified
+erp-kit app generate doc story <flow>/<actor>--<story> -p {APP_ROOT}/{APP_NAME}
+```
+
+4. **Link stories** in business flow READMEs: replace `- TBD` placeholders in each flow's `## Stories` section with actual links:
+
+```markdown
+- [Story Title](./story/<actor>--<story-name>.md)
+```
 
 ### Phase 4: Validate
 
 ```bash
-pnpm run app:doc:check
+erp-kit app check -p {APP_ROOT}
 ```
 
 See [schema-constraints.md](../erp-kit-app-shared/references/schema-constraints.md) for notes on expected "No matching files found" output.
@@ -88,6 +114,7 @@ See [schema-constraints.md](../erp-kit-app-shared/references/schema-constraints.
 | `requirements.yml`  | 1    | `README.md`                           |
 | `actors.yml`        | 2    | `docs/actors/<name>.md`               |
 | `business-flow.yml` | 2    | `docs/business-flow/<flow>/README.md` |
+| `story.yml`         | 2    | `docs/business-flow/<flow>/story/<actor>--<name>.md` |
 
 ## Next Step
 

package/skills/{erp-kit-app-3-plan → erp-kit-app-1-requirements}/references/story-extraction.md

@@ -51,7 +51,7 @@ For each story, extract:
 
 For each story, determine:
 
-- **Needs resolvers**: Story involves create/update/delete operations → mark as `- TBD` for resolvers
+- **Needs resolvers**: Story involves create/update/delete operations → mark as `TBD` for resolvers
 - **Read-only**: Story only views/lists data → mark as `None` for resolvers
 
 ## Naming Convention

package/skills/erp-kit-app-2-requirements-review/SKILL.md

@@ -22,12 +22,13 @@ Define shared context for all agents:
 - `APP_README`: `<APP_ROOT>/README.md`
 - `BUSINESS_FLOW_DOCS`: glob `<APP_ROOT>/docs/business-flow/*/README.md`
 - `ACTOR_DOCS`: glob `<APP_ROOT>/docs/actors/*.md`
+- `STORY_DOCS`: glob `<APP_ROOT>/docs/business-flow/*/story/*.md`
 
 Verify at least `APP_README` exists. If not, stop with: "No application README found at <APP_ROOT>. Run erp-kit-app-1-requirements first."
 
 ## Step 2: Dispatch Agents (parallelize if possible)
 
-Launch 2 Agent tool calls in parallel — one per review concern.
+Launch 3 Agent tool calls in parallel — one per review concern.
 Each agent receives: APP_NAME, relevant doc file paths.
 Each agent returns: structured markdown per [references/requirements-report-format.md](references/requirements-report-format.md).
 
@@ -35,13 +36,15 @@ Each agent returns: structured markdown per [references/requirements-report-form
 | ----- | ------------------------------------------------------------------------------------ | ------------------------------------------ |
 | 1     | [references/best-practices-check.md](references/best-practices-check.md)             | APP_README, ACTOR_DOCS, BUSINESS_FLOW_DOCS |
 | 2     | [references/boundary-consistency-check.md](references/boundary-consistency-check.md) | APP_README, ACTOR_DOCS, BUSINESS_FLOW_DOCS |
+| 3     | [references/story-quality-check.md](references/story-quality-check.md)               | APP_README, ACTOR_DOCS, BUSINESS_FLOW_DOCS, STORY_DOCS |
 
 For each agent:
 
 1. Read the prompt template file
 2. Replace `{{APP_NAME}}` with the resolved app name
 3. Replace `{{APP_README}}`, `{{ACTOR_DOCS}}`, `{{BUSINESS_FLOW_DOCS}}` with the actual file paths
-4. Dispatch the agent with the filled prompt
+4. Replace `{{STORY_DOCS}}` with the story doc file paths (agent 3 only)
+5. Dispatch the agent with the filled prompt
 
 ## Step 3: Aggregate & Validate
 
@@ -52,7 +55,18 @@ After ALL agents return:
 3. Merge all `recommendations[]` arrays into a single list
 4. **Filter out** any recommendation that would violate `erp-kit app check` schema constraints (e.g., title-casing business flow H1 headings)
 5. Calculate totals across all summaries
-6. Render the final report below
+
+## Step 4: Priority Validation
+
+Subagents tend to over-classify. Before rendering the report, re-evaluate every non-pass finding:
+
+- **"Is this even this application's responsibility?"** — If the concern belongs to a module or is out of scope, drop it from the report
+- **"Does this block proceeding to planning?"** → `critical`
+- **"Will this force Tier 3-4 rework (stories, screens, resolvers)?"** → `high`
+- **"Is this a quality improvement with no rework risk?"** → `medium`
+- All no → `low`, regardless of subagent label
+
+## Step 5: Render Report
 
 ## Report Format
 
@@ -82,14 +96,24 @@ Render the aggregated results as markdown:
 
 ---
 
-### 3. Summary
+### 3. Story Quality
+
+| Story/Flow | Check | Status | Detail |
+| ---------- | ----- | ------ | ------ |
+
+(Populated from agent 3 issues)
+
+---
+
+### 4. Summary
 
 | Aspect                    | Status | Details           |
 | ------------------------- | ------ | ----------------- |
 | Best Practices            |        | X/Y checks passed |
 | Documentation Consistency |        | X/Y checks passed |
+| Story Quality             |        | X/Y checks passed |
 
-### 4. Recommendations
+### 5. Recommendations
 
 Numbered list of actionable fixes, grouped by priority:
 

package/skills/erp-kit-app-2-requirements-review/references/best-practices-check.md

@@ -11,6 +11,10 @@ Business flow docs: {{BUSINESS_FLOW_DOCS}}
 
 Read [erp-kit-app-shared/references/schema-constraints.md](../../erp-kit-app-shared/references/schema-constraints.md) before evaluating. **Never recommend changes that violate the schema.**
 
+## Tier 2 Scope
+
+This review targets Tier 1-2 documentation only. Stories (`## Stories` section in business flows) are created in step 3 (`erp-kit-app-3-plan`). A `- TBD` placeholder in the Stories section is expected and correct at this stage — do **not** flag it as incomplete or missing.
+
 ## Instructions
 
 1. Read the application README at the path above

package/skills/erp-kit-app-2-requirements-review/references/boundary-consistency-check.md

@@ -11,6 +11,10 @@ Business flow docs: {{BUSINESS_FLOW_DOCS}}
 
 Read [erp-kit-app-shared/references/schema-constraints.md](../../erp-kit-app-shared/references/schema-constraints.md) before evaluating. When checking `naming_consistency`, validate that H1 headings follow the schema rules — different doc types have different heading formats.
 
+## Tier 2 Scope
+
+This review targets Tier 1-2 documentation only. Stories (`## Stories` section in business flows) are created in step 3 (`erp-kit-app-3-plan`). A `- TBD` placeholder in the Stories section is expected and correct at this stage — do **not** flag it as a broken link, missing content, or incomplete documentation.
+
 ## Instructions
 
 1. Read the application README at the path above

package/skills/erp-kit-app-2-requirements-review/references/story-quality-check.md

@@ -0,0 +1,67 @@
+# Story Quality Check
+
+## Context
+
+App: {{APP_NAME}}
+Actor docs: {{ACTOR_DOCS}}
+Business flow docs: {{BUSINESS_FLOW_DOCS}}
+Story docs: {{STORY_DOCS}}
+
+## Instructions
+
+1. Read ALL actor docs at the paths above
+2. Read ALL business flow docs at the paths above
+3. Read ALL story docs at the paths above
+4. Validate story quality against the checks below
+5. Return results per the report format at the bottom
+
+## Checks
+
+### Story-to-Flow Parity
+
+For each business flow:
+- Every flow must have at least one story
+- Every story must map to exactly one flow (via its directory location)
+- The `## Stories` section in each flow README must link to all stories in its `story/` directory
+- No broken links in `## Stories` sections
+
+### Naming Conventions
+
+- Story filename must follow `<actor>--<story-name>.md` pattern (double-dash separator)
+- Actor slug in filename must match an existing actor doc
+- Story name portion must be kebab-case
+
+### Content Completeness
+
+For each story:
+- Must have scenario patterns (non-empty)
+- Must have preconditions and postconditions
+- Must have screen references (can be TBD at this stage)
+- Must have resolver classification (TBD for mutations, None for read-only)
+
+### Actor Consistency
+
+- Actor referenced in story filename must exist in `docs/actors/`
+- Actor referenced in story content must match the filename actor
+
+## Output Format
+
+Return findings as structured markdown:
+
+### Issues
+
+For each issue found:
+
+- **Check:** which check failed
+- **Scope:** which file/story/flow is affected
+- **Severity:** critical / high / medium / low
+- **Detail:** what's wrong and how to fix it
+
+### Summary
+
+| Check | Passed | Failed | Total |
+| ----- | ------ | ------ | ----- |
+| Story-to-Flow Parity | | | |
+| Naming Conventions | | | |
+| Content Completeness | | | |
+| Actor Consistency | | | |

package/skills/erp-kit-app-3-plan/SKILL.md

@@ -1,11 +1,11 @@
 ---
 name: erp-kit-app-3-plan
-description: Create Tier 3-4 documentation (stories, screens, resolvers) by breaking down business flows. Use after completing requirements review with erp-kit-app-2-requirements-review.
+description: Create Tier 3-4 documentation (screens, resolvers) by breaking down business flows and existing stories. Use after completing requirements review with erp-kit-app-2-requirements-review.
 ---
 
 # Business Flow Breakdown to Stories, Screens, and Resolvers
 
-Convert Tier 2 business flows into Tier 3 (stories, screens) and Tier 4 (resolvers) documentation using parallel extraction agents.
+Convert Tier 2 business flows and stories into Tier 3 (screens) and Tier 4 (resolvers) documentation using parallel extraction agents.
 
 ## When to Use
 
@@ -20,6 +20,7 @@ Tier 1-2 documentation must exist:
 - `README.md` (requirements)
 - `docs/actors/*.md` (actor definitions)
 - `docs/business-flow/*/README.md` (business workflows)
+- `docs/business-flow/<flow>/story/<actor>--<name>.md` (story definitions)
 
 ## Step 1: Setup
 
@@ -29,68 +30,75 @@ Define shared context for all agents:
 - `APP_NAME`: basename of APP_ROOT
 - `BUSINESS_FLOW_DOCS`: glob `<APP_ROOT>/docs/business-flow/*/README.md`
 - `ACTOR_DOCS`: glob `<APP_ROOT>/docs/actors/*.md`
+- `STORY_DOCS`: glob `<APP_ROOT>/docs/business-flow/*/story/*.md`
+- `MODULE_OVERVIEW`: output of `erp-kit doc modules`
 
 Verify at least `BUSINESS_FLOW_DOCS` is non-empty. If no business flow docs exist, stop with: "No business flow docs found under <APP_ROOT>/docs/. Run erp-kit-app-1-requirements first."
 
+Verify at least `STORY_DOCS` is non-empty. If no story docs exist, stop with: "No story docs found. Run erp-kit-app-1-requirements first to create stories."
+
+Collect module overview:
+
+```bash
+erp-kit doc modules
+```
+
+This returns each module's name, overview, command/query/model counts, and dependencies. Save the full output as `MODULE_OVERVIEW` — both agents receive it.
+
+> **Sync barrier:** `MODULE_OVERVIEW` must be collected before dispatching agents.
+
 ## Step 2: Dispatch Agents (parallelize if possible)
 
-Launch 3 Agent tool calls in parallel — one per extraction concern.
-Each agent receives: APP_NAME, relevant doc file paths.
+For each business flow in BUSINESS_FLOW_DOCS, launch 2 Agent tool calls in parallel — one per extraction concern.
+
+Each agent pair receives: APP_NAME, ACTOR_DOCS, the single business flow's STORY_DOCS, MODULE_OVERVIEW, and only that flow's BUSINESS_FLOW_DOC (singular).
 
-| Agent | Prompt Template                                                        | Inputs                                   |
-| ----- | ---------------------------------------------------------------------- | ---------------------------------------- |
-| 1     | [references/story-extraction.md](references/story-extraction.md)       | APP_NAME, ACTOR_DOCS, BUSINESS_FLOW_DOCS |
-| 2     | [references/screen-extraction.md](references/screen-extraction.md)     | APP_NAME, ACTOR_DOCS, BUSINESS_FLOW_DOCS |
-| 3     | [references/resolver-extraction.md](references/resolver-extraction.md) | APP_NAME, ACTOR_DOCS, BUSINESS_FLOW_DOCS |
+| Agent | Prompt Template                                                        |
+| ----- | ---------------------------------------------------------------------- |
+| A     | [references/screen-extraction.md](references/screen-extraction.md)     |
+| B     | [references/resolver-extraction.md](references/resolver-extraction.md) |
 
 For each agent:
 
 1. Read the prompt template file
 2. Replace `{{APP_NAME}}` with the resolved app name
-3. Replace `{{ACTOR_DOCS}}`, `{{BUSINESS_FLOW_DOCS}}` with the actual file paths
-4. Dispatch the agent with the filled prompt
+3. Replace `{{ACTOR_DOCS}}` with the actor doc file paths
+4. Replace `{{BUSINESS_FLOW_DOCS}}` with ONLY the single business flow doc for this iteration
+5. Replace `{{STORY_DOCS}}` with ONLY the stories under this flow's `story/` directory
+6. Replace `{{MODULE_OVERVIEW}}` with the output from `erp-kit doc modules`
+7. Dispatch the agent with the filled prompt
+
+With N business flows, this produces N × 2 parallel agents.
 
 ## Step 3: Aggregate & Present Plan
 
 After ALL agents return:
 
-1. Collect extraction results from each agent
-2. Present consolidated plan to user:
-   - Stories to create (with actor, flow, scenario patterns)
-   - Screens to create (with type, fields, actions)
+1. Collect extraction results from each agent, grouped by business flow
+2. **Deduplicate screens**: Screens referenced by multiple flows should appear once — merge field lists and story references
+3. Present consolidated plan to user:
+   - Existing stories (from STORY_DOCS, for reference)
+   - Screens to create (deduplicated, with type, fields, actions)
    - Resolvers to create (with operation type, module mapping)
-3. Wait for user approval
+## Step 4: Resolve Module Gaps
 
-## Step 4: Check Module Dependencies
+Step 2's resolver agent mapped resolvers to erp-kit modules using `MODULE_OVERVIEW` and flagged any operations that could not be mapped as module gaps.
 
-Before creating resolver docs, verify required modules exist:
+If there are no gaps, proceed to Step 5.
 
-```bash
-ls packages/erp-kit/src/modules/
-```
+**If resolvers require functionality that no erp-kit module provides:**
 
-For each resolver that references a module command, check the module and command exist:
+1. Group the unmapped operations by domain to identify what custom modules are needed
+2. Create each custom module using `erp-kit-module-1-requirements` skill
+3. Return to this step after the custom modules are ready
 
-```bash
-ls packages/erp-kit/src/modules/<module-name>/docs/commands/
-```
-
-**If modules don't exist:**
-
-1. Identify needed modules — group resolver operations by domain
-2. Create module docs first — use `erp-kit-module-1-requirements` skill
-3. Return to this step after modules have documented commands
-
-**Only reference existing module commands** in resolver documentation.
+For resolvers that reference erp-kit modules, use `MODULE_OVERVIEW` as the source of truth. For resolvers that reference custom modules, use the custom module's own documentation.
 
 ## Step 5: Scaffold & Populate
 
-After approval, scaffold using `erp-kit` CLI:
+Scaffold using `erp-kit` CLI:
 
 ```bash
-# Tier 3: Stories
-erp-kit app generate doc story <flow>/<actor>--<story> -p {APP_ROOT}/{APP_NAME}
-
 # Tier 3: Screens
 erp-kit app generate doc screen <screen-name> -p {APP_ROOT}/{APP_NAME}
 
@@ -100,12 +108,6 @@ erp-kit app generate doc resolver <resolver-name> -p {APP_ROOT}/{APP_NAME}
 
 Fill scaffolded docs with details from agent extraction results.
 
-**After creating stories**, replace `- TBD` placeholders in the `## Stories` section of each business flow README with actual links:
-
-```markdown
-- [Story Title](./story/<actor>--<story-name>.md)
-```
-
 **After creating resolvers**, replace `- TBD` placeholders in the `## Resolvers` section of each story with actual links:
 
 ```markdown
@@ -117,7 +119,7 @@ Read-only stories should have `None` under `## Resolvers`.
 ## Step 6: Validate
 
 ```bash
-pnpm run app:doc:check
+erp-kit app check -p {APP_ROOT}
 ```
 
 ## Naming Conventions
@@ -126,11 +128,10 @@ See [erp-kit-app-shared/references/naming-conventions.md](../erp-kit-app-shared/
 
 ## Schema Reference
 
-| Schema         | Tier | Output Path                                          |
-| -------------- | ---- | ---------------------------------------------------- |
-| `story.yml`    | 3    | `docs/business-flow/<flow>/story/<actor>--<name>.md` |
-| `screen.yml`   | 3    | `docs/screen/<name>.md`                              |
-| `resolver.yml` | 4    | `docs/resolver/<name>.md`                            |
+| Schema         | Tier | Output Path               |
+| -------------- | ---- | ------------------------- |
+| `screen.yml`   | 3    | `docs/screen/<name>.md`   |
+| `resolver.yml` | 4    | `docs/resolver/<name>.md` |
 
 ## Common Patterns
 
@@ -144,7 +145,7 @@ See [erp-kit-app-shared/references/naming-conventions.md](../erp-kit-app-shared/
 
 ## Tips
 
-- One business flow typically produces 3-8 stories
+- Stories are created in step 1 (erp-kit-app-1-requirements) — this step consumes them
 - Stories should be completable in a single user session
 - Screens can be shared across multiple stories
 - Prefer built-in queries over custom resolvers for simple list/get operations

package/skills/erp-kit-app-3-plan/references/resolver-extraction.md

@@ -5,13 +5,27 @@
 App: {{APP_NAME}}
 Actor docs: {{ACTOR_DOCS}}
 Business flow docs: {{BUSINESS_FLOW_DOCS}}
+Story docs: {{STORY_DOCS}}
+
+## Available Modules
+
+The following modules are available in erp-kit. Use this to map resolvers to real module commands.
+
+{{MODULE_OVERVIEW}}
+
+To inspect a specific module's commands in detail, run:
+
+```bash
+erp-kit doc module <module-name> command <command-name>
+```
 
 ## Instructions
 
 1. Read ALL actor docs at the paths above
 2. Read ALL business flow docs at the paths above
-3. Identify GraphQL resolvers needed for each business flow
-4. Return results as a structured markdown report
+3. Read ALL story docs at the paths above
+4. Identify GraphQL resolvers needed for each business flow and story, using the module overview and `erp-kit doc module <name> command` for detail
+5. Return results as a structured markdown report
 
 ## Extraction Rules
 
@@ -21,26 +35,13 @@ For each business flow step that modifies data:
 
 1. Identify the operation type (create, update, delete, approve, etc.)
 2. Map to a resolver name using camelCase action-verb convention
-3. Identify the module command the resolver will call
+3. Identify the module command the resolver will call. If no erp-kit module covers the domain, flag it as a module gap.
 4. Extract inputs, outputs, and error scenarios
 
 ### Operation → Resolver Mapping
 
 See [erp-kit-app-shared/references/resolver-classification.md](../../erp-kit-app-shared/references/resolver-classification.md) for the full operation → resolver mapping table and custom vs built-in classification.
 
-### Module Command Mapping
-
-For each resolver, identify which erp-kit module provides the command:
-
-| Resolver Operation | Typical Module        |
-| ------------------ | --------------------- |
-| User invite/roles  | `user-management`     |
-| Supplier CRUD      | `supplier-management` |
-| Document handling  | `document-management` |
-| Task workflows     | `task-management`     |
-| Item CRUD          | `item-management`     |
-| Unit/currency      | `primitives`          |
-
 ### Resolver Content
 
 For each resolver, extract:
@@ -78,12 +79,17 @@ For each resolver:
 
 List entities that only need built-in list/get queries (no custom resolver needed).
 
-### Module Dependencies
+### Module Gaps
+
+List any operations that could not be mapped to an existing erp-kit module. These will require a custom module. For each gap:
 
-Table with columns: Module, Required Commands, Status (exists/missing)
+- **Operation:** what the flow requires
+- **Suggested custom module:** proposed module name and domain
+- **Suggested command:** proposed command name
 
 ### Summary
 
 - Total custom resolvers
 - Total built-in queries
 - Resolvers per module (table)
+- Module gaps (if any)

package/skills/erp-kit-app-3-plan/references/screen-extraction.md

@@ -5,13 +5,28 @@
 App: {{APP_NAME}}
 Actor docs: {{ACTOR_DOCS}}
 Business flow docs: {{BUSINESS_FLOW_DOCS}}
+Story docs: {{STORY_DOCS}}
+
+## Available Modules
+
+The following modules are available in erp-kit. Use this to understand which entities exist and what operations are available.
+
+{{MODULE_OVERVIEW}}
+
+To inspect a specific module's model (domain description, state transitions, invariants, commands), run:
+
+```bash
+erp-kit doc module <module-name> model <model-name>
+```
 
 ## Instructions
 
 1. Read ALL actor docs at the paths above
 2. Read ALL business flow docs at the paths above
-3. Identify screens needed for each business flow
-4. Return results as a structured markdown report
+3. Read ALL story docs at the paths above
+4. Identify screens needed for each business flow and story
+5. For screens that display or edit module entities, use `erp-kit doc module <name> model` to understand the entity's domain
+6. Return results as a structured markdown report
 
 ## Extraction Rules
 
@@ -63,6 +78,7 @@ For each screen:
 
 - **Screen:** `<screen-name>`
 - **Type:** ListView / Form / DetailView
+- **Module source:** which module's model provides the data (if applicable)
 - **Fields/Columns:** bulleted list of fields with types
 - **Actions:** bulleted list of actions
 - **Referenced by stories:** which stories use this screen