create-agentic-starter 0.1.14 → 0.1.16

package/dist/templates/commands/architecture.md

@@ -19,8 +19,9 @@ Read:
 7. If architecture-critical information is still missing, ask architecture-specific questions and keep updating `.agentic/workspace/memory/architecture.md` instead of routing yet.
 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.
+10. For UI-heavy or design-led projects, you may use Figma MCP or a similar design integration if it is available and the user approves. Otherwise rely on the design assets already placed in `.agentic/workspace/project/`.
 
-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

@@ -26,8 +26,9 @@ Read:
 9. If the requirement understanding is still weak or important gaps remain, continue asking focused project questions and keep updating the memory files.
 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.
+12. If Figma MCP or a similar design integration is available and useful, you may offer to use it to inspect the design or gather screenshots, but ask the user before doing so. If it is not available, ask for screenshots, exported frames, links, or file paths and organize them under `.agentic/workspace/project/`.
 
-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/context.md

@@ -27,6 +27,8 @@ Use `.agentic/workspace/project/` for:
 
 If relevant project materials are found outside this folder, move or organize them into `.agentic/workspace/project/` by default. Only leave them in place if the user explicitly says not to move them.
 
+Figma MCP or a similar design integration is optional. If it is available, it may be used to inspect designs or gather screenshots, but ask the user before using it. If it is not available, continue with screenshots, exported frames, links, or files placed under `.agentic/workspace/project/`.
+
 ### Memory
 
 Use `.agentic/workspace/memory/` for:

package/dist/templates/core/init.md

@@ -47,24 +47,25 @@ You are starting a fresh AI session inside this project. Your job is to quickly
    - scope or modules
    - available references such as screenshots, docs, notes, links, or file paths
    - desired outputs
-8. If enough context exists, give a short summary of the project and the most important missing pieces.
-9. If the user mentions screenshots, notes, requirement docs, links, or file paths, move or organize them into `.agentic/workspace/project/` by default unless the user explicitly says not to.
-10. After the first useful exchange, create or update:
+8. When design references are important and the user mentions Figma, you may suggest using Figma MCP if it is available in the environment, but ask the user before using it. If it is not available, ask for screenshots, exported frames, links, or file paths and continue normally.
+9. If enough context exists, give a short summary of the project and the most important missing pieces.
+10. If the user mentions screenshots, notes, requirement docs, links, or file paths, move or organize them into `.agentic/workspace/project/` by default unless the user explicitly says not to.
+11. After the first useful exchange, create or update:
    - `.agentic/workspace/memory/project-overview.md`
    - `.agentic/workspace/memory/requirements.md`
    - `.agentic/workspace/memory/open-questions.md`
-11. Update `.agentic/workspace/memory/architecture.md` only if the new context changes architecture.
-12. Write drafts even from partial information.
-13. Clearly separate confirmed facts, assumptions, and open questions.
-14. Do not route immediately just because the workspace is empty. Do useful synthesis or ask focused questions first.
-15. Do not rewrite unrelated files just because `@.agentic/init.md` ran.
-16. If important project basics are still missing, continue asking focused questions and keep updating the memory files instead of routing forward yet.
-17. When suggesting next commands in resumed sessions, use the existing progress:
+12. Update `.agentic/workspace/memory/architecture.md` only if the new context changes architecture.
+13. Write drafts even from partial information.
+14. Clearly separate confirmed facts, assumptions, and open questions.
+15. Do not route immediately just because the workspace is empty. Do useful synthesis or ask focused questions first.
+16. Do not rewrite unrelated files just because `@.agentic/init.md` ran.
+17. If important project basics are still missing, continue asking focused questions and keep updating the memory files instead of routing forward yet.
+18. When suggesting next commands in resumed sessions, use the existing progress:
    - if requirements exist but architecture does not, recommend `@.agentic/commands/architecture.md`
    - if architecture exists, suggest `@.agentic/commands/create-brd.md`, `@.agentic/commands/create-proposal.md`, `@.agentic/commands/create-plan.md`, and `@.agentic/commands/create-tasks.md`
    - 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:
+19. 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/dist/templates/meta/agents.md

@@ -62,6 +62,8 @@ Starter export scripts live under `.agentic/workspace/scripts/`.
 
 Adapt the relevant script when the project needs a custom template or style. Keep the script path stable by default instead of inventing a separate export path.
 
+Figma MCP can be used as an optional accelerator for design intake when it is available. Ask the user before using it, and continue with normal screenshots or exported design assets when MCP is not available.
+
 Dependency guidance:
 
 1. Prefer the target project root if it already has a usable Node environment.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-agentic-starter",
-  "version": "0.1.14",
+  "version": "0.1.16",
   "description": "Scaffold a minimal AI-powered project delivery workflow inside the current folder.",
   "license": "MIT",
   "type": "module",