create-agentic-starter 0.1.13 → 0.1.15

package/dist/templates/commands/architecture.md

@@ -20,7 +20,7 @@ Read:
 8. Ask only the minimum blocking questions.
 9. If the user directly asks for a downstream deliverable and the architecture context is already sufficient, let them continue there instead of forcing this step to repeat.
 
-When the architecture is strong enough, tell the user the available next options:
+When the architecture is strong enough, tell the user the available next options, and also make it clear they can ask for something else by saying what they want to do next.
 
 - `@.agentic/commands/create-brd.md`
 - `@.agentic/commands/create-proposal.md`

package/dist/templates/commands/create-brd.md

@@ -25,6 +25,6 @@ Read:
 13. If critical information is missing, ask only the minimum blocking questions and keep improving the BRD draft instead of routing yet.
 14. If the user explicitly asked for this BRD work, continue it directly using the existing workspace context instead of routing them backward.
 
-When the BRD is solid enough to define functional requirements, tell the user:
+When the BRD is solid enough to define functional requirements, recommend the next command and also make it clear the user can say what they want to do now:
 
 `Next type @.agentic/commands/create-frd.md`

package/dist/templates/commands/create-estimate.md

@@ -27,6 +27,6 @@ Read:
 14. Ask only the minimum blocking questions.
 15. If the user explicitly asked for this estimate work, continue it directly using the existing workspace context instead of routing them backward.
 
-When the estimate is strong enough for proposal drafting, tell the user:
+When the estimate is strong enough for proposal drafting, recommend the next command and also make it clear the user can say what they want to do now:
 
 `Next type @.agentic/commands/create-proposal.md`

package/dist/templates/commands/create-frd.md

@@ -25,6 +25,6 @@ Read:
 12. Ask only the minimum blocking questions.
 13. If the user explicitly asked for this FRD work, continue it directly using the existing workspace context instead of routing them backward.
 
-When the FRD is strong enough for estimation, tell the user:
+When the FRD is strong enough for estimation, recommend the next command and also make it clear the user can say what they want to do now:
 
 `Next type @.agentic/commands/create-estimate.md`

package/dist/templates/commands/create-plan.md

@@ -30,7 +30,7 @@ Read:
 14. If planning inputs are missing, ask focused questions and keep refining instead of routing.
 15. If the user explicitly asked for this plan work, continue it directly using the existing workspace context instead of routing them backward.
 
-When the plan is complete enough, tell the user the available next options:
+When the plan is complete enough, tell the user the available next options, and also make it clear they can ask for something else by saying what they want to do next.
 
 - `@.agentic/commands/architecture.md`
 - `@.agentic/commands/create-tasks.md`

package/dist/templates/commands/create-tasks.md

@@ -28,7 +28,7 @@ Read:
 13. If execution detail is missing, ask focused questions and keep refining instead of routing.
 14. If the user explicitly asked for this task planning work, continue it directly using the existing workspace context instead of routing them backward.
 
-When the tasks are complete enough, tell the user the available next options:
+When the tasks are complete enough, tell the user the available next options, and also make it clear they can ask for something else by saying what they want to do next.
 
 - `@.agentic/commands/create-plan.md`
 - `@.agentic/commands/create-proposal.md`

package/dist/templates/commands/project-requirements.md

@@ -27,7 +27,7 @@ Read:
 10. Only ask for missing details that block useful requirement understanding.
 11. If the user has already asked for a later deliverable and the existing context is sufficient, acknowledge that and let them move there instead of forcing this step.
 
-When the requirements are strong enough, tell the user the available next options:
+When the requirements are strong enough, tell the user the available next options, and also make it clear they can ask for something else by saying what they want to do next.
 
 - `@.agentic/commands/architecture.md` (recommended)
 - `@.agentic/commands/create-plan.md`

package/dist/templates/core/init.md

@@ -65,6 +65,6 @@ You are starting a fresh AI session inside this project. Your job is to quickly
    - if BRD work already exists, also allow `@.agentic/commands/create-frd.md`
    - if FRD work already exists, also allow `@.agentic/commands/create-estimate.md`
    - if estimate work already exists, also allow `@.agentic/commands/create-proposal.md`
-18. Only when you have done enough useful intake work for a first-time project, end with:
+18. Only when you have done enough useful intake work for a first-time project, end by recommending the next command and also make it clear the user can say what they want to do now:
 
 `Next type @.agentic/commands/project-requirements.md`

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-agentic-starter",
-  "version": "0.1.13",
+  "version": "0.1.15",
   "description": "Scaffold a minimal AI-powered project delivery workflow inside the current folder.",
   "license": "MIT",
   "type": "module",
@@ -8,7 +8,8 @@
     "create-agentic-starter": "./dist/index.js"
   },
   "files": [
-    "dist"
+    "dist",
+    "README.md"
   ],
   "repository": {
     "type": "git",