@pavp/storywright 1.8.1 → 1.8.3

package/commands/story-generate.md

@@ -14,7 +14,7 @@ Follow the skill's full procedure:
 3. Run gap check via `clarification-questions` component. Ask at most 3 critical questions if anything is blocking.
 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 self-check. If NOT A STORY / NEEDS REFINEMENT / RUN A SPIKE / SPLIT RECOMMENDED — STOP and hand off accordingly.
+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: `story.jira-wiki.md` (Jira wiki markup) and `story.standard.md` (CommonMark).
 8. If clarifications remain, emit `clarifications.md` and mark the story DRAFT.
 

package/commands/story-refine.md

@@ -15,6 +15,6 @@ Follow the skill's procedure:
 3. Detect language and preserve it in output.
 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. If verdict is `SPLIT RECOMMENDED`, stop and recommend `/story-split` instead.
+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`.
 8. Emit `clarifications.md` if assumptions remain unresolved.

package/package.json

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