@pavp/storywright 1.11.0 → 1.12.0

package/commands/story-generate.md

@@ -15,7 +15,12 @@ Follow the skill's full procedure:
 4. Fill the CORE sections (Title, Summary, User Story, Acceptance Criteria, Definition of Done).
 5. Fill optional sections only if they have real content (drop empty ones).
 6. Run INVEST pre-split test. If count ≥2, show candidate children + ask via `AskUserQuestion` with options: "Yes, split" / "Continue without split" / "No, keep as-is". Never auto-split silently. For other verdicts (NOT A STORY / NEEDS REFINEMENT / RUN A SPIKE) — STOP and hand off accordingly.
-7. Render dual outputs via `jira-wiki-formatter`. Use the `Write` tool to write `story.standard.md` and `story.jira-wiki.md` to `docs/storywright/YYYY-MM-DD-HHmm-<title-slug>/` (current local time, title in kebab-case max 5 words). Also emit both as fenced code blocks in chat. Never ask — always write.
+7. Render three outputs via `jira-wiki-formatter` to `docs/storywright/YYYY-MM-DD-HHmm-<title-slug>/` (current local time, title kebab-case max 5 words). Use the `Write` tool for all files — never ask:
+   - `story.standard.md` — PM-facing CommonMark: observable behavior only, no file paths/imports/component names/CLI commands
+   - `story.jira-wiki.md` — PM-facing Jira wiki markup: same content as standard
+   - `story.dev.md` — dev-facing CommonMark: full technical detail (file paths, imports, Technical Considerations, technical edge cases, DoD with `npm run` commands)
+   - `.storywright-context.json` — resolved session answers: `{"language":"...","persona":"...","naming_pattern":null,"output_folder":"...","resolved_questions":[],"sibling_refs":[]}`
+   Emit `story.standard.md` and `story.jira-wiki.md` as fenced code blocks in chat. Do NOT emit `story.dev.md` in chat.
 8. Non-blocking assumptions remain? Mark inline with `⚠️ Assumed:`. Do NOT emit clarifications.md.
 
 Output in the input language (preserve es/en).

package/commands/story-refine.md

@@ -16,5 +16,10 @@ Follow the skill's procedure:
 4. Fill missing/weak sections via component skills. Preserve original wording where good.
 5. Append a "Refinement log" at the end listing what changed.
 6. Run INVEST pre-split test. If count ≥2, show candidate children + ask via `AskUserQuestion` with options: "Yes, split" / "Continue without split" / "No, keep as-is". Never auto-split silently.
-7. Render dual outputs via `jira-wiki-formatter`. Use the `Write` tool to write `story.standard.md` and `story.jira-wiki.md` to `docs/storywright/YYYY-MM-DD-HHmm-<title-slug>/` (current local time, title in kebab-case max 5 words). Also emit both as fenced code blocks in chat. Never ask — always write.
+7. Render three outputs via `jira-wiki-formatter` to `docs/storywright/YYYY-MM-DD-HHmm-<title-slug>/` (current local time, title kebab-case max 5 words). Use the `Write` tool for all files — never ask:
+   - `story.standard.md` — PM-facing CommonMark: observable behavior only, no file paths/imports/component names/CLI commands
+   - `story.jira-wiki.md` — PM-facing Jira wiki markup: same content as standard
+   - `story.dev.md` — dev-facing CommonMark: full technical detail (file paths, imports, Technical Considerations, technical edge cases, DoD with `npm run` commands)
+   - `.storywright-context.json` — resolved session answers: `{"language":"...","persona":"...","naming_pattern":null,"output_folder":"...","resolved_questions":[],"sibling_refs":[]}`
+   Emit `story.standard.md` and `story.jira-wiki.md` as fenced code blocks in chat. Do NOT emit `story.dev.md` in chat.
 8. Non-blocking assumptions remain? Mark inline with `⚠️ Assumed:`. Do NOT emit clarifications.md.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pavp/storywright",
