thachvd-kit 1.0.27 → 1.0.28

package/.agent/docs/getting-started.md

@@ -2,9 +2,20 @@
 
 Read this after `thachvd-kit init`. The kit gives every member one entry point, then selects only the process and expertise the task needs.
 
-## Start Every Task With /task
+## Client Command Map
 
-Use `/task <request>` before editing whenever the route is not already obvious. It must produce:
+| Client | Task router | Simple fix | Bug fix | Feature spec | Release |
+|---|---|---|---|---|---|
+| Codex | `/prompts:task` | `/prompts:simple` | `/prompts:debug` | `/prompts:spec` | `/prompts:release` |
+| Antigravity | `/task` | `/simple` | `/debug` | `/spec` | `/release` |
+| Claude Code | `/task` | `/simple` | `/debug` | `/spec` | `/release` |
+| Cursor | `/task` | `/simple` | `/debug` | `/spec` | `/release` |
+
+Codex reads custom prompts from `~/.codex/prompts`. Antigravity reads workspace workflows from `.agent/workflows`. Claude Code reads project skills from `.claude/skills/<name>/SKILL.md`. Cursor reads commands from `.cursor/commands`.
+
+## Start Every Task With The Router
+
+In Codex, use `/prompts:task <request>` before editing whenever the route is not already obvious. Other clients can read `.agent/workflows/task.md` directly. It must produce:
 
 ```text
 ROUTE: question | simple | feature | bug | review | release | multi-domain
@@ -22,22 +33,22 @@ A workflow is the process and its gates. A skill is the method or checklist. An
 | Situation | Command | Gate | Required next step |
 |---|---|---|---|
 | Explain, inspect, or brainstorm only | direct answer or `/brainstorm` | none | no code until the request becomes actionable |
-| One obvious local fix | `/simple <request>` | fast-path | inspect -> edit -> focused verify |
-| New behavior, multi-file change, unclear scope, or >~30 min | `/task` -> `/brainstorm` -> `/spec` when needed -> `/plan` | standard | wait for approval before implementation |
-| Bug, regression, failing test, or unknown error | `/debug <symptom>` | bug | reproduce -> isolate -> regression test -> fix -> verify |
+| One obvious local fix | `/prompts:simple <request>` in Codex | fast-path | inspect -> edit -> focused verify |
+| New behavior, multi-file change, unclear scope, or >~30 min | `/prompts:task` -> `/brainstorm` -> `/prompts:spec` when needed -> `/plan` | standard | wait for approval before implementation |
+| Bug, regression, failing test, or unknown error | `/prompts:debug <symptom>` in Codex | bug | reproduce -> isolate -> regression test -> fix -> verify |
 | Pre-merge or independent review | `/review` | review | five-axis review; resolve blocking findings |
-| Version, tag, npm publish, or deployment | `/release` | release | release checklist; never fast-path |
+| Version, tag, npm publish, or deployment | `/prompts:release` in Codex | release | release checklist; never fast-path |
 | Frontend + backend + data/security together | `/orchestrate` | standard | plan -> approval -> specialist work -> integration verify |
 
 ## Standard Feature Flow
 
-The gated sequence is Spec -> Plan -> Implement -> Review: `/task` -> `/brainstorm` -> `/spec` when scope is ambiguous or multi-file -> `/plan` -> user approves the plan -> implementation -> `/test` -> `/review` -> final verification -> commit/push.
+The gated sequence is Spec -> Plan -> Implement -> Review: `/prompts:task` -> `/brainstorm` -> `/prompts:spec` when scope is ambiguous or multi-file -> `/plan` -> user approves the plan -> implementation -> `/test` -> `/review` -> final verification -> commit/push.
 
 The plan is a gate, not a suggestion. Do not start product-code implementation before explicit approval. Load only the relevant specialist agent and skills, such as `$frontend-design`, `$api-design`, or `$webapp-testing`.
 
 ## Bug Fix Flow
 
-Use `/debug <symptom>`, not the feature flow, when something is failing or the root cause is unknown:
+Use Codex `/prompts:debug <symptom>`, not the feature flow, when something is failing or the root cause is unknown:
 
 1. Capture the exact symptom, environment, reproduction, and expected result.
 2. Inspect the relevant code path with MCP/codegraph when available.
@@ -51,7 +62,7 @@ Load `$systematic-debugging`, the `debugger` agent, and `testing-patterns` for t
 
 ## Simple Fast Path
 
-Use `/simple <request>` only when the change is one obvious file, the result is unambiguous, and it changes no behavior, API, schema, security, CI, dependency, workflow, or release contract. Before editing, state:
+Use Codex `/prompts:simple <request>` only when the change is one obvious file, the result is unambiguous, and it changes no behavior, API, schema, security, CI, dependency, workflow, or release contract. Before editing, state:
 
 ```text
 FAST_PATH: simple-fix
