@pavp/storywright 1.9.0 → 1.10.1

package/commands/story-generate.md

@@ -15,7 +15,7 @@ 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: `story.jira-wiki.md` (Jira wiki markup) and `story.standard.md` (CommonMark).
-8. If clarifications remain, emit `clarifications.md` and mark the story DRAFT.
+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.
+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,5 @@ 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`.
-8. Emit `clarifications.md` if assumptions remain unresolved.
+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.
+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.9.0",
+  "version": "1.10.1",
   "description": "PM Skills pack for Claude Code — turn ambiguous inputs (prompts, screenshots, Figma links) into Jira-ready user stories.",
   "keywords": [
     "claude",

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

@@ -226,7 +226,12 @@ 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]]`. 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.
+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.
+    - Write `.storywright-context.json` to the same folder.
+    - 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).