@avesta-hq/prevention 0.6.0-pre.21 → 0.6.0-pre.22

package/.claude/commands/avesta-init.md

@@ -16,4 +16,4 @@ If `success` is false: Display the `error` to the user and stop.
 Show the result to the user:
 - Project type
 - Whether it needs scaffolding (`needs_scaffold`)
-- Next step from `next_step` field: if "scaffold" → tell user to run `/avesta-scaffold`, if "vision" → tell user to run `/avesta-vision`
+- Next step: tell user to run `/avesta-vision` to define what they're building.

package/.claude/commands/avesta-scaffold.md

@@ -7,21 +7,18 @@ Call `avesta_dispatch(user_input="$ARGUMENTS", current_command="scaffold")`.
 
 If `gate_check.allowed` is false: Display the `error_message` to the user and stop.
 
-## Feature name
-
-Use `AskUserQuestion` to ask: "What is the main thing your app does? This becomes your first feature folder (e.g. 'todo', 'identity', 'catalog'). Use a short, lowercase, singular noun."
-
-Wait for the answer. Store it as `feature_name`.
-
 ## Spawn
 
-Use the **Agent tool** with `subagent_type: "avesta-scaffolder"` and the following prompt — substituting actual values for `[project_type]` and `[feature_name]`:
+Do NOT ask the user for a feature name. The scaffolder agent derives it automatically from `.avesta/docs/user-story-map/story-map.html` (rendered by `/avesta-shape` Step 6) — first MVP story text, falling back to the product name from `<h1><em>` or `<title>`.
+
+Use the **Agent tool** with `subagent_type: "avesta-scaffolder"` and the following prompt — substituting the actual value for `[project_type]`:
 
 ```
 IMPORTANT: Your FIRST action must be to call avesta_get_prompt("scaffolder") with context {project_type: "[project_type from dispatch]"} to load your full instructions. Then call avesta_load_skill for EVERY skill in skills_to_load before doing anything else. Read the checkpoint manifest via avesta_get_checkpoint_manifest() and resume from the next un-advanced checkpoint — do not re-ask questions whose answers were already captured.
 
+When you call avesta_scaffold, omit the feature_name parameter — the tool resolves it from .avesta/docs/user-story-map/story-map.html and returns the resolved value in feature_name with feature_name_source. If the tool errors because the HTML is missing, surface the error and tell the user to run /avesta-shape to completion before scaffolding. Do NOT ask the user for a feature name and do NOT volunteer example names.
+
 User request: $ARGUMENTS
-Feature name: [feature_name]
 Dispatch result: [full dispatch response]
 ```
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@avesta-hq/prevention",
-  "version": "0.6.0-pre.21",
+  "version": "0.6.0-pre.22",
   "description": "XP/CD development agent commands for Claude Code - achieve Elite DORA metrics through disciplined TDD and Continuous Delivery practices",
   "keywords": [
     "claude-code",