@@ -59,18 +70,18 @@ REASON: [why Spec/Plan/Review are not needed]
 SCOPE: [file or narrow area]
 ```
 
-This bypasses only Spec, Plan, and the feature/refactor Review gate. It never bypasses inspection, focused verification, or reporting evidence. If the scope expands, stop and re-route with `/task`.
+This bypasses only Spec, Plan, and the feature/refactor Review gate. It never bypasses inspection, focused verification, or reporting evidence. If the scope expands, stop and re-route with Codex `/prompts:task`.
 
 ## Command And Skill Map
 
 - `/brainstorm`: clarify intent and tradeoffs; no code.
-- `/spec`: define requirements and acceptance criteria; no code.
+- Codex `/prompts:spec`: define requirements and acceptance criteria; no code.
 - `/plan`: create an approved implementation plan; no code before approval.
 - `/enhance` or `/create`: implement an approved feature with the relevant specialist agent.
-- `/debug`: systematic root-cause investigation and regression protection.
+- Codex `/prompts:debug`: systematic root-cause investigation and regression protection.
 - `/test`: add or run tests and assess coverage.
 - `/review`: five-axis review before completion or merge.
-- `/release`: verify, version, tag, publish, and verify npm output.
+- Codex `/prompts:release`: verify, version, tag, publish, and verify npm output.
 - `$clean-code` and `$verification-before-completion`: default implementation hygiene.
 - `$webapp-testing`: browser/UI verification; use Playwright when available.
 

package/.agent/docs/workflow.md

@@ -4,7 +4,7 @@
 
 1. Read AGENTS.md.
 2. Read .agent/docs/project.md.
-3. Route the request with `/task <request>` when the path is not obvious.
+3. Route the request with Codex `/prompts:task <request>` when the path is not obvious; otherwise read `.agent/workflows/task.md` directly.
 4. Read only the relevant docs under .agent/agents, .agent/skills, .claude/skills, and .agent/workflows.
 5. Check if MCP servers (like `codegraph`) are active/available and prioritize using them as the primary entry point to search and locate files, symbols, and code blocks.
 
@@ -13,11 +13,11 @@
 | Situation | Command | Workflow / gate |
 |---|---|---|
 | Question or analysis only | direct answer | no edits |
-| One obvious local fix | `/simple` | `.agent/workflows/simple.md`, fast-path |
-| Bug, regression, failing test, or unknown error | `/debug` | `.agent/workflows/debug.md`, evidence-first |
-| New behavior, multi-file change, or unclear scope | `/brainstorm` -> `/spec` when needed -> `/plan` | spec/plan approval -> implement -> review |
+| One obvious local fix | Codex `/prompts:simple` | `.agent/workflows/simple.md`, fast-path |
+| Bug, regression, failing test, or unknown error | Codex `/prompts:debug` | `.agent/workflows/debug.md`, evidence-first |
+| New behavior, multi-file change, or unclear scope | `/brainstorm` -> Codex `/prompts:spec` when needed -> `/plan` | spec/plan approval -> implement -> review |
 | Pre-merge review | `/review` | `.agent/workflows/review.md`, five-axis |
-| npm version, tag, publish, or deployment | `/release` | `.agent/workflows/release.md`, release gate |
+| npm version, tag, publish, or deployment | Codex `/prompts:release` | `.agent/workflows/release.md`, release gate |
 | Several specialist domains | `/orchestrate` | plan -> approval -> parallel work -> integration verify |
 
 If a task is not clearly simple, use the standard flow. Never use the fast path for behavior, API, schema, security, CI, dependency, workflow, or release changes.
@@ -35,7 +35,7 @@ If a task is not clearly simple, use the standard flow. Never use the fast path
 
 ## Implementation Flow
 
-For `/simple` fixes, state the fast-path decision before editing:
+For Codex `/prompts:simple` fixes, state the fast-path decision before editing:
 
 ```text
 FAST_PATH: simple-fix
@@ -52,7 +52,7 @@ Then:
 5. Run verification (prioritize using Playwright MCP for web/UI changes to automate verification and capture screenshots).
 6. Summarize changed files and verification evidence.
 
-For bugs, use `/debug` with `$systematic-debugging`, the `debugger` agent, and `testing-patterns`: reproduce, isolate the root cause, add regression protection, make the smallest fix, and verify.
+For bugs, use Codex `/prompts:debug` with `$systematic-debugging`, the `debugger` agent, and `testing-patterns`: reproduce, isolate the root cause, add regression protection, make the smallest fix, and verify.
 
 For features or refactors, this flow runs *inside* the gated flow defined in AGENTS.md (spec -> plan -> implement -> review) — steps 3-5 above are the "Implement" phase, and step 6 is not a substitute for the mandatory `.agent/workflows/review.md` gate.
 
@@ -60,7 +60,7 @@ For features or refactors, this flow runs *inside* the gated flow defined in AGE
 
 A feature/refactor task is only complete when all of the following hold — not when code compiles or tests pass:
 
-The Spec checkbox may be skipped only when the documented `/simple` fast-path protocol is stated and its criteria are met.
+The Spec checkbox may be skipped only when the documented Codex `/prompts:simple` fast-path protocol is stated and its criteria are met.
 
 - [ ] `.agent/workflows/spec.md` exit criteria met (or explicitly skipped as a trivial/self-contained change)
 - [ ] `.agent/workflows/plan.md` produced a plan file, approved by the user

package/.agent/rules/GEMINI.md

@@ -30,6 +30,7 @@ Load only the agent, skill, or workflow files relevant to the current task.
 ## Execution
 
 - Route every task before editing. Use `/task <request>` when the correct path is not obvious.
+- Workspace workflows are available as `/task`, `/simple`, `/debug`, `/spec`, and `/release` from `.agent/workflows/`.
 - Questions and analysis: answer directly; do not edit code.
 - Simple fix: use `/simple <request>` only for one-file, unambiguous changes with no behavior or contract change.
 - Bug or failing behavior: use `/debug <symptom>` and follow the evidence-first root-cause flow.

package/.agent/workflows/simple.md

@@ -6,6 +6,8 @@ description: Fast path for one-file, unambiguous fixes with no behavior or share
 
 $ARGUMENTS
 
+Codex UI command: `/prompts:simple`. The `/simple` name below describes the workflow; it is not a built-in Codex slash command.
+
 ## Use Only When
 
 - The change is limited to one obvious file or one tiny local edit.

