ros/spec-kit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Clarify Codex-specific README note with rationale for its different workflow.

Browse Source
This commit is contained in:
honjo-hiroaki-gtt
2025-09-19 16:40:41 +09:00
parent 286ad553fd
commit 312703260c
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@@ -224,9 +224,9 @@ specify init <project_name> --ai claude --ignore-agent-tools
> [!NOTE] > [!NOTE]
> Codex CLI specifics > Codex CLI specifics
> - When you run `specify init --ai codex`, the CLI ensures a `commands/` directory exists. If packaged templates are not available, it bootstraps minimal command files (`specify.md`, `plan.md`, `tasks.md`). > - Codex CLI loads slash commands from the project workspace instead of from an IDE bundle, so `specify init --ai codex` creates a `commands/` directory (and seeds `specify.md`, `plan.md`, `tasks.md` if templates are missing) to match that expectation.
> - Codex reads project memory from `AGENTS.md`. If it does not exist yet, run `codex /init` inside the project. > - 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.
> - To allow the bundled scripts under `scripts/` to run from Codex slash commands, open `codex /approvals` and enable “Run shell commands”. > - To let Codex trigger the helper scripts under `scripts/` through slash commands, open `codex /approvals` and enable “Run shell commands”.
### **STEP 1:** Bootstrap the project ### **STEP 1:** Bootstrap the project