@pavp/storywright 1.8.2 → 1.9.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pavp/storywright",
-  "version": "1.8.2",
+  "version": "1.9.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

@@ -63,7 +63,7 @@ Final step in `story-generate` and `story-refine`. Always last.
    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. Always write `story.standard.md` and `story.jira-wiki.md` to disk using the `Write` tool (Claude Code). Also emit both as fenced code blocks in the chat so the user can copy them. Never ask whether to save — always save. If `Write` tool is unavailable, emit in chat only and note the limitation.
+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.
 
 ## Examples
 

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

@@ -226,7 +226,7 @@ NOTHING else. No NFR block. No Edge Cases enumeration. No Dependencies prose. No
    - `NEEDS REFINEMENT` → iterate failing dimension, max 1 cycle, then STOP.
    - `NOT A STORY` → tell user it's a tech task and stop.
 
-10. **Render** via `[[jira-wiki-formatter]]`. Files: `story.standard.md` + `story.jira-wiki.md`. Plus `.storywright-context.json`. No other files.
+10. **Render** via `[[jira-wiki-formatter]]`. Use the `Write` tool to persist `story.standard.md` and `story.jira-wiki.md` to `docs/stories/` under the current working directory (create the folder if it does not exist). Also emit both as fenced code blocks in chat. Plus write `.storywright-context.json` to `docs/stories/`. No other files. Never ask whether to save — always write.
 
 11. **Log** ≤3 bullets (≤5 if SPLIT) appended at story end. Log type label is host-specific (Generation / Refinement / Split).