package/.agent/workflows/task.md

@@ -6,6 +6,8 @@ description: Route every task to the smallest safe workflow, fast path, bug flow
 
 $ARGUMENTS
 
+Codex UI command: `/prompts:task`. The `/task` name below describes the workflow; it is not a built-in Codex slash command.
+
 ## Purpose
 
 Use `/task` at the start of a task when you are unsure which workflow, skill, or specialist agent applies. This command routes the request before implementation.

package/README.md

@@ -60,37 +60,48 @@ Skills work best through progressive disclosure: the agent should first see skil
 - Keep `.agent/skills` as the complete shared source from the kit.
 - Let `thachvd-kit` copy selected skills to `~/.codex/skills/` for Codex and `.claude/skills` for Claude Code.
 - Make every `SKILL.md` frontmatter `description` specific: include when to use it, trigger phrases, and boundaries.
-- Run `thachvd-kit --help` to see a compact workflow guide without adding that guidance to every agent context. It recommends when to use `/task`, `/simple`, `/brainstorm`, `/plan`, `/create`, `/enhance`, `/debug`, `/test`, `/preview`, `/deploy`, `/review`, `/release`, `/status`, and `/orchestrate`.
+- Run `thachvd-kit --help` to see a compact workflow guide. In Codex, custom prompts appear as `/prompts:task`, `/prompts:simple`, `/prompts:debug`, `/prompts:spec`, and `/prompts:release` after `init` and a Codex restart. Built-in commands such as `/plan` and `/review` remain unchanged.
 - Use explicit prompts when implicit matching misses, for example `Use $webapp-testing to verify this UI` or `Use $clean-code before refactoring`.
 - Restart Codex or Claude Code if a newly copied or edited skill does not appear.
 
 ## Development Workflow
 
-After install, every AI client starts at `/task <request>` when the route is not already obvious. `/task` selects the smallest safe workflow and the relevant skills/agents; it does not force the full feature gate onto every request.
+After install, every AI client starts at the task router when the route is not already obvious. In Codex, use `/prompts:task <request>`; other clients can read `.agent/workflows/task.md` directly. The router selects the smallest safe workflow and relevant skills/agents; it does not force the full feature gate onto every request.
+
+### Client Commands
+
+| Client | Router | Fast path | Bug flow | Feature spec | Release |
+|---|---|---|---|---|---|
+| Codex | `/prompts:task` | `/prompts:simple` | `/prompts:debug` | `/prompts:spec` | `/prompts:release` |
+| Antigravity | `/task` | `/simple` | `/debug` | `/spec` | `/release` |
+| Claude Code | `/task` | `/simple` | `/debug` | `/spec` | `/release` |
+| Cursor | `/task` | `/simple` | `/debug` | `/spec` | `/release` |
+
+`init` installs these from the same source: Codex prompts in `~/.codex/prompts`, Antigravity workflows in `.agent/workflows`, Claude Code skills in `.claude/skills`, and Cursor commands in `.cursor/commands`. Restart or reload the client after the first installation if commands do not appear.
 
 | Situation | Command | Required flow |
 |---|---|---|
 | Question or analysis | direct answer | no edits |
-| One obvious local fix | `/simple <request>` | inspect → edit → focused verify |
-| Bug or failing behavior | `/debug <symptom>` | reproduce → root cause → regression test → fix → verify |
-| New behavior or refactor | `/task` → `/brainstorm` → `/spec` when needed → `/plan` | approval → implement → test → `/review` |
+| One obvious local fix | `/prompts:simple <request>` in Codex | inspect → edit → focused verify |
+| Bug or failing behavior | `/prompts:debug <symptom>` in Codex | reproduce → root cause → regression test → fix → verify |
+| New behavior or refactor | `/prompts:task` → `/brainstorm` → `/prompts:spec` when needed → `/plan` | approval → implement → test → `/review` |
 | Pre-merge review | `/review` | five-axis review; resolve blocking findings |
 | npm version/tag/publish | `/release` | release verification; never fast path |
 | Several specialist domains | `/orchestrate` | plan → approval → parallel work → integration verify |
 
 ### Standard Feature Flow
 
-`/task` → `/brainstorm` when needed → `/spec` for ambiguous or multi-file scope → `/plan` → explicit user approval → implementation → `/test` → `/review` → final verification → commit/push.
+`/prompts:task` → `/brainstorm` when needed → `/prompts:spec` for ambiguous or multi-file scope → `/plan` → explicit user approval → implementation → `/test` → `/review` → final verification → commit/push.
 
 Workflow files define process and gates. Skills define methods/checklists. Agents provide specialist ownership. Members should invoke the command, not only describe the work in chat.
 
 ### Bug Fix Flow
 
-Use `/debug` for regressions, failing tests, exceptions, incorrect output, or any symptom with an unknown root cause. Load `$systematic-debugging`, the `debugger` agent, and `testing-patterns`; reproduce the issue, inspect the code path, test hypotheses, add regression protection, make the smallest root-cause fix, and verify. Use `/review` when the change is cross-file or affects a shared contract.
+Use `/prompts:debug` in Codex for regressions, failing tests, exceptions, incorrect output, or any symptom with an unknown root cause. Load `$systematic-debugging`, the `debugger` agent, and `testing-patterns`; reproduce the issue, inspect the code path, test hypotheses, add regression protection, make the smallest root-cause fix, and verify. Use `/review` when the change is cross-file or affects a shared contract.
 
 ### Simple Fast Path
 
