create-agentic-starter 0.1.7 → 0.1.9

package/README.md

@@ -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,8 +44,18 @@ The command sets up:
 - `.agentic/workspace/project/`
 - `.agentic/workspace/memory/`
 - `.agentic/workspace/documents/`
+- `.agentic/workspace/scripts/`
+- `.docs/`
 - `AGENTS.md`
 
+The scaffold also includes starter export scripts under `.agentic/workspace/scripts/` for:
+
+- `.docx` via `docx`
+- `.pptx` via `pptxgenjs`
+- `.xlsx` via `exceljs`
+
+Those scripts are meant to be adapted per project when the user provides a specific template or output style.
+
 ## First Run Flow
 
 After scaffolding:

package/dist/index.js

@@ -1,15 +1,15 @@
 #!/usr/bin/env node
-import{mkdir as I,rm as A,writeFile as E}from"fs/promises";import u from"path";import{readFile as R,writeFile as l}from"fs/promises";import b from"path";function g(e){return e.replace(/[.*+?^${}()|[\]\\]/g,"\\$&")}function q(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 F,rm as T,writeFile as _}from"fs/promises";import l from"path";import{readFile as v,writeFile as u}from"fs/promises";import j from"path";function h(e){return e.replace(/[.*+?^${}()|[\]\\]/g,"\\$&")}function P(e,t,s,r){let o=new RegExp(`${h(s)}[\\s\\S]*?${h(r)}\\n?`,"m");if(o.test(e))return e.replace(o,`${t}
+`);let a=e.endsWith(`
 `)?`
 `:`
 
-`;return`${e}${s}${t}
-`}async function a(e,t,o,r,n){let s=b.join(e,t);try{let i=await R(s,"utf8"),j=q(i,o,r,n);await l(s,j,"utf8")}catch(i){if(i.code!=="ENOENT")throw i;await l(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}${a}${t}
+`}async function m(e,t,s,r,o){let a=j.join(e,t);try{let n=await v(a,"utf8"),b=P(n,s,r,o);await u(a,b,"utf8")}catch(n){if(n.code!=="ENOENT")throw n;await u(a,`${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,146 +17,72 @@ 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/\`: starter Node export helpers that can be adapted per project
+- \`.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. 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:
+## Output Conventions
 
-\`Next type @.agentic/commands/project-requirements.md\`
-`,".agentic/context.md":`# Context
+Default user-facing outputs live under \`.docs/\`:
 
-This repository uses a prompt-based project kick-off system.
+- 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\`
 
-## Folder Map
+## Export Helpers
 
-- \`.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
+Starter export scripts live under \`.agentic/workspace/scripts/\`.
 
-## Workspace Semantics
+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.
 
-### Project
+Dependency guidance:
 
-Use \`.agentic/workspace/project/\` for:
+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\`.
 
-- 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
+Planned library stack:
 
-Use \`.agentic/workspace/memory/\` for:
+- \`docx\`
+- \`pptxgenjs\`
+- \`exceljs\`
 
-- \`project-overview.md\`
-- \`requirements.md\`
-- \`open-questions.md\`
-- \`architecture.md\`
-- assumptions and structured working memory
-
-### Documents
-
-Use \`.agentic/workspace/documents/\` for polished outputs:
-
-- \`brd.md\`
-- \`frd.md\`
-- \`estimate.md\`
-- \`proposal.md\`
-
-## 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 w={".agentic/commands/project-requirements.md":`# Project Requirements
 
 Read:
 
@@ -174,19 +100,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.
+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 the requirements are strong enough for architecture work, 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:
@@ -208,9 +136,12 @@ 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.
 
-When the architecture is strong enough for BRD drafting, 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:
@@ -223,11 +154,19 @@ 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 and keep improving the BRD draft instead of routing yet.
+1. Maintain any internal draft content under \`.agentic/workspace/documents/brd.md\` and structured export input under \`.agentic/workspace/documents/brd.json\` if useful.
+2. Produce the user-facing BRD at \`.docs/brd/brd.docx\`.
+3. Use or update the starter script at \`.agentic/workspace/scripts/generate_brd.js\` when export automation is needed.
+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 and starter script shape.
+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 the project's template or style requires different export logic, update \`.agentic/workspace/scripts/generate_brd.js\` instead of inventing a separate export path by default.
+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 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:
 
@@ -240,17 +179,23 @@ 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. If important functional details are still missing, ask focused follow-up questions and keep improving the FRD instead of routing yet.
-6. Ask only the minimum blocking questions.
+1. Maintain any internal draft content under \`.agentic/workspace/documents/frd.md\` and structured export input under \`.agentic/workspace/documents/frd.json\` if useful.
+2. Produce the user-facing FRD at \`.docs/frd/frd.docx\`.
+3. Use or update the starter script at \`.agentic/workspace/scripts/generate_frd.js\` when export automation is needed.
+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. If the project's template or style requires different export logic, update \`.agentic/workspace/scripts/generate_frd.js\` instead of inventing a separate export path by default.
+9. Cover modules, flows, validations, roles, and edge cases where relevant.
+10. 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.
+11. If important functional details are still missing, ask focused follow-up questions and keep improving the FRD instead of routing yet.
+12. Ask only the minimum blocking questions.
 
 When the FRD is strong enough for estimation, tell the user:
 
@@ -263,41 +208,661 @@ 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. 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.
-6. Ask only the minimum blocking questions.
+1. Maintain any internal draft content under \`.agentic/workspace/documents/estimate.md\` and structured export input under \`.agentic/workspace/documents/estimate.json\` if useful.
+2. Produce the user-facing estimate at \`.docs/estimate/estimate.xlsx\`.
+3. Use or update the starter script at \`.agentic/workspace/scripts/generate_estimate.js\` when export automation is needed.
+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 and starter script shape.
+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. If the project's template or style requires different export logic, update \`.agentic/workspace/scripts/generate_estimate.js\` instead of inventing a separate export path by default.
+11. Keep the estimate aligned with the known scope and clearly state uncertainty.
+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 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.
+14. 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
+`,".agentic/commands/create-proposal.md":"# Create Proposal\n\nRead:\n\n- `@.agentic/context.md`\n- `.agentic/workspace/memory/project-overview.md`\n- `.agentic/workspace/memory/requirements.md`\n- `.agentic/workspace/memory/architecture.md`\n- `.agentic/workspace/documents/brd.*` if it exists\n- `.agentic/workspace/documents/frd.*` if it exists\n- `.agentic/workspace/documents/estimate.*` if it exists\n\n## Your job\n\n1. Maintain any internal draft content under `.agentic/workspace/documents/proposal.md` and structured export input under `.agentic/workspace/documents/proposal.json` if useful.\n2. Produce the user-facing proposal at `.docs/proposal/proposal.pptx`.\n3. Use or update the starter script at `.agentic/workspace/scripts/generate_proposal.js` when export automation is needed.\n4. Keep the prompt focused on presentation-ready content unless the user explicitly provides a template or style preference.\n5. If export dependencies are needed, first check whether the target project root already has a usable Node environment.\n6. Prefer the project root if it is suitable; otherwise ask the user which path should receive the install.\n7. Ask the user before running any `npm install`.\n8. If the project's template or style requires different export logic, update `.agentic/workspace/scripts/generate_proposal.js` instead of inventing a separate export path by default.\n9. Make gaps explicit instead of inventing details.\n10. 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.\n11. If key proposal inputs are still missing, ask focused questions and keep improving the proposal instead of prematurely declaring completion.\n12. Ask only the minimum blocking questions.\n\nWhen the proposal is complete enough for handoff, tell the user the workflow is complete and list the generated files.\n",".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\`
-- \`.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/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. If key proposal inputs are still missing, ask focused questions and keep improving the proposal instead of prematurely declaring completion.
-6. Ask only the minimum blocking questions.
+1. Maintain any internal draft content under \`.agentic/workspace/documents/plan.md\` and structured export input under \`.agentic/workspace/documents/plan.json\` 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 and starter script shape.
+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. Use or update the starter script at \`.agentic/workspace/scripts/generate_plan.js\` when export automation is needed.
+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. If the project's template or style requires different export logic, update \`.agentic/workspace/scripts/generate_plan.js\` instead of inventing a separate export path by default.
+12. Include phases, milestones, dependencies, assumptions, risks, and sequencing.
+13. 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.
+14. 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\n\nRead:\n\n- `@.agentic/context.md`\n- `.agentic/workspace/memory/project-overview.md`\n- `.agentic/workspace/memory/requirements.md`\n- `.agentic/workspace/memory/architecture.md` if it exists\n- `.agentic/workspace/documents/plan.*` if it exists\n- `.agentic/workspace/documents/brd.*` if it exists\n- `.agentic/workspace/documents/frd.*` if it exists\n- relevant files under `.agentic/workspace/project/`\n\n## Your job\n\n1. Maintain any internal draft content under `.agentic/workspace/documents/tasks.md` and structured export input under `.agentic/workspace/documents/tasks.json` if useful.\n2. Produce the user-facing task breakdown at `.docs/tasks/tasks.xlsx`.\n3. Use or update the starter script at `.agentic/workspace/scripts/generate_tasks.js` when export automation is needed.\n4. If the user already provided a template file/path/reference, follow it.\n5. Otherwise ask whether they want a specific task breakdown style or structure.\n6. If neither a template nor a style is provided, use the built-in default structure and starter script shape.\n7. If export dependencies are needed, first check whether the target project root already has a usable Node environment.\n8. Prefer the project root if it is suitable; otherwise ask the user which path should receive the install.\n9. Ask the user before running any `npm install`.\n10. If the project's template or style requires different export logic, update `.agentic/workspace/scripts/generate_tasks.js` instead of inventing a separate export path by default.\n11. Produce a practical task breakdown with modules, roles, dependencies, sequencing, and status placeholders.\n12. 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.\n13. If execution detail is missing, ask focused questions and keep refining instead of routing.\n\nWhen the tasks are complete enough, tell the user the available next options:\n\n- `@.agentic/commands/create-plan.md`\n- `@.agentic/commands/create-proposal.md`\n- `@.agentic/commands/create-brd.md`\n"};var k={".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
+- structured export input such as \`brd.json\`, \`frd.json\`, \`estimate.json\`, \`proposal.json\`, \`plan.json\`, and \`tasks.json\`
+
+### Scripts
+
+Use \`.agentic/workspace/scripts/\` for Node.js export helpers.
+
+Starter scripts are scaffolded there by default. Update the relevant script for the current project when the user provides a custom template, layout, or style requirement.
+
+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"],p=[".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 I=`#!/usr/bin/env node
+
+const fs = require("node:fs");
+const path = require("node:path");
+
+function parseArgs(argv) {
+  const args = {};
+
+  for (let index = 0; index < argv.length; index += 1) {
+    const token = argv[index];
+
+    if (!token.startsWith("--")) {
+      continue;
+    }
+
+    const key = token.slice(2);
+    const next = argv[index + 1];
+
+    if (!next || next.startsWith("--")) {
+      args[key] = true;
+      continue;
+    }
+
+    args[key] = next;
+    index += 1;
+  }
+
+  return args;
+}
+
+function resolveFromRoot(targetPath) {
+  return path.resolve(process.cwd(), targetPath);
+}
+
+function ensureParentDir(filePath) {
+  fs.mkdirSync(path.dirname(filePath), { recursive: true });
+}
+
+function readJsonFile(relativePath) {
+  const absolutePath = resolveFromRoot(relativePath);
+
+  if (!fs.existsSync(absolutePath)) {
+    throw new Error(
+      "Input file not found: " +
+        relativePath +
+        "\\nCreate it first under .agentic/workspace/documents/ or pass --input."
+    );
+  }
+
+  return JSON.parse(fs.readFileSync(absolutePath, "utf8"));
+}
+
+function loadPackage(packageName) {
+  try {
+    return require(packageName);
+  } catch (error) {
+    console.error("Missing dependency:", packageName);
+    console.error(
+      "Install it in the target project's chosen Node environment before running this script."
+    );
+    console.error("Current working directory:", process.cwd());
+    process.exit(1);
+  }
+}
+
+function writeBuffer(relativePath, buffer) {
+  const absolutePath = resolveFromRoot(relativePath);
+  ensureParentDir(absolutePath);
+  fs.writeFileSync(absolutePath, buffer);
+  return absolutePath;
+}
+
+function writeSuccess(label, absolutePath) {
+  console.log(label + " written to " + absolutePath);
+}
+
+function toParagraphs(docx, lines, options = {}) {
+  if (!Array.isArray(lines) || lines.length === 0) {
+    return [];
+  }
+
+  return lines.map((line) =>
+    new docx.Paragraph({
+      text: String(line),
+      bullet: options.bullet ? { level: 0 } : undefined,
+      spacing: { after: options.bullet ? 80 : 160 },
+    })
+  );
+}
+
+function deriveColumns(rows) {
+  const firstRow = Array.isArray(rows) && rows.length > 0 ? rows[0] : null;
+
+  if (!firstRow || Array.isArray(firstRow)) {
+    return [];
+  }
+
+  return Object.keys(firstRow).map((key) => ({
+    header: key,
+    key,
+    width: Math.max(String(key).length + 4, 18),
+  }));
+}
+
+module.exports = {
+  parseArgs,
+  resolveFromRoot,
+  readJsonFile,
+  loadPackage,
+  writeBuffer,
+  writeSuccess,
+  toParagraphs,
+  deriveColumns,
+};
+`,S=`#!/usr/bin/env node
+
+const shared = require("./_shared.js");
+const docx = shared.loadPackage("docx");
+
+const args = shared.parseArgs(process.argv.slice(2));
+const inputPath = args.input || ".agentic/workspace/documents/brd.json";
+const outputPath = args.output || ".docs/brd/brd.docx";
+const data = shared.readJsonFile(inputPath);
+
+const children = [
+  new docx.Paragraph({
+    text: data.title || "Business Requirements Document",
+    heading: docx.HeadingLevel.TITLE,
+  }),
+];
+
+if (data.subtitle) {
+  children.push(
+    new docx.Paragraph({
+      text: String(data.subtitle),
+      spacing: { after: 240 },
+    })
+  );
+}
+
+for (const section of data.sections || []) {
+  if (section.heading) {
+    children.push(
+      new docx.Paragraph({
+        text: String(section.heading),
+        heading: docx.HeadingLevel.HEADING_1,
+      })
+    );
+  }
+
+  children.push(...shared.toParagraphs(docx, section.paragraphs));
+  children.push(...shared.toParagraphs(docx, section.bullets, { bullet: true }));
+}
+
+const document = new docx.Document({
+  sections: [{ children }],
+});
+
+docx.Packer.toBuffer(document).then((buffer) => {
+  const absolutePath = shared.writeBuffer(outputPath, buffer);
+  shared.writeSuccess("BRD", absolutePath);
+});
+`,A=`#!/usr/bin/env node
+
+const shared = require("./_shared.js");
+const docx = shared.loadPackage("docx");
+
+const args = shared.parseArgs(process.argv.slice(2));
+const inputPath = args.input || ".agentic/workspace/documents/frd.json";
+const outputPath = args.output || ".docs/frd/frd.docx";
+const data = shared.readJsonFile(inputPath);
+
+const children = [
+  new docx.Paragraph({
+    text: data.title || "Functional Requirements Document",
+    heading: docx.HeadingLevel.TITLE,
+  }),
+];
+
+for (const moduleItem of data.modules || []) {
+  children.push(
+    new docx.Paragraph({
+      text: String(moduleItem.name || "Module"),
+      heading: docx.HeadingLevel.HEADING_1,
+    })
+  );
+
+  children.push(...shared.toParagraphs(docx, moduleItem.summary ? [moduleItem.summary] : []));
+  children.push(...shared.toParagraphs(docx, moduleItem.features, { bullet: true }));
+  children.push(...shared.toParagraphs(docx, moduleItem.validations, { bullet: true }));
+  children.push(...shared.toParagraphs(docx, moduleItem.edgeCases, { bullet: true }));
+}
+
+const document = new docx.Document({
+  sections: [{ children }],
+});
+
+docx.Packer.toBuffer(document).then((buffer) => {
+  const absolutePath = shared.writeBuffer(outputPath, buffer);
+  shared.writeSuccess("FRD", absolutePath);
+});
+`,R=`#!/usr/bin/env node
+
+const shared = require("./_shared.js");
+const ExcelJS = shared.loadPackage("exceljs");
+
+const args = shared.parseArgs(process.argv.slice(2));
+const inputPath = args.input || ".agentic/workspace/documents/estimate.json";
+const outputPath = args.output || ".docs/estimate/estimate.xlsx";
+const data = shared.readJsonFile(inputPath);
+
+const workbook = new ExcelJS.Workbook();
+const worksheet = workbook.addWorksheet(data.sheetName || "Estimate");
+const rows = Array.isArray(data.rows) ? data.rows : [];
+
+worksheet.columns = Array.isArray(data.columns) && data.columns.length > 0
+  ? data.columns
+  : shared.deriveColumns(rows);
+
+for (const row of rows) {
+  worksheet.addRow(row);
+}
+
+worksheet.views = [{ state: "frozen", ySplit: 1 }];
+
+workbook.xlsx.writeBuffer().then((buffer) => {
+  const absolutePath = shared.writeBuffer(outputPath, buffer);
+  shared.writeSuccess("Estimate", absolutePath);
+});
+`,q=`#!/usr/bin/env node
+
+const shared = require("./_shared.js");
+const PptxGenJS = shared.loadPackage("pptxgenjs");
+
+const args = shared.parseArgs(process.argv.slice(2));
+const inputPath = args.input || ".agentic/workspace/documents/proposal.json";
+const outputPath = args.output || ".docs/proposal/proposal.pptx";
+const data = shared.readJsonFile(inputPath);
+
+const pptx = new PptxGenJS();
+pptx.layout = "LAYOUT_WIDE";
+pptx.author = "create-agentic-starter";
+
+const titleSlide = pptx.addSlide();
+titleSlide.addText(data.title || "Project Proposal", {
+  x: 0.7,
+  y: 1.0,
+  w: 11.0,
+  h: 0.8,
+  fontSize: 24,
+  bold: true,
+});
+
+if (data.subtitle) {
+  titleSlide.addText(String(data.subtitle), {
+    x: 0.7,
+    y: 2.0,
+    w: 10.5,
+    h: 0.5,
+    fontSize: 14,
+    color: "666666",
+  });
+}
+
+for (const slideData of data.slides || []) {
+  const slide = pptx.addSlide();
+
+  slide.addText(String(slideData.title || "Slide"), {
+    x: 0.7,
+    y: 0.5,
+    w: 11,
+    h: 0.6,
+    fontSize: 20,
+    bold: true,
+  });
+
+  const bullets = Array.isArray(slideData.bullets)
+    ? slideData.bullets.map((item) => ({ text: String(item), options: { bullet: { indent: 18 } } }))
+    : [];
+
+  if (bullets.length > 0) {
+    slide.addText(bullets, {
+      x: 0.9,
+      y: 1.5,
+      w: 10.6,
+      h: 4.5,
+      fontSize: 16,
+      breakLine: true,
+    });
+  } else if (slideData.body) {
+    slide.addText(String(slideData.body), {
+      x: 0.9,
+      y: 1.5,
+      w: 10.6,
+      h: 4.5,
+      fontSize: 16,
+      breakLine: true,
+    });
+  }
+}
+
+pptx.writeFile({ fileName: shared.resolveFromRoot(outputPath) }).then(() => {
+  shared.writeSuccess("Proposal", shared.resolveFromRoot(outputPath));
+});
+`,D=`#!/usr/bin/env node
+
+const shared = require("./_shared.js");
+
+const args = shared.parseArgs(process.argv.slice(2));
+const inputPath = args.input || ".agentic/workspace/documents/plan.json";
+const data = shared.readJsonFile(inputPath);
+const format = args.format || data.format || "docx";
+
+if (format === "xlsx") {
+  const ExcelJS = shared.loadPackage("exceljs");
+  const outputPath = args.output || ".docs/plan/plan.xlsx";
+  const workbook = new ExcelJS.Workbook();
+  const worksheet = workbook.addWorksheet(data.sheetName || "Plan");
+  const rows = Array.isArray(data.rows) ? data.rows : [];
+
+  worksheet.columns = Array.isArray(data.columns) && data.columns.length > 0
+    ? data.columns
+    : shared.deriveColumns(rows);
+
+  for (const row of rows) {
+    worksheet.addRow(row);
+  }
+
+  worksheet.views = [{ state: "frozen", ySplit: 1 }];
+
+  workbook.xlsx.writeBuffer().then((buffer) => {
+    const absolutePath = shared.writeBuffer(outputPath, buffer);
+    shared.writeSuccess("Plan", absolutePath);
+  });
+} else {
+  const docx = shared.loadPackage("docx");
+  const outputPath = args.output || ".docs/plan/plan.docx";
+  const children = [
+    new docx.Paragraph({
+      text: data.title || "Project Plan",
+      heading: docx.HeadingLevel.TITLE,
+    }),
+  ];
+
+  for (const phase of data.phases || []) {
+    children.push(
+      new docx.Paragraph({
+        text: String(phase.name || "Phase"),
+        heading: docx.HeadingLevel.HEADING_1,
+      })
+    );
+
+    children.push(...shared.toParagraphs(docx, phase.summary ? [phase.summary] : []));
+    children.push(...shared.toParagraphs(docx, phase.tasks, { bullet: true }));
+    children.push(...shared.toParagraphs(docx, phase.risks, { bullet: true }));
+  }
+
+  const document = new docx.Document({
+    sections: [{ children }],
+  });
+
+  docx.Packer.toBuffer(document).then((buffer) => {
+    const absolutePath = shared.writeBuffer(outputPath, buffer);
+    shared.writeSuccess("Plan", absolutePath);
+  });
+}
+`,E=`#!/usr/bin/env node
+
+const shared = require("./_shared.js");
+const ExcelJS = shared.loadPackage("exceljs");
+
+const args = shared.parseArgs(process.argv.slice(2));
+const inputPath = args.input || ".agentic/workspace/documents/tasks.json";
+const outputPath = args.output || ".docs/tasks/tasks.xlsx";
+const data = shared.readJsonFile(inputPath);
+
+const workbook = new ExcelJS.Workbook();
+const worksheet = workbook.addWorksheet(data.sheetName || "Tasks");
+const rows = Array.isArray(data.rows) ? data.rows : [];
+
+worksheet.columns = Array.isArray(data.columns) && data.columns.length > 0
+  ? data.columns
+  : shared.deriveColumns(rows);
+
+for (const row of rows) {
+  worksheet.addRow(row);
+}
+
+worksheet.views = [{ state: "frozen", ySplit: 1 }];
+
+workbook.xlsx.writeBuffer().then((buffer) => {
+  const absolutePath = shared.writeBuffer(outputPath, buffer);
+  shared.writeSuccess("Tasks", absolutePath);
+});
+`,x={".agentic/workspace/scripts/README.md":`# Export Scripts
+
+This folder contains starter Node.js export helpers for deliverables in \`.docs/\`.
+
+These scripts are meant to be a starting point. The AI agent should update the relevant script for the current project when the user provides a template, a preferred structure, or custom formatting rules.
+
+## Included Starter Scripts
+
+- \`generate_brd.js\`
+- \`generate_frd.js\`
+- \`generate_estimate.js\`
+- \`generate_proposal.js\`
+- \`generate_plan.js\`
+- \`generate_tasks.js\`
+- \`_shared.js\`
+
+## Planned Libraries
+
+- \`docx\` for BRD, FRD, and document-style plan output
+- \`pptxgenjs\` for proposal decks
+- \`exceljs\` for estimate, tasks, and spreadsheet-style plan output
+
+## Install Strategy
+
+1. Check whether the target project root already has a usable Node environment.
+2. Prefer installing export dependencies 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\`.
+
+## Default Input Files
+
+The starter scripts read structured input from \`.agentic/workspace/documents/\` by default:
+
+- BRD: \`brd.json\`
+- FRD: \`frd.json\`
+- Estimate: \`estimate.json\`
+- Proposal: \`proposal.json\`
+- Plan: \`plan.json\`
+- Tasks: \`tasks.json\`
+
+The agent may also keep matching \`.md\` drafts beside these files for human-readable working content.
+
+## Default Outputs
+
+- 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\`
+
+## Usage Pattern
 
-When the proposal is complete enough for handoff, tell the user the v1 workflow is complete and list the generated files.
-`});async function T(e){await Promise.all(y.map(t=>A(u.join(e,t),{recursive:!0,force:!0})))}async function S(e){await Promise.all(x.map(t=>I(u.join(e,t),{recursive:!0})))}async function N(e){let t=v();await Promise.all(Object.entries(t).map(([o,r])=>E(u.join(e,o),r,"utf8")))}async function D(){let e=process.cwd();await T(e),await S(e),await N(e),await a(e,f,w,c,m),await a(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("")}D().catch(e=>{let t=e instanceof Error?e.message:String(e);console.error(`create-agentic-starter: failed to scaffold project. ${t}`),process.exitCode=1});
+1. Use the current prompt command to build the deliverable content.
+2. Save or update structured export input under \`.agentic/workspace/documents/\`.
+3. Adapt the relevant script if the project requires a custom template or style.
+4. Install the needed package only after user approval.
+5. Run the script from the project root.
+`,".agentic/workspace/scripts/_shared.js":I,".agentic/workspace/scripts/generate_brd.js":S,".agentic/workspace/scripts/generate_frd.js":A,".agentic/workspace/scripts/generate_estimate.js":R,".agentic/workspace/scripts/generate_proposal.js":q,".agentic/workspace/scripts/generate_plan.js":D,".agentic/workspace/scripts/generate_tasks.js":E};var y=()=>({...k,...w,...x});async function N(e){await Promise.all(d.map(t=>T(l.join(e,t),{recursive:!0,force:!0})))}async function B(e){await Promise.all(p.map(t=>F(l.join(e,t),{recursive:!0})))}async function C(e){let t=y();await Promise.all(Object.entries(t).map(([s,r])=>_(l.join(e,s),r,"utf8")))}async function M(){let e=process.cwd();await N(e),await B(e),await C(e),await m(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("")}M().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

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