-  "version": "1.11.0",
+  "version": "1.12.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/jira-wiki-formatter/SKILL.md

@@ -1,14 +1,15 @@
 ---
 name: jira-wiki-formatter
-description: Render a story into both Jira wiki markup and standard CommonMark Markdown. Outputs two artifacts so the same story is copy-pasteable into Jira and into any MD-aware tool.
+description: Render a story into three files: story.standard.md and story.jira-wiki.md (PM-facing, no technical detail) plus story.dev.md (dev-facing, full technical detail).
 trigger: "internal use by story-* skills"
-intent: Component skill that takes a structured story (all sections drafted) and produces two output files following the templates in story-generate/templates.
-version: 1.0.0
+intent: Component skill that takes a structured story and produces three output files following the templates in story-generate/templates.
+version: 2.0.0
 inputs:
   - structured-story
 outputs:
-  - story.jira-wiki.md
   - story.standard.md
+  - story.jira-wiki.md
+  - story.dev.md
 ---
 
 ## Purpose
@@ -25,7 +26,21 @@ Final step in `story-generate` and `story-refine`. Always last.
 
 ## Application (step-by-step)
 
-1. Render `story.jira-wiki.md` using Jira's wiki markup:
+## Audience separation — THREE files
+
+| File | Audience | Technical detail |
+|---|---|---|
+| `story.standard.md` | PM, stakeholders | ❌ None — no file paths, no imports, no component names, no `npm run X` in DoD |
+| `story.jira-wiki.md` | PM → Jira paste | ❌ None — same content as standard, Jira markup |
+| `story.dev.md` | Developer | ✅ Full — file paths, imports, Technical Considerations, technical edge cases, full DoD with commands |
+
+**What is "technical":** file paths, import statements, component/hook names, API method names, CLI commands (`npm run test`), null/undefined checks, browser API constraints (HTTPS, permissions), specific library flags.
+
+**ACs in PM files must describe observable behavior only.** "A copy icon appears next to the email field and clicking it copies the value" — not "ContentCopyOutlinedIcon is rendered next to the email Typography block and calls navigator.clipboard.writeText()".
+
+---
+
+1. Render `story.jira-wiki.md` (PM-facing) using Jira's wiki markup:
    - Headings: `h1. `, `h2. `, `h3. `
    - Bold: `*text*`
    - Italic: `_text_`
@@ -33,7 +48,8 @@ Final step in `story-generate` and `story-refine`. Always last.
    - Lists: `* item`, `# item` (numbered)
    - Tables: `||header||header||` then `|cell|cell|`
    - Panels for callouts: `{panel:title=⚠️ Assumed}…{panel}`
-2. Render `story.standard.md` using CommonMark:
+   - Strip all technical detail (see audience table above)
+2. Render `story.standard.md` (PM-facing) using CommonMark:
    - Headings: `##`, `###`
    - Bold: `**text**`
    - Italic: `*text*`
@@ -41,29 +57,28 @@ Final step in `story-generate` and `story-refine`. Always last.
    - Lists: `- item`, `1. item`
    - Tables: standard pipe tables
    - Callouts: `> ⚠️ **Assumed:** …`
-3. Section model = **core + optional**.
+   - Strip all technical detail (see audience table above)
+3. Render `story.dev.md` (dev-facing) using CommonMark:
+   - Same structure as `story.standard.md` PLUS:
+   - Technical Considerations section (file paths, imports, API calls)
+   - Edge Cases section (null checks, error states, browser constraints)
+   - DoD includes CLI commands and file-level criteria
+   - Refinement log includes technical changes
+4. Section model for PM files = **core + optional (non-technical)**.
 
    **Core (always emit, in this order):**
    1. Title
