@pavp/storywright 1.6.1 → 1.6.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pavp/storywright",
-  "version": "1.6.1",
+  "version": "1.6.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/clarification-questions/SKILL.md

@@ -43,7 +43,7 @@ Invoked by `story-generate`, `story-refine`, `story-split`, and `story-from-figm
 4. For `BLOCKING`, draft questions. Limit to **3 questions max per round**. Prefer multiple-choice or yes/no.
 5. Order by impact: scope > behavior > data > UX detail.
 6. Emit as a Markdown block titled `### Clarifying Questions` with numbered list.
-7. If no questions remain, emit nothing.
+7. If no questions remain, emit nothing — no summary, no "Clarification resolved", no offer to save. Proceed directly to the next step.
 
 ## Examples
 

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. Emit both as fenced code blocks in the chat (so user can copy), and offer to save to disk when running from CLI.
+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.
 
 ## Examples
 
@@ -119,6 +119,8 @@ Permitir a usuarios autenticarse mediante OAuth con Google.
 - Forgetting that Jira's `{code}` block doesn't support all languages — fall back to `{noformat}` for plain text.
 - Emoji in Jira: works in cloud, often mangled in older self-hosted. Keep emojis to non-critical decoration.
 - Empty headings. Drop.
+- Wrong heading levels: CommonMark output uses `#` (H1) for title, `##` (H2) for sections. Jira uses `h2.` for title, `h3.` for sections. The canonical block in `[[storywright-base]]` uses `###`/`####` as taxonomy shorthand only — do not copy those levels into the rendered artifact.
+- Emitting INVEST as a section: INVEST is a process step. Its verdict belongs in the log line only (`INVEST Verdict: READY`), never as a standalone section in the output file.
 
 ## References
 

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

@@ -24,7 +24,7 @@ If you are reading this through a top-level skill, treat every rule below as non
 
 ## Hard rules (v2.2 — apply to all top-level storywright skills)
 
-1. **Terminal-only clarifications.** Never write any sidecar question file (no `clarifications.md`, no `questions.md`, nothing). All gap questions go through `AskUserQuestion`, batched ≤4 per call. Non-blocking gaps → mark `⚠️ Assumed: <text>` inline in the story body — do not ask.
+1. **Terminal-only clarifications.** Never write any sidecar question file (no `clarifications.md`, no `questions.md`, nothing). All gap questions go through `AskUserQuestion`, batched ≤4 per call. Non-blocking gaps → mark `⚠️ Assumed: <text>` inline in the story body — do not ask. Do NOT announce the absence of a clarifications file ("Clarification resolved", "no clarifications.md needed", or any equivalent). Silence = no questions. Proceed directly.
 
 2. **Cohn + Gherkin canonical.** Every story (or child story) has:
    - ONE Use Case block (`As a / I want to / so that`).
@@ -161,6 +161,8 @@ Mechanical counter. Apply the table — do NOT eyeball:
 
 ## Canonical output shape (this is the WHOLE story — no exceptions)
 
+> **Note:** This block shows the *section taxonomy and rules* — not heading levels or exact markup. The rendered artifact must follow the `story-generate/templates/` files exactly: `#` for title, `##` for sections (CommonMark) or `h2.`/`h3.` (Jira wiki). INVEST is a **process step** — it informs the Verdict line in the log but is NOT emitted as a section in the output artifact.
+
 ```markdown
 ### [Title]
 
@@ -187,16 +189,12 @@ Mechanical counter. Apply the table — do NOT eyeball:
 - [link or path]
 - visual notes: [...]
 
-#### INVEST
-- I — <PASS | PARTIAL · depends on <Ci>>
-- N/V/E/S/T — one line each, evidence-based.
-- **Verdict:** READY | READY (after <Ci> builds) | SPLIT RECOMMENDED | NEEDS REFINEMENT | NOT A STORY | WEAK·merge-upstream-candidate
-
 #### <Generation | Refinement | Split> log (≤3 lines; ≤5 if SPLIT verdict)
-- ...
+- INVEST Verdict: <READY | SPLIT RECOMMENDED | NEEDS REFINEMENT | NOT A STORY>
+- [other changes]
 ```
 
-NOTHING else. No NFR block. No Edge Cases enumeration. No Dependencies prose. No Assumptions block (assumptions get `⚠️ Assumed` inline or are resolved via `AskUserQuestion`).
+NOTHING else. No NFR block. No Edge Cases enumeration. No Dependencies prose. No Assumptions block (assumptions get `⚠️ Assumed` inline or are resolved via `AskUserQuestion`). No standalone INVEST section — verdict belongs in the log only.
 
 ## Application (step-by-step — every skill follows this skeleton)
 
@@ -248,6 +246,8 @@ Everything else is identical and lives in this base.
 ## Common Pitfalls (all skills)
 
 - Writing any sidecar question file (clarifications.md, questions.md, etc).
+- Announcing "Clarification resolved" or "no clarifications.md needed" instead of proceeding silently.
+- Offering to save a clarifications file to disk after resolving gaps.
 - Skipping rule 1 (terminal-only) "because the user is async".
 - Eyeballing outcome counts instead of running the mechanical table.
 - Renumbering ACs the team may already reference externally.