💫 Toolkit to help you get started with SDD or any other process!
Update config
Den Delimarsky 🌺d7d2c145c7c6
diff --git a/README.md b/README.mdindex 3680be7a5..b2dbca540 100644--- a/README.md+++ b/README.md@@ -262,14 +262,6 @@ The CLI will check if you have Claude Code, Gemini CLI, Cursor CLI, Qwen CLI, opspecify init <project_name> --ai claude --ignore-agent-tools```-> [!NOTE]-> Codex CLI specifics-> - `specify init --ai codex` seeds `commands/*.md` in your repo and automatically mirrors them into `${CODEX_HOME:-~/.codex}/prompts` so Codex picks up `/specify`, `/plan`, and `/tasks` immediately.-> - If Codex was running during installation, restart the CLI once so it reloads the refreshed slash commands.-> - Codex persists its working memory in `AGENTS.md`; if you do not see that file yet, run `codex /init` once inside the project to generate it.-> - When Codex is configured to run helper scripts, open `codex /approvals` and enable “Run shell commands”.-> - If you point `CODEX_HOME` at the project (for per-repo isolation) the installer adds ignore rules for Codex session artifacts to `.gitignore`; adjust them as needed for your workflow.-### **STEP 1:** Establish project principlesGo to the project folder and run your AI agent. In our example, we're using `claude`.diff --git a/templates/commands/plan.md b/templates/commands/plan.mdindex 6315d0ee8..18a0b5c64 100644--- a/templates/commands/plan.md+++ b/templates/commands/plan.md@@ -14,10 +14,10 @@ Given the implementation details provided as an argument, do this:- Success criteria and acceptance criteria- Any technical constraints or dependencies mentioned-3. Read the constitution at `memory/constitution.md` to understand constitutional requirements.+3. Read the constitution at `/memory/constitution.md` to understand constitutional requirements.4. Execute the implementation plan template:- - Load `templates/plan-template.md` (already copied to IMPL_PLAN path)+ - Load `/templates/plan-template.md` (already copied to IMPL_PLAN path)- Set Input path to FEATURE_SPEC- Run the Execution Flow (main) function steps 1-9- The template is self-contained and executablediff --git a/templates/commands/specify.md b/templates/commands/specify.mdindex 8544b3f21..9a6a3b361 100644--- a/templates/commands/specify.md+++ b/templates/commands/specify.md@@ -5,7 +5,7 @@ scripts:ps: scripts/powershell/create-new-feature.ps1 -Json "{ARGS}"----The text the user typed after `/specify` in the triggering message **is** the feature description. Assume you always have it available in this conversation even if `{ARGS}` appears literally below. Do not ask the user to repeat it unless they provided a truly empty command.+The text the user typed after `/specify` in the triggering message **is** the feature description. Assume you always have it available in this conversation even if `{ARGS}` appears literally below. Do not ask the user to repeat it unless they provided an empty command.Given that feature description, do this:diff --git a/templates/commands/tasks.md b/templates/commands/tasks.mdindex fe89b9581..29b4cd25e 100644--- a/templates/commands/tasks.md+++ b/templates/commands/tasks.md@@ -21,7 +21,7 @@ Given the context provided as an argument, do this:- Generate tasks based on what's available3. Generate tasks following the template:- - Use `templates/tasks-template.md` as the base+ - Use `/templates/tasks-template.md` as the base- Replace example tasks with actual tasks based on:* **Setup tasks**: Project init, dependencies, linting* **Test tasks [P]**: One per contract, one per integration scenario