create-agentic-starter 0.1.16 → 0.1.18

package/dist/index.js

@@ -1,12 +1,12 @@
 #!/usr/bin/env node
-import{mkdir as P,rm as D,writeFile as G}from"fs/promises";import g from"path";import{readFile as A,writeFile as f}from"fs/promises";import F from"path";function u(e){return e.replace(/[.*+?^${}()|[\]\\]/g,"\\$&")}function h(e,r,s,a){let c=new RegExp(`${u(s)}[\\s\\S]*?${u(a)}\\n?`,"m");if(c.test(e))return e.replace(c,`${r}
-`);let o=e.endsWith(`
+import{mkdir as D,rm as G,writeFile as v}from"fs/promises";import g from"path";import{readFile as R,writeFile as f}from"fs/promises";import h from"path";function w(t){return t.replace(/[.*+?^${}()|[\]\\]/g,"\\$&")}function A(t,r,a,s){let c=new RegExp(`${w(a)}[\\s\\S]*?${w(s)}\\n?`,"m");if(c.test(t))return t.replace(c,`${r}
+`);let o=t.endsWith(`
 `)?`
 `:`
 
-`;return`${e}${o}${r}
-`}async function E(e,r,s,a,c){let o=F.join(e,r);try{let i=await A(o,"utf8"),k=h(i,s,a,c);await f(o,k,"utf8")}catch(i){if(i.code!=="ENOENT")throw i;await f(o,`${s}
-`,"utf8")}}import{existsSync as y,readFileSync as $,realpathSync as w}from"fs";import n from"path";import{fileURLToPath as M}from"url";function t(e){let r=[n.dirname(w(M(import.meta.url))),process.argv[1]?n.dirname(w(process.argv[1])):null,process.argv[1]?n.dirname(n.resolve(process.argv[1])):null].filter(s=>!!s);for(let s of r){let a=n.join(s,e);if(y(a))return $(a,"utf8")}throw new Error(`Template not found: ${e}. Checked: ${r.join(", ")}`)}var T="AGENTS.md",m="<!-- from create-agentic-starter:agents:start -->",p="<!-- from create-agentic-starter:agents:end -->",N=t("./templates/meta/agents.md").trimEnd(),j=`${m}
-${N}
+`;return`${t}${o}${r}
+`}async function u(t,r,a,s,c){let o=h.join(t,r);try{let i=await R(o,"utf8"),F=A(i,a,s,c);await f(o,F,"utf8")}catch(i){if(i.code!=="ENOENT")throw i;await f(o,`${a}
+`,"utf8")}}import{existsSync as M,readFileSync as $,realpathSync as E}from"fs";import n from"path";import{fileURLToPath as N}from"url";function e(t){let r=[n.dirname(E(N(import.meta.url))),process.argv[1]?n.dirname(E(process.argv[1])):null,process.argv[1]?n.dirname(n.resolve(process.argv[1])):null].filter(a=>!!a);for(let a of r){let s=n.join(a,t);if(M(s))return $(s,"utf8")}throw new Error(`Template not found: ${t}. Checked: ${r.join(", ")}`)}var j="AGENTS.md",m="<!-- from create-agentic-starter:agents:start -->",p="<!-- from create-agentic-starter:agents:end -->",P=e("./templates/meta/agents.md").trimEnd(),x=`${m}
+${P}
 ${p}
-`;var x={".agentic/commands/project-requirements.md":t("./templates/commands/project-requirements.md"),".agentic/commands/architecture.md":t("./templates/commands/architecture.md"),".agentic/commands/create-brd.md":t("./templates/commands/create-brd.md"),".agentic/commands/create-frd.md":t("./templates/commands/create-frd.md"),".agentic/commands/create-estimate.md":t("./templates/commands/create-estimate.md"),".agentic/commands/create-proposal.md":t("./templates/commands/create-proposal.md"),".agentic/commands/create-plan.md":t("./templates/commands/create-plan.md"),".agentic/commands/create-tasks.md":t("./templates/commands/create-tasks.md")};var _={".agentic/init.md":t("./templates/core/init.md"),".agentic/context.md":t("./templates/core/context.md")};var l=[".agentic"],d=[".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 S={".agentic/workspace/scripts/README.md":t("./templates/scripts/README.md"),".agentic/workspace/scripts/_shared.js":t("./templates/scripts/_shared.js"),".agentic/workspace/scripts/generate_brd.js":t("./templates/scripts/generate_brd.js"),".agentic/workspace/scripts/generate_frd.js":t("./templates/scripts/generate_frd.js"),".agentic/workspace/scripts/generate_estimate.js":t("./templates/scripts/generate_estimate.js"),".agentic/workspace/scripts/generate_proposal.js":t("./templates/scripts/generate_proposal.js"),".agentic/workspace/scripts/generate_plan.js":t("./templates/scripts/generate_plan.js"),".agentic/workspace/scripts/generate_tasks.js":t("./templates/scripts/generate_tasks.js")};var R=()=>({..._,...x,...S});async function O(e){await Promise.all(l.map(r=>D(g.join(e,r),{recursive:!0,force:!0})))}async function v(e){await Promise.all(d.map(r=>P(g.join(e,r),{recursive:!0})))}async function I(e){let r=R();await Promise.all(Object.entries(r).map(([s,a])=>G(g.join(e,s),a,"utf8")))}async function b(){let e=process.cwd();await O(e),await v(e),await I(e),await E(e,T,j,m,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("")}b().catch(e=>{let r=e instanceof Error?e.message:String(e);console.error(`create-agentic-starter: failed to scaffold project. ${r}`),process.exitCode=1});
+`;var T={".agentic/commands/project-requirements.md":e("./templates/commands/project-requirements.md"),".agentic/commands/architecture.md":e("./templates/commands/architecture.md"),".agentic/commands/create-brd.md":e("./templates/commands/create-brd.md"),".agentic/commands/create-frd.md":e("./templates/commands/create-frd.md"),".agentic/commands/create-estimate.md":e("./templates/commands/create-estimate.md"),".agentic/commands/create-proposal.md":e("./templates/commands/create-proposal.md"),".agentic/commands/create-plan.md":e("./templates/commands/create-plan.md"),".agentic/commands/create-tasks.md":e("./templates/commands/create-tasks.md")};var k={".agentic/init.md":e("./templates/core/init.md"),".agentic/context.md":e("./templates/core/context.md")};var d=[".agentic"],l=[".agentic",".agentic/commands",".agentic/workspace",".agentic/workspace/project",".agentic/workspace/memory",".agentic/workspace/memory/features",".agentic/workspace/documents",".agentic/workspace/scripts",".docs",".docs/brd",".docs/frd",".docs/estimate",".docs/proposal",".docs/plan",".docs/tasks"];var y={".agentic/workspace/memory/project-state.md":e("./templates/memory/project-state.md"),".agentic/workspace/memory/decisions.md":e("./templates/memory/decisions.md"),".agentic/workspace/memory/next-actions.md":e("./templates/memory/next-actions.md"),".agentic/workspace/memory/handoff.md":e("./templates/memory/handoff.md")};var _={".agentic/workspace/scripts/README.md":e("./templates/scripts/README.md"),".agentic/workspace/scripts/_shared.js":e("./templates/scripts/_shared.js"),".agentic/workspace/scripts/generate_brd.js":e("./templates/scripts/generate_brd.js"),".agentic/workspace/scripts/generate_frd.js":e("./templates/scripts/generate_frd.js"),".agentic/workspace/scripts/generate_estimate.js":e("./templates/scripts/generate_estimate.js"),".agentic/workspace/scripts/generate_proposal.js":e("./templates/scripts/generate_proposal.js"),".agentic/workspace/scripts/generate_plan.js":e("./templates/scripts/generate_plan.js"),".agentic/workspace/scripts/generate_tasks.js":e("./templates/scripts/generate_tasks.js")};var S=()=>({...k,...T,...y,..._});async function O(t){await Promise.all(d.map(r=>G(g.join(t,r),{recursive:!0,force:!0})))}async function I(t){await Promise.all(l.map(r=>D(g.join(t,r),{recursive:!0})))}async function b(t){let r=S();await Promise.all(Object.entries(r).map(([a,s])=>v(g.join(t,a),s,"utf8")))}async function C(){let t=process.cwd();await O(t),await I(t),await b(t),await u(t,j,x,m,p),console.log("create-agentic-starter: ready"),console.log("Next: Start a new chat with @.agentic/init.md")}C().catch(t=>{let r=t instanceof Error?t.message:String(t);console.error(`create-agentic-starter: failed to scaffold project. ${r}`),process.exitCode=1});

package/dist/templates/commands/architecture.md

@@ -20,6 +20,12 @@ Read:
 8. Ask only the minimum blocking questions.
 9. If the user directly asks for a downstream deliverable and the architecture context is already sufficient, let them continue there instead of forcing this step to repeat.
 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/`.
+11. Memory capture is always on for this step. Update:
+   - `.agentic/workspace/memory/architecture.md`
+   - `.agentic/workspace/memory/decisions.md` for major technical choices
+   - `.agentic/workspace/memory/project-state.md`
+   - `.agentic/workspace/memory/handoff.md`
+12. If architecture work affects a specific feature, update the matching file under `.agentic/workspace/memory/features/`.
 
 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.
 

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

@@ -24,6 +24,12 @@ Read:
 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.
 14. If the user explicitly asked for this BRD work, continue it directly using the existing workspace context instead of routing them backward.
+15. Memory capture is always on for this step. Update:
+   - `.agentic/workspace/memory/project-state.md`
+   - `.agentic/workspace/memory/handoff.md`
+   - `.agentic/workspace/memory/next-actions.md` if follow-up work remains
+   - `.agentic/workspace/memory/decisions.md` if this step creates a meaningful product or technical decision
+16. If this BRD work materially affects one or more features, update the matching feature files under `.agentic/workspace/memory/features/`.
 
 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:
 

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

@@ -26,6 +26,12 @@ Read:
 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.
 15. If the user explicitly asked for this estimate work, continue it directly using the existing workspace context instead of routing them backward.
+16. Memory capture is always on for this step. Update:
+   - `.agentic/workspace/memory/project-state.md`
+   - `.agentic/workspace/memory/handoff.md`
+   - `.agentic/workspace/memory/next-actions.md` if follow-up work remains
+   - `.agentic/workspace/memory/decisions.md` if this step creates a meaningful product or technical decision
+17. If this estimate work materially affects one or more features, update the matching feature files under `.agentic/workspace/memory/features/`.
 
 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:
 

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

@@ -24,6 +24,12 @@ Read:
 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.
 13. If the user explicitly asked for this FRD work, continue it directly using the existing workspace context instead of routing them backward.
+14. Memory capture is always on for this step. Update:
+   - `.agentic/workspace/memory/project-state.md`
+   - `.agentic/workspace/memory/handoff.md`
+   - `.agentic/workspace/memory/next-actions.md` if follow-up work remains
+   - `.agentic/workspace/memory/decisions.md` if this step creates a meaningful product or technical decision
+15. If this FRD work materially affects one or more features, update the matching feature files under `.agentic/workspace/memory/features/`.
 
 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:
 

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

@@ -29,6 +29,12 @@ Read:
 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.
 15. If the user explicitly asked for this plan work, continue it directly using the existing workspace context instead of routing them backward.
+16. Memory capture is always on for this step. Update:
+   - `.agentic/workspace/memory/project-state.md`
+   - `.agentic/workspace/memory/handoff.md`
+   - `.agentic/workspace/memory/next-actions.md` if follow-up work remains
+   - `.agentic/workspace/memory/decisions.md` if this step creates a meaningful product or technical decision
+17. If this plan work materially affects one or more features, update the matching feature files under `.agentic/workspace/memory/features/`.
 
 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.
 

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

@@ -25,5 +25,11 @@ Read:
 11. If key proposal inputs are still missing, ask focused questions and keep improving the proposal instead of prematurely declaring completion.
 12. Ask only the minimum blocking questions.
 13. If the user explicitly asked for this proposal work, continue it directly using the existing workspace context instead of routing them backward.
+14. Memory capture is always on for this step. Update:
+   - `.agentic/workspace/memory/project-state.md`
+   - `.agentic/workspace/memory/handoff.md`
+   - `.agentic/workspace/memory/next-actions.md` if follow-up work remains
+   - `.agentic/workspace/memory/decisions.md` if this step creates a meaningful product or technical decision
+15. If this proposal work materially affects one or more features, update the matching feature files under `.agentic/workspace/memory/features/`.
 
 When the proposal is complete enough for handoff, tell the user the workflow is complete and list the generated files.

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

@@ -27,6 +27,12 @@ Read:
 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 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.
+15. Memory capture is always on for this step. Update:
+   - `.agentic/workspace/memory/project-state.md`
+   - `.agentic/workspace/memory/handoff.md`
+   - `.agentic/workspace/memory/next-actions.md` if follow-up work remains
+   - `.agentic/workspace/memory/decisions.md` if this step creates a meaningful product or technical decision
+16. If this task work materially affects one or more features, update the matching feature files under `.agentic/workspace/memory/features/`.
 
 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.
 

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

@@ -27,6 +27,13 @@ Read:
 10. Only ask for missing details that block useful requirement understanding.
 11. If the user has already asked for a later deliverable and the existing context is sufficient, acknowledge that and let them move there instead of forcing this step.
 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/`.
+13. Memory capture is always on for this step. Update:
+   - `.agentic/workspace/memory/project-overview.md`
+   - `.agentic/workspace/memory/requirements.md`
+   - `.agentic/workspace/memory/open-questions.md`
+   - `.agentic/workspace/memory/project-state.md`
+   - `.agentic/workspace/memory/handoff.md`
+14. If this step introduces or refines a specific feature, create or update the matching file under `.agentic/workspace/memory/features/`.
 
 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.
 

package/dist/templates/core/context.md

@@ -37,6 +37,11 @@ Use `.agentic/workspace/memory/` for:
 - `requirements.md`
 - `open-questions.md`
 - `architecture.md`
+- `project-state.md`
+- `decisions.md`
+- `next-actions.md`
+- `handoff.md`
+- `features/` for one file per feature or workstream
 - assumptions and structured working memory
 
 ### Internal Documents
@@ -88,11 +93,15 @@ Use `.docs/` for user-facing deliverables:
 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. In a fresh chat, treat existing memory files and existing outputs as the primary source of truth for resume behavior.
-7. Do not restart basic intake if the workspace already contains strong memory unless the existing information is clearly incomplete or contradictory.
-8. If the user directly asks for a specific deliverable or command, follow that request when enough context already exists.
-9. Prefer the target project root for Node-based export dependencies when a usable Node setup already exists there.
-10. If root is not suitable, ask the user which path should be used for dependency installation.
-11. Ask the user before running any install command.
-12. Ask only the minimum blocking questions required to continue.
-13. Always end by telling the user the exact next command to run or listing the available next options.
+6. Treat `.agentic/workspace/memory/` as the canonical shared project memory across tools and sessions.
+7. Do not rely on tool-local memory paths such as `~/.codex/...` as the primary source of truth.
+8. Store outcomes, decisions, feature state, blockers, handoff notes, and next actions instead of raw chat transcripts.
+9. In a fresh chat, treat existing memory files and existing outputs as the primary source of truth for resume behavior.
+10. Do not restart basic intake if the workspace already contains strong memory unless the existing information is clearly incomplete or contradictory.
+11. If the user directly asks for a specific deliverable, feature discussion, or implementation task and enough context already exists, do the work and capture the outcome automatically in the relevant memory files.
+12. Update only the memory files affected by the current work instead of rewriting everything.
+13. Prefer the target project root for Node-based export dependencies when a usable Node setup already exists there.
+14. If root is not suitable, ask the user which path should be used for dependency installation.
+15. Ask the user before running any install command.
+16. Ask only the minimum blocking questions required to continue.
+17. Always end by telling the user the exact next command to run or listing the available next options.

package/dist/templates/core/init.md

@@ -33,39 +33,45 @@ You are starting a fresh AI session inside this project. Your job is to quickly
    - root-level signals
    - existing workspace files
    - the user's message in this chat
-4. If `project-overview.md`, `requirements.md`, `architecture.md`, internal drafts, or user-facing outputs already exist, treat this as an in-progress workspace and resume from what is already known.
-5. In resumed sessions:
+4. Treat repo memory under `.agentic/workspace/memory/` as the shared source of truth across tools and sessions.
+5. If `project-overview.md`, `requirements.md`, `architecture.md`, `project-state.md`, internal drafts, or user-facing outputs already exist, treat this as an in-progress workspace and resume from what is already known.
+6. In resumed sessions:
    - give a short summary of what is already understood
+   - summarize current project state, active features, blockers, and next actions when that information exists
    - mention only the most important missing or uncertain pieces
    - do not ask basic project questions again unless the existing memory is clearly incomplete, contradictory, or missing a blocking detail
    - if the user adds new context, update the relevant memory files before suggesting what to do next
    - suggest valid next commands based on the current progress instead of forcing `@.agentic/commands/project-requirements.md`
-6. If the user directly asks to create or continue a specific deliverable and the existing context is sufficient, follow that request instead of routing them back through the recommended sequence.
-7. If project context is still thin, ask a small number of targeted questions about:
+7. Memory capture is always on. Do not require a separate memory-capture prompt to store useful project information.
+8. If the user directly asks to create, continue, or implement something and the existing context is sufficient, follow that request instead of routing them back through the recommended sequence.
+9. If project context is still 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
-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:
+10. 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.
+11. If enough context exists, give a short summary of the project and the most important missing pieces.
+12. 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.
+13. 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`
-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:
+   - `.agentic/workspace/memory/project-state.md`
+   - `.agentic/workspace/memory/handoff.md`
+14. Update `.agentic/workspace/memory/architecture.md` only if the new context changes architecture.
+15. If the user is discussing a specific feature, create or update a feature file under `.agentic/workspace/memory/features/` using kebab-case naming and include: feature name, current status, summary, requirements, implementation notes, dependencies, blockers, decisions affecting the feature, related docs, and next steps.
+16. Write drafts even from partial information.
+17. Clearly separate confirmed facts, assumptions, and open questions.
+18. Do not route immediately just because the workspace is empty. Do useful synthesis or ask focused questions first.
+19. Do not rewrite unrelated files just because `@.agentic/init.md` ran.
+20. If important project basics are still missing, continue asking focused questions and keep updating the memory files instead of routing forward yet.
+21. 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`
-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:
+22. 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/memory/decisions.md

@@ -0,0 +1,11 @@
+# Decisions
+
+Use this file to capture important product and technical decisions.
+
+## Decision Log
+
+### YYYY-MM-DD - Decision Title
+
+- Decision:
+- Reason:
+- Impact:

package/dist/templates/memory/handoff.md

@@ -0,0 +1,10 @@
+# Handoff
+
+Use this file to help the next session or next tool continue the work.
+
+## Latest Summary
+
+- What happened:
+- What changed:
+- What remains open:
+- Where to continue next:

package/dist/templates/memory/next-actions.md

@@ -0,0 +1,7 @@
+# Next Actions
+
+Use this file as the short actionable queue for the next agent or teammate.
+
+## Current Queue
+
+- [ ] Add the next action here

package/dist/templates/memory/project-state.md

@@ -0,0 +1,29 @@
+# Project State
+
+## Current Phase
+
+- Not set yet
+
+## Current Priorities
+
+- Add the current top priorities here
+
+## In Progress
+
+- Add active workstreams or features here
+
+## Completed Outputs
+
+- Add completed BRD, FRD, estimate, proposal, plan, tasks, or other deliverables here
+
+## Active Features
+
+- Add links or references to feature files under `features/`
+
+## Blockers
+
+- Add current blockers here
+
+## Suggested Next Actions
+
+- Add the next recommended actions here

package/dist/templates/meta/agents.md

@@ -45,6 +45,8 @@ Use this scaffold when you want an AI tool to:
 
 If a workspace already contains memory and document progress, `@.agentic/init.md` should summarize what is already known, update memory with any new context from the user, and let the user continue from the relevant next step instead of restarting the full sequence.
 
+Memory capture is automatic during normal work. Users do not need to run a separate prompt just to store project context.
+
 ## Output Conventions
 
 Default user-facing outputs live under `.docs/`:
@@ -76,4 +78,10 @@ Planned library stack:
 - `pptxgenjs`
 - `exceljs`
 
+## Shared Memory
+
+`.agentic/workspace/memory/` is the shared project memory layer across tools such as Codex, Claude, Cursor, Antigravity, and others.
+
+Use repo memory as the source of truth instead of tool-local memory paths or raw chat history.
+
 If your tool does not support `@file` references, paste the contents of the prompt file into a new chat manually.

package/package.json

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