@pavp/storywright 1.0.3 → 1.2.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pavp/storywright",
-  "version": "1.0.3",
+  "version": "1.2.0",
   "description": "PM Skills pack for Claude Code — turn ambiguous inputs (prompts, screenshots, Figma links) into Jira-ready user stories.",
   "keywords": [
     "claude",

package/skills/_components/clarification-questions/SKILL.md

@@ -37,6 +37,7 @@ Invoked by `story-generate`, `story-refine`, `story-split`, and `story-from-figm
    - **Data inputs** (auth scope, identifiers, format)
    - **Constraints** (platform, accessibility, locale, SLA)
    - **Out-of-scope assumptions**
+   - **Multi-source conflicts** (when text + image + Figma are all provided): explicit disagreement between sources MUST be surfaced. Examples: text says "Google only" but Figma shows multiple providers; text mentions 1 flow but Figma shows 3; image shows error state not mentioned in text. Never silently pick a winner.
 2. For each axis, mark one of: ANSWERED · INFERRABLE · BLOCKING.
 3. Drop `ANSWERED`. For `INFERRABLE`, do NOT ask — mark assumption in the story output with `> ⚠️ Assumed:`.
 4. For `BLOCKING`, draft questions. Limit to **3 questions max per round**. Prefer multiple-choice or yes/no.

package/skills/story-from-figma/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: story-from-figma
 description: Generate user stories from a Figma file or frame URL. Uses an MCP Figma server to enumerate frames, components, navigation, and states; falls back to asking for screenshots if MCP is unavailable.
-trigger: "story from figma | generate from figma | analizar figma | https://www.figma.com/"
+trigger: "/story-from-figma | story from figma | generate from figma | analizar figma | https://www.figma.com/"
 intent: Multimodal entrypoint skill. Inspects a Figma design, infers user flows and screens, and produces one or more stories via story-generate.
 version: 1.0.0
 inputs:
@@ -47,6 +47,14 @@ A Figma file usually represents N screens / N flows. This skill maps that visual
    - Ask the user to either (a) install an MCP Figma server, (b) export the relevant frames as PNGs and drop them in chat, or (c) paste a textual description of the flows.
    - Continue under the chosen fallback. The rest of the skill works with screenshots via Claude vision.
 
+### Phase 0.5 — Detect companion inputs
+
+Before extracting from Figma, check whether the user attached:
+- **Accompanying text** (goal, story draft, constraints) — treat as canonical for `User Story / Scope / Business Goal`. Figma is canonical for `Components / States / Flows`.
+- **Reference screenshots** — usually redundant when Figma is available; use only if Figma frames are missing states the screenshots show.
+
+If text + Figma both describe the same flow but disagree (e.g., text says "single page form", Figma shows multi-step wizard), **surface the conflict** in clarifications and ask before drafting. Do NOT silently pick a winner. See `[[story-generate]]` "Mixed inputs" section for source priority.
+
 ### Phase 1 — Inventory
 
 1. List pages in the file (if MCP allows).

package/skills/story-generate/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: story-generate
 description: Transform an ambiguous prompt, half-baked story, screenshot, or Figma link into a Jira-ready user story with acceptance criteria, DoD, edge cases, and risks. Ask only critical clarifying questions.
-trigger: "generate a user story | write a user story | turn this into a story | crear historia de usuario"
+trigger: "/story-generate | generate a user story | write a user story | turn this into a story | crear historia de usuario"
 intent: Top-level orchestrator skill that drives the full story generation flow by composing component skills.
 version: 1.0.0
 inputs:
@@ -49,9 +49,37 @@ Use vision. Extract:
 ### Figma links
 If MCP Figma is available (see `[[story-from-figma]]`), use it to enumerate frames, components, navigation. If not, fall back to asking the user to drop screenshots.
 
+### Mixed inputs (text + image + Figma)
+
+The skill is designed to **fuse multiple sources** in a single invocation. Common pairings:
+
+- **Text + screenshot** — text states the goal, image shows the proposed UI. Use text for `User Story / Goal / Scope`, image for `Components / States / Edge cases / UX flow`.
+- **Text + Figma link** — text gives intent, Figma gives implementation surface. Use text for `User Story / Business goal`, Figma for `Technical considerations / Edge cases / Components / Multi-screen flows`.
+- **Text + image + Figma** — full triangulation. Highest fidelity; also highest chance of conflict.
+
+**Source priority (when sources disagree):**
+
+| Section | Primary | Secondary | Tertiary |
+|---|---|---|---|
+| User Story / Goal | Text | Figma (frame titles, callouts) | Image |
+| Business Rules / Scope | Text | Figma | Image |
+| UI Components / States | Figma | Image | Text |
+| Edge Cases | Figma + Image (states shown) | Text | — |
+| Technical Considerations | Figma (component naming, design system refs) | Text | Image |
+| Acceptance Criteria | Triangulate all three | — | — |
+
+**Conflict handling:**
+
+1. **Detect the conflict explicitly.** Example: text says "Google only" but Figma shows Google + Facebook buttons.
+2. **Do NOT silently pick a winner.** Surface the conflict in `clarifications.md` as a BLOCKING question: *"Text says X but design shows Y — which is canonical?"*
+3. **If the user is in-session, ask immediately** before drafting. If running batch, mark the story `DRAFT` and write both options in scope/out-of-scope with `> ⚠️ Conflict:` annotation.
+4. **Scope coverage check:** if Figma shows N flows but text describes 1, ask whether to (a) generate 1 story bounded to text, (b) generate N stories from Figma, or (c) generate 1 story + flag remaining flows as roadmap.
+
 ## Application (step-by-step)
 
-1. **Detect input type** (text | image | figma-link | mixed). Branch accordingly.
+1. **Detect input types present** — text, image, figma-link, or any combination. Branch accordingly:
+   - **Single source** → process as before.
+   - **Mixed sources** → run the "Mixed inputs" protocol above, including source-priority lookup and explicit conflict detection BEFORE drafting.
 2. **Intake gap check** — invoke `[[clarification-questions]]`. If it returns BLOCKING questions, **ask first** before drafting.
 3. **Detect language** of input (es | en | other). Output in the input language.
 4. **Draft skeleton** of the structured story (all 15 sections from the template).

package/skills/story-refine/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: story-refine
 description: Audit an existing user story for gaps and fill them in place. Surfaces missing AC, DoD, edge cases, risks; asks clarifications only for blocking unknowns. Returns dual-format refined story.
-trigger: "refine this story | improve this story | refinar historia | this story is incomplete"
+trigger: "/story-refine | refine this story | improve this story | refinar historia | this story is incomplete"
 intent: Refinement skill for stories that already exist but are incomplete or weakly specified. Composes the same component skills as story-generate but skips the drafting step.
 version: 1.0.0
 inputs:

package/skills/story-split/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: story-split
 description: Detect when a story is too big to ship in one sprint and propose an INVEST-driven split into an epic with sub-stories. Never auto-splits — always proposes, then waits for user confirmation.
-trigger: "split this story | divide this story | dividir historia | this is too big"
+trigger: "/story-split | split this story | divide this story | dividir historia | this is too big"
 intent: Splitting skill that uses the INVEST failure reasons (from invest-checklist) as the rationale for decomposition. Produces an epic skeleton plus N child story stubs, ready to feed back into story-generate.
 version: 1.0.0
 inputs: