@pavp/storywright 1.8.0 → 1.8.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. package/commands/story-generate.md +1 -1
  2. package/commands/story-refine.md +1 -1
  3. package/package.json +1 -1
  4. package/skills/_components/jira-wiki-formatter/SKILL.md +1 -1
package/commands/story-generate.md CHANGED
@@ -14,7 +14,7 @@ Follow the skill's full procedure:
14
14
  3. Run gap check via `clarification-questions` component. Ask at most 3 critical questions if anything is blocking.
15
15
  4. Fill the CORE sections (Title, Summary, User Story, Acceptance Criteria, Definition of Done).
16
16
  5. Fill optional sections only if they have real content (drop empty ones).
17
- 6. Run INVEST self-check. If NOT A STORY / NEEDS REFINEMENT / RUN A SPIKE / SPLIT RECOMMENDED — STOP and hand off accordingly.
17
+ 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.
18
18
  7. Render dual outputs: `story.jira-wiki.md` (Jira wiki markup) and `story.standard.md` (CommonMark).
19
19
  8. If clarifications remain, emit `clarifications.md` and mark the story DRAFT.
20
20
 
package/commands/story-refine.md CHANGED
@@ -15,6 +15,6 @@ Follow the skill's procedure:
15
15
  3. Detect language and preserve it in output.
16
16
  4. Fill missing/weak sections via component skills. Preserve original wording where good.
17
17
  5. Append a "Refinement log" at the end listing what changed.
18
- 6. Run INVEST. If verdict is `SPLIT RECOMMENDED`, stop and recommend `/story-split` instead.
18
+ 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.
19
19
  7. Render dual outputs via `jira-wiki-formatter`.
20
20
  8. Emit `clarifications.md` if assumptions remain unresolved.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@pavp/storywright",
3
- "version": "1.8.0",
3
+ "version": "1.8.2",
4
4
  "description": "PM Skills pack for Claude Code — turn ambiguous inputs (prompts, screenshots, Figma links) into Jira-ready user stories.",
5
5
  "keywords": [
6
6
  "claude",
package/skills/_components/jira-wiki-formatter/SKILL.md CHANGED
@@ -63,7 +63,7 @@ Final step in `story-generate` and `story-refine`. Always last.
63
63
  15. Edge Cases
64
64
 
65
65
  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.
66
- 5. Always write `story.standard.md` and `story.jira-wiki.md` to disk. Also emit both as fenced code blocks in the chat so the user can copy them. Never ask whether to save — always save.
66
+ 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.
67
67
 
68
68
  ## Examples
69
69