-Use `/simple` only for one obvious file, an unambiguous result, and no behavior, API, schema, security, CI, dependency, workflow, or release contract change. Before editing, state:
+Use `/prompts:simple` in Codex only for one obvious file, an unambiguous result, and no behavior, API, schema, security, CI, dependency, workflow, or release contract change. Before editing, state:
 
 ```text
 FAST_PATH: simple-fix
@@ -98,7 +109,7 @@ REASON: [why Spec/Plan/Review are not needed]
 SCOPE: [file or narrow area]
 ```
 
-This bypasses only Spec, Plan, and the feature/refactor Review gate. It never bypasses inspection or verification. If the scope expands, stop and run `/task` again.
+This bypasses only Spec, Plan, and the feature/refactor Review gate. It never bypasses inspection or verification. If the scope expands, stop and run `/prompts:task` again.
 
 Claude Code has a Stop hook that checks the standard feature/refactor gate. Codex, Antigravity, and Cursor use the same written routing rules through `AGENTS.md`, `.cursorrules`, and `.agent/rules/GEMINI.md`.
 

package/bin/cli.js

@@ -145,33 +145,33 @@ ${pc.bold('What gets generated:')}
   .claude/skills/   Selected Claude Code project skills copied from .agent/skills
 
 ${pc.bold('Workflow guide:')}
-  Every task               /task        Classify the request and select the workflow, skill, and agent
-  Small obvious fix        /simple      Fast path; skips spec/plan/review but still verifies
+  Every task               /prompts:task   Classify request and select workflow, skill, and agent
+  Small obvious fix        /prompts:simple Fast path; skips spec/plan/review but still verifies
   Idea is fuzzy            /brainstorm  Explore options, tradeoffs, and recommended direction
-  Scope needs a contract    /spec        Define requirements and acceptance criteria; no code yet
+  Scope needs a contract    /prompts:spec  Define requirements and acceptance criteria; no code yet
   New app from scratch     /create      Turn an app idea into plan + implementation flow
   Feature is clear         /plan        Create docs/PLAN-*.md first, no code yet
   Existing app update      /enhance     Add or change a feature in an existing codebase
-  Bug or failing behavior  /debug       Investigate symptoms, hypotheses, root cause, fix
+  Bug or failing behavior  /prompts:debug Investigate symptoms, root cause, fix
   UI / UX work             ui-ux-pro-max, frontend-specialist, $frontend-design, $webapp-testing
   Run or add tests         /test        Generate tests, run tests, check coverage
   Preview locally          /preview     Start, stop, restart, or health-check dev server
   Deploy / infra           /deploy      Release, hosting, Docker, cloud, environment setup
   Pre-merge review         /review      Run the five-axis review before calling work complete
-  Npm package release      /release     Verify, version, tag, publish, and verify the package
+  Npm package release      /prompts:release Verify, version, tag, publish, and verify the package
   Project state            /status      Summarize stack, progress, preview, pending work
   Multi-domain work        /orchestrate Coordinate frontend, backend, data, security, QA
 
 ${pc.bold('Common explicit skill prompts:')}
-  Use /task to route this request before editing.
-  Use /simple for a one-file fix with no behavior or contract change.
+  In Codex, use /prompts:task to route this request before editing.
+  In Codex, use /prompts:simple for a one-file fix with no behavior or contract change.
   Use /brainstorm for this feature idea before planning.
-  Use /spec when requirements or scope need an explicit contract.
+  In Codex, use /prompts:spec when requirements or scope need an explicit contract.
   Use /plan for this feature; do not write code yet.
   Use /enhance to implement this planned feature.
-  Use /debug for this failing behavior and find the root cause before editing.
+  In Codex, use /prompts:debug for this failing behavior and find the root cause before editing.
   Use /review before claiming this feature/refactor complete.
-  Use /release for npm versioning and publishing.
+  In Codex, use /prompts:release for npm versioning and publishing.
   Use $clean-code before editing this module.
   Use $systematic-debugging to investigate this bug.
   Use $webapp-testing to verify the UI with Playwright.
