npm - create-agentic-starter - Versions diffs - 0.1.6 → 0.1.8 - Mend

create-agentic-starter 0.1.6 → 0.1.8

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (3) hide show

package/README.md CHANGED Viewed

@@ -28,7 +28,9 @@ Run the command inside an existing project folder.
 The scaffold is non-interactive. It will:
 - recreate `.agentic/`
-- preserve existing `AGENTS.md` and `.gitignore`, appending a marked `create-agentic-starter` section when needed
+- create `.docs/` for user-facing outputs
+- preserve existing `AGENTS.md`, appending a marked `create-agentic-starter` section when needed
+- never modify `.gitignore`
 - never modify `README.md`
 - print the next step for the team
@@ -42,6 +44,8 @@ The command sets up:
 - `.agentic/workspace/project/`
 - `.agentic/workspace/memory/`
 - `.agentic/workspace/documents/`
+- `.agentic/workspace/scripts/`
+- `.docs/`
 - `AGENTS.md`
 ## First Run Flow

package/dist/index.js CHANGED Viewed

@@ -1,15 +1,15 @@
 #!/usr/bin/env node
-import{mkdir as E,rm as q,writeFile as I}from"fs/promises";import l from"path";import{readFile as R,writeFile as u}from"fs/promises";import b from"path";function g(e){return e.replace(/[.*+?^${}()|[\]\\]/g,"\\$&")}function A(e,t,o,r){let n=new RegExp(`${g(o)}[\\s\\S]*?${g(r)}\\n?`,"m");if(n.test(e))return e.replace(n,`${t}
-`);let s=e.endsWith(`
+import{mkdir as R,rm as A,writeFile as q}from"fs/promises";import p from"path";import{readFile as v,writeFile as m}from"fs/promises";import j from"path";function u(e){return e.replace(/[.*+?^${}()|[\]\\]/g,"\\$&")}function I(e,t,s,r){let n=new RegExp(`${u(s)}[\\s\\S]*?${u(r)}\\n?`,"m");if(n.test(e))return e.replace(n,`${t}
+`);let o=e.endsWith(`
 `)?`
 `:`
-`;return`${e}${s}${t}
-`}async function i(e,t,o,r,n){let s=b.join(e,t);try{let a=await R(s,"utf8"),j=A(a,o,r,n);await u(s,j,"utf8")}catch(a){if(a.code!=="ENOENT")throw a;await u(s,`${o}
-`,"utf8")}}var f="AGENTS.md",h=".gitignore",c="<!-- from create-agentic-starter:agents:start -->",m="<!-- from create-agentic-starter:agents:end -->",d="# from create-agentic-starter:start",p="# from create-agentic-starter:end",w=`${c}
+`;return`${e}${o}${t}
+`}async function h(e,t,s,r,n){let o=j.join(e,t);try{let a=await v(o,"utf8"),b=I(a,s,r,n);await m(o,b,"utf8")}catch(a){if(a.code!=="ENOENT")throw a;await m(o,`${s}
+`,"utf8")}}var f="AGENTS.md",i="<!-- from create-agentic-starter:agents:start -->",c="<!-- from create-agentic-starter:agents:end -->",g=`${i}
 # Agentic Starter Guide
-This project includes a reusable AI working area under \`.agentic/\` for project kick-off and pre-delivery documentation.
+This project includes a reusable AI working area under \`.agentic/\` for project kick-off and delivery documentation.
 ## What This Is For
@@ -17,145 +17,70 @@ Use this scaffold when you want an AI tool to:
 - understand a project from files, notes, screenshots, and links
 - maintain structured project memory
-- generate markdown deliverables such as BRD, FRD, estimate, and proposal
+- prepare internal drafts in \`.agentic/workspace/\`
+- create user-facing deliverables in \`.docs/\`
+- optionally use Node.js export helpers from \`.agentic/workspace/scripts/\`
 ## Folder Purpose
 - \`.agentic/init.md\`: first prompt for every new AI session
 - \`.agentic/context.md\`: shared rules and folder map
 - \`.agentic/commands/\`: task-specific prompt files you reference in your AI tool
-- \`.agentic/workspace/project/\`: raw project inputs such as screenshots, notes, requirement docs, and reference links
+- \`.agentic/workspace/project/\`: raw project inputs such as screenshots, notes, requirement docs, and references
 - \`.agentic/workspace/memory/\`: evolving AI-maintained project understanding
-- \`.agentic/workspace/documents/\`: polished markdown deliverables
+- \`.agentic/workspace/documents/\`: internal drafts and intermediate artifacts
+- \`.agentic/workspace/scripts/\`: optional Node export helpers
+- \`.docs/\`: user-facing deliverables
 ## How To Use It
 1. Open your AI tool in this project.
 2. Start every new session with \`@.agentic/init.md\`.
-3. Follow the command sequence below.
+3. Follow the command flow below.
-## V1 Command Sequence
+## Command Flow
 1. \`@.agentic/init.md\`
 2. \`@.agentic/commands/project-requirements.md\`
 3. \`@.agentic/commands/architecture.md\`
-4. \`@.agentic/commands/create-brd.md\`
-5. \`@.agentic/commands/create-frd.md\`
-6. \`@.agentic/commands/create-estimate.md\`
-7. \`@.agentic/commands/create-proposal.md\`
+4. Then choose from the available options shown by the current command, such as:
+   - \`@.agentic/commands/create-brd.md\`
+   - \`@.agentic/commands/create-frd.md\`
+   - \`@.agentic/commands/create-estimate.md\`
+   - \`@.agentic/commands/create-proposal.md\`
+   - \`@.agentic/commands/create-plan.md\`
+   - \`@.agentic/commands/create-tasks.md\`
-If your tool does not support \`@file\` references, paste the contents of the prompt file into a new chat manually.
-${m}
-`,k=`${d}
-.agentic/workspace/documents/
-.agentic/workspace/memory/
-${p}
-`;var y=[".agentic"],x=[".agentic",".agentic/commands",".agentic/workspace",".agentic/workspace/project",".agentic/workspace/memory",".agentic/workspace/documents"],v=()=>({".agentic/init.md":`# Init
-Read \`@.agentic/context.md\` first.
-You are starting a fresh AI session inside this project. Your job is to quickly understand what this project is, what context already exists, and what the user still needs to provide.
-## Read Scope
-1. Read only root-level files and folders in the current project.
-2. Do not recursively inspect the full repository.
-3. Treat \`.agentic/\` as the exception:
-   - inspect \`.agentic/workspace/project/\`
-   - inspect \`.agentic/workspace/memory/\`
-   - inspect \`.agentic/workspace/documents/\`
-4. Use existing workspace context if it is already present.
-## Response Style
-1. Be concise and synthesis-first.
-2. Do not dump a full file inventory unless the user explicitly asks.
-3. Do not mirror the prompt structure back to the user.
-4. Respond with either:
-   - a short synthesized summary of what you understand, or
-   - a few focused questions if important context is still missing
-## What To Do
-1. Infer what kind of project this is from the root-level signals.
-2. Check whether \`.agentic/workspace/project/\`, \`.agentic/workspace/memory/\`, and \`.agentic/workspace/documents/\` already contain useful context.
-3. Build the best current understanding from:
-   - root-level signals
-   - existing workspace files
-   - the user's message in this chat
-4. If project context is thin, ask a small number of targeted questions about:
-   - project goal
-   - target users
-   - scope or modules
-   - available references such as screenshots, docs, notes, links, or file paths
-   - desired outputs
-5. If enough context exists, give a short summary of the project and the most important missing pieces.
-6. 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.
-7. 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\`
-8. Write drafts even from partial information.
-9. Clearly separate confirmed facts, assumptions, and open questions.
-10. Do not route immediately just because the workspace is empty. Do useful synthesis or ask focused questions first.
-11. Once you have done useful intake work, end with:
-\`Next type @.agentic/commands/project-requirements.md\`
-`,".agentic/context.md":`# Context
-This repository uses a prompt-based project kick-off system.
+## Output Conventions
-## Folder Map
-- \`.agentic/init.md\`: session bootstrap prompt
-- \`.agentic/context.md\`: shared rules and folder semantics
-- \`.agentic/commands/\`: prompt files for distinct tasks
-- \`.agentic/workspace/project/\`: raw project materials
-- \`.agentic/workspace/memory/\`: evolving AI-maintained understanding
-- \`.agentic/workspace/documents/\`: polished markdown outputs
+Default user-facing outputs live under \`.docs/\`:
-## Workspace Semantics
+- BRD: \`.docs/brd/brd.docx\`
+- FRD: \`.docs/frd/frd.docx\`
+- Estimate: \`.docs/estimate/estimate.xlsx\`
+- Proposal: \`.docs/proposal/proposal.pptx\`
+- Plan: \`.docs/plan/plan.docx\` or \`.docs/plan/plan.xlsx\`
+- Tasks: \`.docs/tasks/tasks.xlsx\`
-### Project
+## Export Helpers
-Use \`.agentic/workspace/project/\` for:
+Optional export scripts can live under \`.agentic/workspace/scripts/\`.
-- Figma screenshots
-- requirement notes
-- requirement documents
-- links captured into markdown files
-- user-supplied project references
-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.
-### Memory
-Use \`.agentic/workspace/memory/\` for:
-- \`project-overview.md\`
-- \`requirements.md\`
-- \`open-questions.md\`
-- \`architecture.md\`
-- assumptions and structured working memory
+Dependency guidance:
-### Documents
+1. Prefer the target project root if it already has a usable Node environment.
+2. If root is not suitable, ask the user which path should receive the install.
+3. Ask the user before running any \`npm install\`.
-Use \`.agentic/workspace/documents/\` for polished outputs:
+Planned library stack:
-- \`brd.md\`
-- \`frd.md\`
-- \`estimate.md\`
-- \`proposal.md\`
+- \`docx\`
+- \`pptxgenjs\`
+- \`exceljs\`
-## Working Rules
-1. Reuse and improve existing workspace files when they already exist.
-2. Do not scan the whole repository unless the user explicitly asks.
-3. If relevant project assets are outside \`.agentic/workspace/project/\`, move them into the workspace by default and then use the workspace copy.
-4. Only avoid moving files when the user explicitly asks to keep them in place.
-5. Ask only the minimum blocking questions required to continue.
-6. Always end by telling the user the exact next command to run.
-`,".agentic/commands/project-requirements.md":`# Project Requirements
+If your tool does not support \`@file\` references, paste the contents of the prompt file into a new chat manually.
+${c}
+`;var k={".agentic/commands/project-requirements.md":`# Project Requirements
 Read:
@@ -173,18 +98,21 @@ Read:
    - existing file paths already shared by the user, or
    - fresh explanation typed in chat
 4. Move or organize project inputs into \`.agentic/workspace/project/\` by default unless the user explicitly says not to.
-5. Organize and normalize the project context so the later architecture and document steps can rely on it.
+5. Organize and normalize the project context so later architecture and deliverable steps can rely on it.
 6. Create or update:
    - \`.agentic/workspace/memory/project-overview.md\`
    - \`.agentic/workspace/memory/requirements.md\`
    - \`.agentic/workspace/memory/open-questions.md\`
 7. Capture assumptions separately from confirmed facts.
-8. Reduce open questions where possible before handing off to architecture.
-9. Ask only for missing details that block useful requirement understanding.
+8. Reduce open questions where possible before handing off.
+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.
-When done, tell the user:
+When the requirements are strong enough, tell the user the available next options:
-\`Next type @.agentic/commands/architecture.md\`
+- \`@.agentic/commands/architecture.md\` (recommended)
+- \`@.agentic/commands/create-plan.md\`
+- \`@.agentic/commands/create-proposal.md\`
 `,".agentic/commands/architecture.md":`# Architecture
 Read:
@@ -203,11 +131,15 @@ Read:
 4. Add a diagram description or mermaid diagram when supported.
 5. Mention draw.io MCP only as an optional tool if available in the user's environment.
 6. If relevant screenshots, notes, or references are found outside \`.agentic/workspace/project/\`, move or organize them into the workspace by default unless the user explicitly says not to.
-7. Ask only the minimum blocking questions.
+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.
-When done, tell the user:
+When the architecture is strong enough, tell the user the available next options:
-\`Next type @.agentic/commands/create-brd.md\`
+- \`@.agentic/commands/create-brd.md\`
+- \`@.agentic/commands/create-proposal.md\`
+- \`@.agentic/commands/create-plan.md\`
+- \`@.agentic/commands/create-tasks.md\`
 `,".agentic/commands/create-brd.md":`# Create BRD
 Read:
@@ -220,13 +152,20 @@ Read:
 ## Your job
-1. Create or update \`.agentic/workspace/documents/brd.md\`.
-2. Produce a polished markdown Business Requirements Document.
-3. Use confirmed facts first and clearly label assumptions where needed.
-4. If relevant source material is outside \`.agentic/workspace/project/\`, move or organize it into the workspace by default unless the user explicitly says not to.
-5. If critical information is missing, ask only the minimum blocking questions before drafting.
-When done, tell the user:
+1. Maintain any internal draft content under \`.agentic/workspace/documents/brd.*\` if useful.
+2. Produce the user-facing BRD at \`.docs/brd/brd.docx\`.
+3. Assume Node.js export scripts will later convert structured content and templates into the final \`.docx\`.
+4. If the user already provided a template file/path/reference, follow it.
+5. Otherwise ask whether they want a specific BRD style or structure.
+6. If neither a template nor a style is provided, use the built-in default structure.
+7. If export dependencies are needed, first check whether the target project root already has a usable Node environment.
+8. Prefer the project root if it is suitable; otherwise ask the user which path should receive the install.
+9. Ask the user before running any \`npm install\`.
+10. Use confirmed facts first and clearly label assumptions where needed.
+11. If relevant source material is outside \`.agentic/workspace/project/\`, move or organize it into the workspace by default unless the user explicitly says not to.
+12. If critical information is missing, ask only the minimum blocking questions and keep improving the BRD draft instead of routing yet.
+When the BRD is solid enough to define functional requirements, tell the user:
 \`Next type @.agentic/commands/create-frd.md\`
 `,".agentic/commands/create-frd.md":`# Create FRD
@@ -237,18 +176,24 @@ Read:
 - \`.agentic/workspace/memory/project-overview.md\`
 - \`.agentic/workspace/memory/requirements.md\`
 - \`.agentic/workspace/memory/architecture.md\`
-- \`.agentic/workspace/documents/brd.md\` if it exists
+- \`.agentic/workspace/documents/brd.*\` if it exists
 - relevant files under \`.agentic/workspace/project/\`
 ## Your job
-1. Create or update \`.agentic/workspace/documents/frd.md\`.
-2. Produce a polished markdown Functional Requirements Document.
-3. Cover modules, flows, validations, roles, and edge cases where relevant.
-4. If relevant source material is outside \`.agentic/workspace/project/\`, move or organize it into the workspace by default unless the user explicitly says not to.
-5. Ask only the minimum blocking questions.
+1. Maintain any internal draft content under \`.agentic/workspace/documents/frd.*\` if useful.
+2. Produce the user-facing FRD at \`.docs/frd/frd.docx\`.
+3. Assume Node.js export scripts will later convert structured content into the final \`.docx\`.
+4. Keep the content behavior straightforward unless the user explicitly supplies a template or style preference.
+5. If export dependencies are needed, first check whether the target project root already has a usable Node environment.
+6. Prefer the project root if it is suitable; otherwise ask the user which path should receive the install.
+7. Ask the user before running any \`npm install\`.
+8. Cover modules, flows, validations, roles, and edge cases where relevant.
+9. If relevant source material is outside \`.agentic/workspace/project/\`, move or organize it into the workspace by default unless the user explicitly says not to.
+10. If important functional details are still missing, ask focused follow-up questions and keep improving the FRD instead of routing yet.
+11. Ask only the minimum blocking questions.
-When done, tell the user:
+When the FRD is strong enough for estimation, tell the user:
 \`Next type @.agentic/commands/create-estimate.md\`
 `,".agentic/commands/create-estimate.md":`# Create Estimate
@@ -259,18 +204,26 @@ Read:
 - \`.agentic/workspace/memory/project-overview.md\`
 - \`.agentic/workspace/memory/requirements.md\`
 - \`.agentic/workspace/memory/architecture.md\`
-- \`.agentic/workspace/documents/brd.md\` if it exists
-- \`.agentic/workspace/documents/frd.md\` if it exists
+- \`.agentic/workspace/documents/brd.*\` if it exists
+- \`.agentic/workspace/documents/frd.*\` if it exists
 ## Your job
-1. Create or update \`.agentic/workspace/documents/estimate.md\`.
-2. Produce a markdown estimate with effort breakdown, assumptions, dependencies, and risks.
-3. Keep the estimate aligned with the known scope and clearly state uncertainty.
-4. If relevant source material is outside \`.agentic/workspace/project/\`, move or organize it into the workspace by default unless the user explicitly says not to.
-5. Ask only the minimum blocking questions.
-When done, tell the user:
+1. Maintain any internal draft content under \`.agentic/workspace/documents/estimate.*\` if useful.
+2. Produce the user-facing estimate at \`.docs/estimate/estimate.xlsx\`.
+3. Assume Node.js export scripts will later convert structured content and templates into the final \`.xlsx\`.
+4. If the user already provided a template file/path/reference, follow it.
+5. Otherwise ask whether they want a specific estimate style or structure.
+6. If neither a template nor a style is provided, use the built-in default structure.
+7. If export dependencies are needed, first check whether the target project root already has a usable Node environment.
+8. Prefer the project root if it is suitable; otherwise ask the user which path should receive the install.
+9. Ask the user before running any \`npm install\`.
+10. Keep the estimate aligned with the known scope and clearly state uncertainty.
+11. If relevant source material is outside \`.agentic/workspace/project/\`, move or organize it into the workspace by default unless the user explicitly says not to.
+12. If the estimate is too uncertain because key delivery information is missing, ask focused follow-up questions and keep refining the estimate instead of routing yet.
+13. Ask only the minimum blocking questions.
+When the estimate is strong enough for proposal drafting, tell the user:
 \`Next type @.agentic/commands/create-proposal.md\`
 `,".agentic/commands/create-proposal.md":`# Create Proposal
@@ -281,17 +234,270 @@ Read:
 - \`.agentic/workspace/memory/project-overview.md\`
 - \`.agentic/workspace/memory/requirements.md\`
 - \`.agentic/workspace/memory/architecture.md\`
-- \`.agentic/workspace/documents/brd.md\` if it exists
-- \`.agentic/workspace/documents/frd.md\` if it exists
-- \`.agentic/workspace/documents/estimate.md\` if it exists
+- \`.agentic/workspace/documents/brd.*\` if it exists
+- \`.agentic/workspace/documents/frd.*\` if it exists
+- \`.agentic/workspace/documents/estimate.*\` if it exists
+## Your job
+1. Maintain any internal draft content under \`.agentic/workspace/documents/proposal.*\` if useful.
+2. Produce the user-facing proposal at \`.docs/proposal/proposal.pptx\`.
+3. Assume Node.js export scripts will later convert structured content and templates into the final \`.pptx\`.
+4. Keep the prompt focused on presentation-ready content unless the user explicitly provides a template or style preference.
+5. If export dependencies are needed, first check whether the target project root already has a usable Node environment.
+6. Prefer the project root if it is suitable; otherwise ask the user which path should receive the install.
+7. Ask the user before running any \`npm install\`.
+8. Make gaps explicit instead of inventing details.
+9. If relevant screenshots, decks, notes, or references are found outside \`.agentic/workspace/project/\`, move or organize them into the workspace by default unless the user explicitly says not to.
+10. If key proposal inputs are still missing, ask focused questions and keep improving the proposal instead of prematurely declaring completion.
+11. Ask only the minimum blocking questions.
+When the proposal is complete enough for handoff, tell the user the workflow is complete and list the generated files.
+`,".agentic/commands/create-plan.md":`# Create Plan
+Read:
+- \`@.agentic/context.md\`
+- \`.agentic/workspace/memory/project-overview.md\`
+- \`.agentic/workspace/memory/requirements.md\`
+- \`.agentic/workspace/memory/architecture.md\` if it exists
+- relevant files under \`.agentic/workspace/project/\`
 ## Your job
-1. Create or update \`.agentic/workspace/documents/proposal.md\`.
-2. Produce a polished markdown proposal using the known scope, architecture direction, and estimate.
-3. Make gaps explicit instead of inventing details.
-4. If relevant screenshots, decks, notes, or references are found outside \`.agentic/workspace/project/\`, move or organize them into the workspace by default unless the user explicitly says not to.
-5. Ask only the minimum blocking questions.
+1. Maintain any internal draft content under \`.agentic/workspace/documents/plan.*\` if useful.
+2. If the user has not already specified the preferred plan output, ask whether they want:
+   - a document-style plan, or
+   - a spreadsheet-style plan
+3. If the user already provided a template file/path/reference, follow it.
+4. Otherwise ask whether they want a specific plan style or structure.
+5. If neither a template nor a style is provided, use the built-in default structure.
+6. Produce the user-facing output at:
+   - \`.docs/plan/plan.docx\` for document-style plan output, or
+   - \`.docs/plan/plan.xlsx\` for spreadsheet-style plan output
+7. Assume Node.js export scripts will later convert structured content and templates into the final output format.
+8. If export dependencies are needed, first check whether the target project root already has a usable Node environment.
+9. Prefer the project root if it is suitable; otherwise ask the user which path should receive the install.
+10. Ask the user before running any \`npm install\`.
+11. Include phases, milestones, dependencies, assumptions, risks, and sequencing.
+12. If relevant source material is outside \`.agentic/workspace/project/\`, move or organize it into the workspace by default unless the user explicitly says not to.
+13. If planning inputs are missing, ask focused questions and keep refining instead of routing.
+When the plan is complete enough, tell the user the available next options:
+- \`@.agentic/commands/architecture.md\`
+- \`@.agentic/commands/create-tasks.md\`
+- \`@.agentic/commands/create-brd.md\`
+- \`@.agentic/commands/create-proposal.md\`
+`,".agentic/commands/create-tasks.md":`# Create Tasks
+Read:
+- \`@.agentic/context.md\`
+- \`.agentic/workspace/memory/project-overview.md\`
+- \`.agentic/workspace/memory/requirements.md\`
+- \`.agentic/workspace/memory/architecture.md\` if it exists
+- \`.agentic/workspace/documents/plan.*\` if it exists
+- \`.agentic/workspace/documents/brd.*\` if it exists
+- \`.agentic/workspace/documents/frd.*\` if it exists
+- relevant files under \`.agentic/workspace/project/\`
-When done, tell the user the v1 workflow is complete and list the generated files.
-`});async function T(e){await Promise.all(y.map(t=>q(l.join(e,t),{recursive:!0,force:!0})))}async function S(e){await Promise.all(x.map(t=>E(l.join(e,t),{recursive:!0})))}async function N(e){let t=v();await Promise.all(Object.entries(t).map(([o,r])=>I(l.join(e,o),r,"utf8")))}async function P(){let e=process.cwd();await T(e),await S(e),await N(e),await i(e,f,w,c,m),await i(e,h,k,d,p),console.log(""),console.log("create-agentic-starter: scaffold created successfully."),console.log(`Project folder: ${e}`),console.log(""),console.log("Next steps:"),console.log("1. Open your AI tool in this folder."),console.log("2. Start a new chat with @.agentic/init.md"),console.log("")}P().catch(e=>{let t=e instanceof Error?e.message:String(e);console.error(`create-agentic-starter: failed to scaffold project. ${t}`),process.exitCode=1});
+## Your job
+1. Maintain any internal draft content under \`.agentic/workspace/documents/tasks.*\` if useful.
+2. Produce the user-facing task breakdown at \`.docs/tasks/tasks.xlsx\`.
+3. Assume Node.js export scripts will later convert structured content and templates into the final \`.xlsx\`.
+4. If the user already provided a template file/path/reference, follow it.
+5. Otherwise ask whether they want a specific task breakdown style or structure.
+6. If neither a template nor a style is provided, use the built-in default structure.
+7. If export dependencies are needed, first check whether the target project root already has a usable Node environment.
+8. Prefer the project root if it is suitable; otherwise ask the user which path should receive the install.
+9. Ask the user before running any \`npm install\`.
+10. Produce a practical task breakdown with modules, roles, dependencies, sequencing, and status placeholders.
+11. If relevant source material is outside \`.agentic/workspace/project/\`, move or organize it into the workspace by default unless the user explicitly says not to.
+12. If execution detail is missing, ask focused questions and keep refining instead of routing.
+When the tasks are complete enough, tell the user the available next options:
+- \`@.agentic/commands/create-plan.md\`
+- \`@.agentic/commands/create-proposal.md\`
+- \`@.agentic/commands/create-brd.md\`
+`};var w={".agentic/init.md":`# Init
+Read \`@.agentic/context.md\` first.
+You are starting a fresh AI session inside this project. Your job is to quickly understand what this project is, what context already exists, and what the user still needs to provide.
+## Read Scope
+1. Read only root-level files and folders in the current project.
+2. Do not recursively inspect the full repository.
+3. Treat \`.agentic/\` as the exception:
+   - inspect \`.agentic/workspace/project/\`
+   - inspect \`.agentic/workspace/memory/\`
+   - inspect \`.agentic/workspace/documents/\`
+4. Use existing workspace context if it is already present.
+## Response Style
+1. Be concise and synthesis-first.
+2. Do not dump a full file inventory unless the user explicitly asks.
+3. Do not mirror the prompt structure back to the user.
+4. Respond with either:
+   - a short synthesized summary of what you understand, or
+   - a few focused questions if important context is still missing
+## What To Do
+1. Infer what kind of project this is from the root-level signals.
+2. Check whether \`.agentic/workspace/project/\`, \`.agentic/workspace/memory/\`, and \`.agentic/workspace/documents/\` already contain useful context.
+3. Build the best current understanding from:
+   - root-level signals
+   - existing workspace files
+   - the user's message in this chat
+4. If project context is thin, ask a small number of targeted questions about:
+   - project goal
+   - target users
+   - scope or modules
+   - available references such as screenshots, docs, notes, links, or file paths
+   - desired outputs
+5. If enough context exists, give a short summary of the project and the most important missing pieces.
+6. 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.
+7. 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\`
+8. Write drafts even from partial information.
+9. Clearly separate confirmed facts, assumptions, and open questions.
+10. Do not route immediately just because the workspace is empty. Do useful synthesis or ask focused questions first.
+11. If important project basics are still missing, continue asking focused questions and keep updating the memory files instead of routing forward yet.
+12. Only when you have done enough useful intake work to create a solid initial understanding, end with:
+\`Next type @.agentic/commands/project-requirements.md\`
+`,".agentic/context.md":`# Context
+This repository uses a prompt-based project kick-off system.
+## Folder Map
+- \`.agentic/init.md\`: session bootstrap prompt
+- \`.agentic/context.md\`: shared rules and folder semantics
+- \`.agentic/commands/\`: prompt files for distinct tasks
+- \`.agentic/workspace/project/\`: raw project materials
+- \`.agentic/workspace/memory/\`: evolving AI-maintained understanding
+- \`.agentic/workspace/documents/\`: internal drafts and intermediate artifacts
+- \`.agentic/workspace/scripts/\`: optional Node export helpers
+- \`.docs/\`: user-facing deliverables
+## Workspace Semantics
+### Project
+Use \`.agentic/workspace/project/\` for:
+- Figma screenshots
+- requirement notes
+- requirement documents
+- links captured into markdown files
+- user-supplied project references
+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.
+### Memory
+Use \`.agentic/workspace/memory/\` for:
+- \`project-overview.md\`
+- \`requirements.md\`
+- \`open-questions.md\`
+- \`architecture.md\`
+- assumptions and structured working memory
+### Internal Documents
+Use \`.agentic/workspace/documents/\` for internal drafts or intermediate artifacts such as:
+- draft BRD content
+- draft FRD content
+- draft estimate content
+- draft proposal content
+- draft plan content
+- draft task breakdowns
+### Scripts
+Use \`.agentic/workspace/scripts/\` for optional Node.js export helpers.
+Planned library stack:
+- \`docx\` for \`.docx\`
+- \`pptxgenjs\` for \`.pptx\`
+- \`exceljs\` for \`.xlsx\`
+Install behavior:
+1. Check whether the target project root already has a usable Node environment.
+2. Prefer installing there if suitable.
+3. If root is not suitable or is ambiguous, ask the user which path should receive the install.
+4. Ask the user before running any \`npm install\`.
+### User Outputs
+Use \`.docs/\` for user-facing deliverables:
+- \`.docs/brd/brd.docx\`
+- \`.docs/frd/frd.docx\`
+- \`.docs/estimate/estimate.xlsx\`
+- \`.docs/proposal/proposal.pptx\`
+- \`.docs/plan/plan.docx\` or \`.docs/plan/plan.xlsx\`
+- \`.docs/tasks/tasks.xlsx\`
+## Working Rules
+1. Reuse and improve existing workspace files when they already exist.
+2. Do not scan the whole repository unless the user explicitly asks.
+3. If relevant project assets are outside \`.agentic/workspace/project/\`, move them into the workspace by default and then use the workspace copy.
+4. Only avoid moving files when the user explicitly asks to keep them in place.
+5. Keep internal working material in \`.agentic/workspace/\` and user-facing deliverables in \`.docs/\`.
+6. Prefer the target project root for Node-based export dependencies when a usable Node setup already exists there.
+7. If root is not suitable, ask the user which path should be used for dependency installation.
+8. Ask the user before running any install command.
+9. Ask only the minimum blocking questions required to continue.
+10. Always end by telling the user the exact next command to run or listing the available next options.
+`};var d=[".agentic"],l=[".agentic",".agentic/commands",".agentic/workspace",".agentic/workspace/project",".agentic/workspace/memory",".agentic/workspace/documents",".agentic/workspace/scripts",".docs",".docs/brd",".docs/frd",".docs/estimate",".docs/proposal",".docs/plan",".docs/tasks"];var y={".agentic/workspace/scripts/README.md":"# Export Scripts\n\nThis folder is reserved for optional Node.js export helpers that will later generate user-facing deliverables in `.docs/`.\n\n## Planned Libraries\n\n- `docx` for `.docx`\n- `pptxgenjs` for `.pptx`\n- `exceljs` for `.xlsx`\n\n## Install Strategy\n\n1. Check whether the target project root already has a usable Node environment.\n2. Prefer installing export dependencies there if suitable.\n3. If root is not suitable or is ambiguous, ask the user which path should receive the install.\n4. Ask the user before running any `npm install`.\n\n## Planned Outputs\n\n- BRD: `.docs/brd/brd.docx`\n- FRD: `.docs/frd/frd.docx`\n- Estimate: `.docs/estimate/estimate.xlsx`\n- Proposal: `.docs/proposal/proposal.pptx`\n- Plan: `.docs/plan/plan.docx` or `.docs/plan/plan.xlsx`\n- Tasks: `.docs/tasks/tasks.xlsx`\n\nThese scripts are placeholders for now. They define the intended contract but do not perform real generation yet.\n",".agentic/workspace/scripts/generate_brd.js":`#!/usr/bin/env node
+console.error("generate_brd.js is not implemented yet.");
+console.error("Intended output: .docs/brd/brd.docx");
+console.error("Planned library: docx");
+process.exit(1);
+`,".agentic/workspace/scripts/generate_frd.js":`#!/usr/bin/env node
+console.error("generate_frd.js is not implemented yet.");
+console.error("Intended output: .docs/frd/frd.docx");
+console.error("Planned library: docx");
+process.exit(1);
+`,".agentic/workspace/scripts/generate_estimate.js":`#!/usr/bin/env node
+console.error("generate_estimate.js is not implemented yet.");
+console.error("Intended output: .docs/estimate/estimate.xlsx");
+console.error("Planned library: exceljs");
+process.exit(1);
+`,".agentic/workspace/scripts/generate_proposal.js":`#!/usr/bin/env node
+console.error("generate_proposal.js is not implemented yet.");
+console.error("Intended output: .docs/proposal/proposal.pptx");
+console.error("Planned library: pptxgenjs");
+process.exit(1);
+`,".agentic/workspace/scripts/generate_plan.js":`#!/usr/bin/env node
+console.error("generate_plan.js is not implemented yet.");
+console.error("Intended outputs: .docs/plan/plan.docx or .docs/plan/plan.xlsx");
+console.error("Planned libraries: docx or exceljs");
+process.exit(1);
+`,".agentic/workspace/scripts/generate_tasks.js":`#!/usr/bin/env node
+console.error("generate_tasks.js is not implemented yet.");
+console.error("Intended output: .docs/tasks/tasks.xlsx");
+console.error("Planned library: exceljs");
+process.exit(1);
+`};var x=()=>({...w,...k,...y});async function P(e){await Promise.all(d.map(t=>A(p.join(e,t),{recursive:!0,force:!0})))}async function E(e){await Promise.all(l.map(t=>R(p.join(e,t),{recursive:!0})))}async function N(e){let t=x();await Promise.all(Object.entries(t).map(([s,r])=>q(p.join(e,s),r,"utf8")))}async function T(){let e=process.cwd();await P(e),await E(e),await N(e),await h(e,f,g,i,c),console.log(""),console.log("create-agentic-starter: scaffold created successfully."),console.log(`Project folder: ${e}`),console.log(""),console.log("Next steps:"),console.log("1. Open your AI tool in this folder."),console.log("2. Start a new chat with @.agentic/init.md"),console.log("")}T().catch(e=>{let t=e instanceof Error?e.message:String(e);console.error(`create-agentic-starter: failed to scaffold project. ${t}`),process.exitCode=1});

package/package.json CHANGED Viewed

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