-   2. Summary
-   3. User Story (As a / I want to / so that)
-   4. Acceptance Criteria
-   5. Definition of Done
-
-   **Optional (emit only if non-empty, in this order, after a separator):**
-   6. Contexto
-   7. Business Goal
-   8. Scope
-   9. Out of Scope
-   10. Business Rules
-   11. Technical Considerations
-   12. Dependencies
-   13. Risks
-   14. Analytics
-   15. Edge Cases
-
-4. **Drop any section with no real content.** An empty heading is noise. A story with only the 5 core sections is a valid output.
-5. Emit both as fenced code blocks in the chat so the user can copy them. File persistence is handled by the calling skill via the `Write` tool.
+   2. User Story (As a / I want to / so that)
+   3. Acceptance Criteria (observable behavior only)
+   4. Definition of Done (acceptance criteria only, no commands)
+
+   **Optional PM sections (emit only if non-empty):**
+   5. Business Goal
+   6. Scope / Out of Scope
+   7. Business Rules
+
+5. **Drop any section with no real content.** An empty heading is noise.
+6. Emit `story.standard.md` and `story.jira-wiki.md` as fenced code blocks in chat (PM-facing). Do NOT emit `story.dev.md` in chat — write to disk only. File persistence is handled by the calling skill via the `Write` tool.
 
 ## Examples
 

package/skills/_components/storywright-base/SKILL.md

@@ -228,10 +228,13 @@ NOTHING else. No NFR block. No Edge Cases enumeration. No Dependencies prose. No
 
 10. **Render** via `[[jira-wiki-formatter]]`.
     - Derive the output folder: `docs/storywright/YYYY-MM-DD-HHmm-<title-slug>/` where `YYYY-MM-DD-HHmm` is the current local date+time and `<title-slug>` is the story title in kebab-case (max 5 words, drop articles/prepositions).
-    - Use the `Write` tool to persist `story.standard.md` and `story.jira-wiki.md` to that folder (create it if it does not exist).
-    - Also emit both as fenced code blocks in chat.
+    - Use the `Write` tool to persist three files to that folder (create it if it does not exist):
+      - `story.standard.md` — PM-facing CommonMark, no technical detail
+      - `story.jira-wiki.md` — PM-facing Jira wiki markup, no technical detail
+      - `story.dev.md` — dev-facing CommonMark, full technical detail (file paths, imports, technical edge cases, full DoD with commands)
+    - Emit `story.standard.md` and `story.jira-wiki.md` as fenced code blocks in chat. Do NOT emit `story.dev.md` in chat.
     - Write `.storywright-context.json` to the same folder.
-    - No other files. Never ask whether to save — always write.
+    - Never ask whether to save — always write all four files.
 
 11. **Log** ≤3 bullets (≤5 if SPLIT) appended at story end. Log type label is host-specific (Generation / Refinement / Split).
 

package/skills/story-generate/SKILL.md

@@ -11,6 +11,7 @@ inputs:
 outputs:
   - story.standard.md
   - story.jira-wiki.md
+  - story.dev.md
   - .storywright-context.json
 composes:
   - _components/storywright-base

package/skills/story-generate/templates/story.dev.md

@@ -0,0 +1,27 @@
+# {{Title}} — Dev Notes
+
+> This file is the developer supplement to `story.standard.md`.
+> It contains all technical detail stripped from the PM-facing outputs.
+
+## Technical Considerations
+
+- {{file path or component name}} — {{what changes}}
+- {{import to add/remove}}
+- {{API call / SDK / feature flag / data model note}}
+
+## Edge Cases & Error States
+
+- **{{axis}}:** {{technical behavior — null checks, error states, race conditions, HTTPS requirements}}
+
+## Definition of Done
+
+- [ ] {{business criterion}}
+- [ ] {{test command: npm run test / npm run lint}}
+- [ ] {{file-level criterion: file X updated, import Y removed}}
+
+---
+
+<!-- Refinement Log — full version including technical changes -->
+
+*Refinement log*
+- {{change}} — {{reason}}

package/skills/story-refine/SKILL.md

@@ -11,6 +11,7 @@ inputs:
 outputs:
   - story.standard.md
   - story.jira-wiki.md
+  - story.dev.md
   - .storywright-context.json
 composes:
   - _components/storywright-base