@@ -919,18 +919,18 @@ If any \`.agent/docs/*.md\` file still contains \`TODO: refine\`, update the doc
 
 ## Task Flow
 
-Route every task before editing. Use \`/task <request>\` when the correct path is not obvious.
+Route every task before editing. In Codex, use \`/prompts:task <request>\`; other clients can read the matching file under \`.agent/workflows/\`.
 
 - Questions and analysis: answer directly, cite relevant files when useful, and do not edit code.
-- Simple fix: use \`/simple <request>\` only for one-file, unambiguous changes with no behavior or contract change.
-- Bug or failing behavior: use \`/debug <symptom>\` and follow the evidence-first root-cause flow.
-- Feature or refactor: use \`/brainstorm\` for discovery, \`/spec\` for ambiguous or multi-file scope, then \`/plan\`, wait for approval, implement, test, and \`/review\`.
+- Simple fix: use Codex \`/prompts:simple <request>\` only for one-file, unambiguous changes with no behavior or contract change.
+- Bug or failing behavior: use Codex \`/prompts:debug <symptom>\` and follow the evidence-first root-cause flow.
+- Feature or refactor: use \`/brainstorm\` for discovery, Codex \`/prompts:spec\` for ambiguous or multi-file scope, then \`/plan\`, wait for approval, implement, test, and \`/review\`.
 - Pre-merge review: use \`/review\` even when the implementation itself was done by another client or member.
-- Release or npm publish: use \`/release\`; release work never uses the simple fast path.
+- Release or npm publish: use Codex \`/prompts:release\`; release work never uses the simple fast path.
 - Multi-domain work: use \`.agent/workflows/orchestrate.md\` and route to the relevant specialist docs.
 - UI work: read \`.agent/agents/frontend-specialist.md\` and applicable design skills before editing.
 
-### Fast Path (\`/simple\`)
+### Fast Path (Codex \`/prompts:simple\`)
 
 The fast path intentionally bypasses only Spec, Plan, and the feature/refactor Review gate for a trivial change. It never bypasses inspection, focused verification, or reporting evidence. The agent must state this protocol before editing:
 
@@ -940,7 +940,7 @@ REASON: [why the change is one-file and unambiguous]
 SCOPE: [file or narrow area]
 \`\`\`
 
-If the scope expands, stop and re-route with \`/task\`. Do not silently skip gates for work that changes behavior, APIs, schemas, security, CI, dependencies, workflows, or release state.
+If the scope expands, stop and re-route with Codex \`/prompts:task\`. Do not silently skip gates for work that changes behavior, APIs, schemas, security, CI, dependencies, workflows, or release state.
 
 ### Gated Flow (feature or refactor)
 
@@ -949,7 +949,7 @@ If the scope expands, stop and re-route with \`/task\`. Do not silently skip gat
 3. **Implement** — smallest coherent change per the approved plan, with focused tests for changed behavior.
 4. **Review** — run \`.agent/workflows/review.md\` (five-axis review) before the change is considered done. All 🔴 BLOCKING items must be resolved or explicitly accepted with rationale.
 
-A feature/refactor task is not "done" until step 4's exit criteria are met — passing tests alone does not satisfy the gate. Simple fixes use the explicit \`/simple\` fast path above. See \`.agent/docs/getting-started.md\` for the complete route guide.
+A feature/refactor task is not "done" until step 4's exit criteria are met — passing tests alone does not satisfy the gate. Simple fixes use the explicit Codex \`/prompts:simple\` fast path above. See \`.agent/docs/getting-started.md\` for the complete route guide.
 
 ## Skill Loading
 
@@ -1185,7 +1185,7 @@ function generateWorkflowDoc() {
 
 1. Read AGENTS.md.
 2. Read .agent/docs/project.md.
-3. Route the request with \`/task <request>\` when the path is not obvious.
+3. Route the request with Codex \`/prompts:task <request>\` when the path is not obvious; otherwise read \`.agent/workflows/task.md\` directly.
 4. Read only the relevant docs under .agent/agents, .agent/skills, .claude/skills, and .agent/workflows.
 5. Check if MCP servers (like \`codegraph\`) are active/available and prioritize using them as the primary entry point to search and locate files, symbols, and code blocks.
 
@@ -1194,11 +1194,11 @@ function generateWorkflowDoc() {
 | Situation | Command | Workflow / gate |
 |---|---|---|
 | Question or analysis only | direct answer | no edits |
-| One obvious local fix | \`/simple\` | \`.agent/workflows/simple.md\`, fast-path |
-| Bug, regression, failing test, or unknown error | \`/debug\` | \`.agent/workflows/debug.md\`, evidence-first |
-| New behavior, multi-file change, or unclear scope | \`/brainstorm\` -> \`/spec\` when needed -> \`/plan\` | spec/plan approval -> implement -> review |
+| One obvious local fix | Codex \`/prompts:simple\` | \`.agent/workflows/simple.md\`, fast-path |
+| Bug, regression, failing test, or unknown error | Codex \`/prompts:debug\` | \`.agent/workflows/debug.md\`, evidence-first |
+| New behavior, multi-file change, or unclear scope | \`/brainstorm\` -> Codex \`/prompts:spec\` when needed -> \`/plan\` | spec/plan approval -> implement -> review |
 | Pre-merge review | \`/review\` | \`.agent/workflows/review.md\`, five-axis |
-| npm version, tag, publish, or deployment | \`/release\` | \`.agent/workflows/release.md\`, release gate |
+| npm version, tag, publish, or deployment | Codex \`/prompts:release\` | \`.agent/workflows/release.md\`, release gate |
 | Several specialist domains | \`/orchestrate\` | plan -> approval -> parallel work -> integration verify |
 
 If a task is not clearly simple, use the standard flow. Never use the fast path for behavior, API, schema, security, CI, dependency, workflow, or release changes.
@@ -1216,7 +1216,7 @@ If a task is not clearly simple, use the standard flow. Never use the fast path
 
 ## Implementation Flow
 
-For \`/simple\` fixes, state the fast-path decision before editing:
+For Codex \`/prompts:simple\` fixes, state the fast-path decision before editing:
 
 \`\`\`text
 FAST_PATH: simple-fix
@@ -1233,7 +1233,7 @@ Then:
 5. Run verification (prioritize using Playwright MCP for web/UI changes to automate verification and capture screenshots).
 6. Summarize changed files and verification evidence.
 
-For bugs, use \`/debug\` with \`$systematic-debugging\`, the \`debugger\` agent, and \`testing-patterns\`: reproduce, isolate the root cause, add regression protection, make the smallest fix, and verify.
+For bugs, use Codex \`/prompts:debug\` with \`$systematic-debugging\`, the \`debugger\` agent, and \`testing-patterns\`: reproduce, isolate the root cause, add regression protection, make the smallest fix, and verify.
 
 For features or refactors, this flow runs *inside* the gated flow defined in AGENTS.md (spec -> plan -> implement -> review) — steps 3-5 above are the "Implement" phase, and step 6 is not a substitute for the mandatory \`.agent/workflows/review.md\` gate.
 
@@ -1241,7 +1241,7 @@ For features or refactors, this flow runs *inside* the gated flow defined in AGE
 
 A feature/refactor task is only complete when all of the following hold — not when code compiles or tests pass:
 
-The Spec checkbox may be skipped only when the documented \`/simple\` fast-path protocol is stated and its criteria are met.
+The Spec checkbox may be skipped only when the documented Codex \`/prompts:simple\` fast-path protocol is stated and its criteria are met.
 
 - [ ] \`.agent/workflows/spec.md\` exit criteria met (or explicitly skipped as a trivial/self-contained change)
 - [ ] \`.agent/workflows/plan.md\` produced a plan file, approved by the user
@@ -1265,9 +1265,20 @@ function generateGettingStartedDoc() {
 
 Read this after \`thachvd-kit init\`. The kit gives every member one entry point, then selects only the process and expertise the task needs.
 
-## Start Every Task With /task
+## Client Command Map
 
-Use \`/task <request>\` before editing whenever the route is not already obvious. It must produce:
+| Client | Task router | Simple fix | Bug fix | Feature spec | Release |
+|---|---|---|---|---|---|
+| Codex | \`/prompts:task\` | \`/prompts:simple\` | \`/prompts:debug\` | \`/prompts:spec\` | \`/prompts:release\` |
+| Antigravity | \`/task\` | \`/simple\` | \`/debug\` | \`/spec\` | \`/release\` |
+| Claude Code | \`/task\` | \`/simple\` | \`/debug\` | \`/spec\` | \`/release\` |
+| Cursor | \`/task\` | \`/simple\` | \`/debug\` | \`/spec\` | \`/release\` |
+
+Codex reads custom prompts from \`~/.codex/prompts\`. Antigravity reads workspace workflows from \`.agent/workflows\`. Claude Code reads project skills from \`.claude/skills/<name>/SKILL.md\`. Cursor reads commands from \`.cursor/commands\`.
+
+## Start Every Task With The Router
+
+In Codex, use \`/prompts:task <request>\` before editing whenever the route is not already obvious. Other clients can read \`.agent/workflows/task.md\` directly. It must produce:
 
 \`\`\`text
 ROUTE: question | simple | feature | bug | review | release | multi-domain
@@ -1285,22 +1296,22 @@ A workflow is the process and its gates. A skill is the method or checklist. An
 | Situation | Command | Gate | Required next step |
 |---|---|---|---|
 | Explain, inspect, or brainstorm only | direct answer or \`/brainstorm\` | none | no code until the request becomes actionable |
-| One obvious local fix | \`/simple <request>\` | fast-path | inspect -> edit -> focused verify |
-| New behavior, multi-file change, unclear scope, or >~30 min | \`/task\` -> \`/brainstorm\` -> \`/spec\` when needed -> \`/plan\` | standard | wait for approval before implementation |
-| Bug, regression, failing test, or unknown error | \`/debug <symptom>\` | bug | reproduce -> isolate -> regression test -> fix -> verify |
+| One obvious local fix | \`/prompts:simple <request>\` in Codex | fast-path | inspect -> edit -> focused verify |
+| New behavior, multi-file change, unclear scope, or >~30 min | \`/prompts:task\` -> \`/brainstorm\` -> \`/prompts:spec\` when needed -> \`/plan\` | standard | wait for approval before implementation |
+| Bug, regression, failing test, or unknown error | \`/prompts:debug <symptom>\` in Codex | bug | reproduce -> isolate -> regression test -> fix -> verify |
 | Pre-merge or independent review | \`/review\` | review | five-axis review; resolve blocking findings |
-| Version, tag, npm publish, or deployment | \`/release\` | release | release checklist; never fast-path |
+| Version, tag, npm publish, or deployment | \`/prompts:release\` in Codex | release | release checklist; never fast-path |
 | Frontend + backend + data/security together | \`/orchestrate\` | standard | plan -> approval -> specialist work -> integration verify |
 
 ## Standard Feature Flow
 
-The gated sequence is Spec -> Plan -> Implement -> Review: \`/task\` -> \`/brainstorm\` -> \`/spec\` when scope is ambiguous or multi-file -> \`/plan\` -> user approves the plan -> implementation -> \`/test\` -> \`/review\` -> final verification -> commit/push.
+The gated sequence is Spec -> Plan -> Implement -> Review: \`/prompts:task\` -> \`/brainstorm\` -> \`/prompts:spec\` when scope is ambiguous or multi-file -> \`/plan\` -> user approves the plan -> implementation -> \`/test\` -> \`/review\` -> final verification -> commit/push.
 
 The plan is a gate, not a suggestion. Do not start product-code implementation before explicit approval. Load only the relevant specialist agent and skills, such as \`$frontend-design\`, \`$api-design\`, or \`$webapp-testing\`.
 
 ## Bug Fix Flow
 
-Use \`/debug <symptom>\`, not the feature flow, when something is failing or the root cause is unknown:
+Use Codex \`/prompts:debug <symptom>\`, not the feature flow, when something is failing or the root cause is unknown:
 
 1. Capture the exact symptom, environment, reproduction, and expected result.
 2. Inspect the relevant code path with MCP/codegraph when available.
@@ -1314,7 +1325,7 @@ Load \`$systematic-debugging\`, the \`debugger\` agent, and \`testing-patterns\`
 
 ## Simple Fast Path
 
-Use \`/simple <request>\` only when the change is one obvious file, the result is unambiguous, and it changes no behavior, API, schema, security, CI, dependency, workflow, or release contract. Before editing, state:
+Use Codex \`/prompts:simple <request>\` only when the change is one obvious file, the result is unambiguous, and it changes no behavior, API, schema, security, CI, dependency, workflow, or release contract. Before editing, state:
 
 \`\`\`text
 FAST_PATH: simple-fix
@@ -1322,18 +1333,18 @@ REASON: [why Spec/Plan/Review are not needed]
 SCOPE: [file or narrow area]
 \`\`\`
 
-This bypasses only Spec, Plan, and the feature/refactor Review gate. It never bypasses inspection, focused verification, or reporting evidence. If the scope expands, stop and re-route with \`/task\`.
+This bypasses only Spec, Plan, and the feature/refactor Review gate. It never bypasses inspection, focused verification, or reporting evidence. If the scope expands, stop and re-route with Codex \`/prompts:task\`.
 
 ## Command And Skill Map
 
 - \`/brainstorm\`: clarify intent and tradeoffs; no code.
-- \`/spec\`: define requirements and acceptance criteria; no code.
+- Codex \`/prompts:spec\`: define requirements and acceptance criteria; no code.
 - \`/plan\`: create an approved implementation plan; no code before approval.
 - \`/enhance\` or \`/create\`: implement an approved feature with the relevant specialist agent.
-- \`/debug\`: systematic root-cause investigation and regression protection.
+- Codex \`/prompts:debug\`: systematic root-cause investigation and regression protection.
 - \`/test\`: add or run tests and assess coverage.
 - \`/review\`: five-axis review before completion or merge.
-- \`/release\`: verify, version, tag, publish, and verify npm output.
+- Codex \`/prompts:release\`: verify, version, tag, publish, and verify npm output.
 - \`$clean-code\` and \`$verification-before-completion\`: default implementation hygiene.
 - \`$webapp-testing\`: browser/UI verification; use Playwright when available.
 
@@ -1536,7 +1547,7 @@ function copyAgentFolder() {
     return { copied, skipped: 0 };
 }
 
-function copySelectedSkillFolders(data, assumeYes) {
+function copySelectedSkillFolders(data, assumeYes) {
     const srcSkills = path.join(sourceDir, '.agent', 'skills');
     if (!fs.existsSync(srcSkills)) return { copied: 0, skipped: 0, missing: 0, skills: [] };
 
@@ -1579,8 +1590,55 @@ function copySelectedSkillFolders(data, assumeYes) {
         }
     }
 
-    return { copied, skipped: 0, missing, skills: selectedSkills };
-}
+    return { copied, skipped: 0, missing, skills: selectedSkills };
+}
+
+function copyCodexPrompts() {
+    const srcPrompts = path.join(sourceDir, 'prompts');
+    const codexPromptsDir = homePath('.codex', 'prompts');
+    if (!fs.existsSync(srcPrompts) || !codexPromptsDir) {
+        return { copied: 0, prompts: [] };
+    }
+
+    let copied = 0;
+    const prompts = [];
+    fs.mkdirSync(codexPromptsDir, { recursive: true });
+    for (const entry of fs.readdirSync(srcPrompts, { withFileTypes: true })) {
+        if (!entry.isFile() || !entry.name.endsWith('.md')) continue;
+        fs.copyFileSync(path.join(srcPrompts, entry.name), path.join(codexPromptsDir, entry.name));
+        copied++;
+        prompts.push(path.basename(entry.name, '.md'));
+    }
+    return { copied, prompts };
+}
+
+function copyClientWorkflowCommands() {
+    const srcPrompts = path.join(sourceDir, 'prompts');
+    const claudeSkillsDir = path.join(targetDir, '.claude', 'skills');
+    const cursorCommandsDir = path.join(targetDir, '.cursor', 'commands');
+    if (!fs.existsSync(srcPrompts)) {
+        return { claude: 0, cursor: 0, prompts: [] };
+    }
+
+    let claude = 0;
+    let cursor = 0;
+    const prompts = [];
+    for (const entry of fs.readdirSync(srcPrompts, { withFileTypes: true })) {
+        if (!entry.isFile() || !entry.name.endsWith('.md')) continue;
+        const name = path.basename(entry.name, '.md');
+        const sourcePath = path.join(srcPrompts, entry.name);
+        const sourceContent = fs.readFileSync(sourcePath, 'utf8');
+        const cursorContent = sourceContent.replace(/^---\r?\n[\s\S]*?\r?\n---\r?\n/, '');
+        fs.mkdirSync(path.join(claudeSkillsDir, name), { recursive: true });
+        fs.copyFileSync(sourcePath, path.join(claudeSkillsDir, name, 'SKILL.md'));
+        fs.mkdirSync(cursorCommandsDir, { recursive: true });
+        fs.writeFileSync(path.join(cursorCommandsDir, entry.name), cursorContent, 'utf8');
+        claude++;
+        cursor++;
+        prompts.push(name);
+    }
+    return { claude, cursor, prompts };
+}
 
 async function writeGeneratedFile(relativePath, content, assumeYes) {
     const outputPath = path.join(targetDir, relativePath);
@@ -1913,12 +1971,22 @@ async function main() {
         console.log(`  ${pc.yellow('~')} ${pc.bold('.agent/')} already exists - ${skipped} file${skipped !== 1 ? 's' : ''} skipped (no overwrite)`);
     }
 
-    const nativeSkills = copySelectedSkillFolders(data, assumeYes);
+    const nativeSkills = copySelectedSkillFolders(data, assumeYes);
     if (nativeSkills.copied > 0) {
         console.log(`  ${pc.green('OK')} Copied native skills to ${pc.bold('~/.codex/skills/')} and ${pc.bold('.claude/skills/')} (${nativeSkills.skills.join(', ')})`);
     } else if (nativeSkills.skipped > 0) {
         console.log(`  ${pc.yellow('~')} Native skills already exist - ${nativeSkills.skipped} file${nativeSkills.skipped !== 1 ? 's' : ''} skipped`);
-    }
+    }
+
+    const codexPrompts = copyCodexPrompts();
+    if (codexPrompts.copied > 0) {
+        console.log(`  ${pc.green('OK')} Installed Codex custom prompts in ${pc.bold('~/.codex/prompts/')} (${codexPrompts.prompts.map(name => `/prompts:${name}`).join(', ')})`);
+    }
+
+    const clientCommands = copyClientWorkflowCommands();
+    if (clientCommands.claude > 0 || clientCommands.cursor > 0) {
+        console.log(`  ${pc.green('OK')} Installed workflow commands for Claude Code (${clientCommands.claude}) and Cursor (${clientCommands.cursor})`);
+    }
 
 
     const generatedFiles = [
@@ -1964,8 +2032,11 @@ async function main() {
     - ${pc.bold('.cursorrules')} Cursor entry
     - ${pc.bold('.agent/docs/')} scan-based project rules, including ${pc.bold('getting-started.md')} (standard flow vs fast path)
     - ${pc.bold('.agent/')} skills, workflows, agents, and rules
-    - ${pc.bold('~/.codex/skills/')} selected Codex skills installed globally (visible in $ menu)
-    - ${pc.bold('.claude/skills/')} selected Claude Code native skills
+    - ${pc.bold('~/.codex/skills/')} selected Codex skills installed globally (visible in $ menu)
+    - ${pc.bold('~/.codex/prompts/')} Codex custom prompts (visible as /prompts:<name> after restart)
+    - ${pc.bold('.claude/skills/')} selected Claude Code native skills
+    - ${pc.bold('.claude/skills/{task,simple,debug,spec,release}/')} workflow skills (visible as /task, /simple, /debug, /spec, /release)
+    - ${pc.bold('.cursor/commands/')} Cursor workflow commands (visible as /task, /simple, /debug, /spec, /release)
     - ${pc.bold('.claude/settings.json')} Definition-of-Done Stop hook (Claude Code only — blocks reporting a feature/refactor "done" without a plan + review pass)
 
   ${pc.bold('MCP/tooling setup:')}

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "thachvd-kit",
-    "version": "1.0.27",
+    "version": "1.0.28",
     "description": "Cross-agent project rules bootstrap kit for Codex, Antigravity, and Claude Code",
     "bin": {
         "thachvd-kit": "./bin/cli.js"
@@ -13,6 +13,7 @@
         "rules",
         "scripts",
         "skills",
+        "prompts",
         "workflows",
         "README.md",
         "LICENSE"

package/prompts/debug.md

@@ -0,0 +1,11 @@
+---
+description: Investigate a bug with evidence, root-cause analysis, regression protection, and verification.
+argument-hint: [SYMPTOM]
+---
+
+Read and follow `.agent/workflows/debug.md` in the current repository.
+
+Bug or symptom:
+$ARGUMENTS
+
+Use `$systematic-debugging`, the `debugger` agent, and `testing-patterns` when available. Reproduce and isolate the root cause before editing.

package/prompts/release.md

@@ -0,0 +1,11 @@
+---
+description: Run the npm release workflow with verification, versioning, tagging, publishing, and registry checks.
+argument-hint: [RELEASE_REQUEST]
+---
+
+Read and follow `.agent/workflows/release.md` in the current repository.
+
+Release request:
+$ARGUMENTS
+
+Do not publish until the release gate and `npm run release:verify` pass.

package/prompts/simple.md

@@ -0,0 +1,11 @@
+---
+description: Run the fast path for one-file, unambiguous fixes with verification.
+argument-hint: [TASK]
+---
+
+Read and follow `.agent/workflows/simple.md` in the current repository.
+
+Request:
+$ARGUMENTS
+
+Use the fast path only when its criteria are met. State `FAST_PATH: simple-fix`, `REASON`, and `SCOPE` before editing. Never skip verification.

package/prompts/spec.md

@@ -0,0 +1,11 @@
+---
+description: Define requirements and acceptance criteria before planning or implementation.
+argument-hint: [REQUEST]
+---
+
+Read and follow `.agent/workflows/spec.md` in the current repository.
+
+Request:
+$ARGUMENTS
+
+Do not write product code. Stop at the spec gate and wait for human confirmation.

package/prompts/task.md

@@ -0,0 +1,12 @@
+---
+description: Route the current request to the smallest safe workflow before editing.
+argument-hint: [TASK]
+---
+
+Read and follow `.agent/workflows/task.md` in the current repository.
+
+Route this request before editing:
+
+$ARGUMENTS
+
+Return the required ROUTE, WORKFLOW, SKILLS, AGENTS, GATE, and NEXT fields. Do not edit code while routing.

package/workflows/simple.md

@@ -6,6 +6,8 @@ description: Fast path for one-file, unambiguous fixes with no behavior or share
 
 $ARGUMENTS
 
+Codex UI command: `/prompts:simple`. The `/simple` name below describes the workflow; it is not a built-in Codex slash command.
+
 ## Use Only When
 
 - The change is limited to one obvious file or one tiny local edit.

package/workflows/task.md

@@ -6,6 +6,8 @@ description: Route every task to the smallest safe workflow, fast path, bug flow
 
 $ARGUMENTS
 
+Codex UI command: `/prompts:task`. The `/task` name below describes the workflow; it is not a built-in Codex slash command.
+
 ## Purpose
 
 Use `/task` at the start of a task when you are unsure which workflow, skill, or specialist agent applies. This command routes the request before implementation.