projectstore-claude 0.30.12 → 0.30.13

package/node_modules/projectstore/.claude-plugin/marketplace.json

@@ -12,7 +12,7 @@
       "name": "projectstore",
       "displayName": "projectstore",
       "description": "📚 Your agent runs the project through a verified loop: task → artifact (ADR · spec · epic · story) → adversarial critic → backlog → planner → reviewer → done. Plain markdown in an Obsidian-friendly vault, every write approved by you — and any model can pick the project up tomorrow.",
-      "version": "0.30.12",
+      "version": "0.30.13",
       "author": {
         "name": "Evgenii Konev",
         "email": "ekonev@smartandpoint.com",

package/node_modules/projectstore/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "projectstore",
   "displayName": "projectstore",
-  "version": "0.30.12",
+  "version": "0.30.13",
   "description": "Your agent runs the project through a verified loop: task → artifact (ADR / spec / epic / story) → adversarial critic → backlog → planner → reviewer → done. Plain markdown in git — any model can pick the project up tomorrow.",
   "author": {
     "name": "Evgenii Konev @ SmartAndPoint",

package/node_modules/projectstore/agents/planner.md

@@ -85,8 +85,17 @@ generic best practice — cite the real files and patterns you found.
 8. **Proposed `code_refs`** — the paths/globs this epic (and story) will own once
    implemented, ready for `/projectstore:codemap set`. You PROPOSE; the command
    writes after approval.
+9. **Open questions** — at most five decisions the user must make that the
+   code and the vault cannot answer, the one that changes the plan most
+   first. One per line:
+   `Q<n>. <the question> Options: (a) … (b) … Recommend (b): <why>`, with two to four options. The
+   recommendation is one of the options, so it can be recorded as the answer
+   when the user skips the question. "None" is the normal case. With more than
+   five, return five, say how many you left out, and say the story is
+   probably too big: suggest how to split it. You ask the user nothing; the
+   plan step puts these to the user in one round.
 
 Rules: be concrete and cite real paths / symbols; if the task is ambiguous or has
-two plausible homes, say so and recommend one with the tradeoff. No code
+two plausible homes, say so in Open questions (item 9) and recommend one with the tradeoff. No code
 generation beyond tiny illustrative snippets. You are read-only — never write
 code or vault files.

package/node_modules/projectstore/commands/story.md

@@ -100,11 +100,32 @@ the two cannot collide).
    `plan_updated_at` / `closed_at` — stamped unconditionally; the
    `lifecycle_gates` key gates checks, never data).
 
+2a. **(plan only) Open questions, one round.** Before writing the plan,
+   collect the open questions: the planner's "Open questions" when it ran,
+   else your own; do not start the planner here. Keep only decisions the
+   user must make; skip what the conversation, or an earlier
+   `### Clarifications` in this plan, already settled. None is the normal
+   case: then ask nothing and write nothing. Keep at most five, the one that
+   changes the plan most first; with more, keep five, say how many were
+   dropped, and suggest splitting the story; when the planner says it left questions out, say so in the same round, with its split suggestion. Each question has two to four
+   options and one recommended option. Put them to the user in one round:
+   one call of AskUserQuestion for up to four questions; with five, or where
+   the harness has no question tool, one plain-text message with the
+   questions numbered. Ask once per gate run: the Edit in step 4 and the
+   re-check in step 5 never ask again. A skipped question, or every question
+   of a dismissed call, takes its recommendation, marked `(assumed)`. Record
+   the round under `### Clarifications`, last in the plan: a line with
+   today's date, then one bullet per question with its answer; a later plan
+   run appends its own dated line to the same subsection. An answer that changes a
+   contract of the covering spec says which one, and the spec is amended
+   the way it records its other amendments before the code is written.
+
 3. **Fill the section content** in the returned `content` before preview:
    - `plan` — write the Implementation Plan. When the story's `specs:` names a
      covering spec, the plan is a THIN ROUTE through that spec's behavioral
      contracts: which contracts, in what order, which files. Consult the
-     planner agent's output if one ran. Do not restate the spec.
+     planner agent's output if one ran. Do not restate the spec. End the plan
+     with the step 2a round, when there was one.
    - `close` — write the Final Summary (what changed / why / tests executed /
      risks & follow-ups), and update the Acceptance Criteria checkboxes with
      evidence suffixes: `- [x] <criterion> — evidence: <test | command | file:line>`.

package/node_modules/projectstore/package.json

@@ -1,6 +1,6 @@
 {
   "name": "projectstore",
-  "version": "0.30.12",
+  "version": "0.30.13",
   "description": "Your agent runs the project through a verified loop: task → artifact (ADR / spec / epic / story) → adversarial critic → backlog → planner → reviewer → done. Plain markdown in git — any model can pick the project up tomorrow.",
   "keywords": [
     "project-management",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "projectstore-claude",
-  "version": "0.30.12",
+  "version": "0.30.13",
   "description": "projectstore for Claude Code: the core pinned and bundled, the harness fixed. A release artifact; the way in is npx projectstore setup",
   "keywords": [
     "projectstore",
@@ -37,7 +37,7 @@
     "README.md"
   ],
   "dependencies": {
-    "projectstore": "=0.30.12"
+    "projectstore": "=0.30.13"
   },
   "bundleDependencies": [
     "projectstore"