codex-sdd

Name: codex-sdd
Author: tranhieutt

69stars41forks

How to install codex-sdd?

tranhieutt/software_development_department/codex-sdd

$npx -y skills add tranhieutt/software_development_department --skill codex-sdd

Installs into the current project.

Summary

Adapts SDD for Codex while preserving Claude Code behavior. Use when working in Codex, setting up Codex compatibility, mapping Claude tools to Codex tools, or explaining how SDD should run outside Claude Code.

Files · 1

View on GitHub

SKILL.md

1	# Codex SDD
2
3	`codex-sdd` is the Codex adapter for the Software Development Department.
4
5	It does not replace Claude Code behavior. It helps Codex follow the existing
6	SDD contract without changing the Claude-native runtime.
7
8	## Core Rule
9
10	Treat these files as the SDD source of truth:
11
12	1. `CLAUDE.md`
13	2. `.claude/skills/using-sdd/SKILL.md`
14	3. `docs/technical/SDD_LIFECYCLE_MAP.md`
15	4. `.claude/settings.json` for Claude-only runtime behavior
16
17	Use `using-sdd` for routing. Use this skill only for Codex-specific adaptation.
18
19	## Non-Impact Boundary
20
21	Do not change these for Codex-only reasons:
22
23	- `.claude/settings.json`
24	- `.claude/hooks/`
25	- existing skill names or directories
26	- existing agent names or files
27	- Claude workflow semantics for `/plan`, `/spec`, `/tdd`, `/context`, or other
28	SDD commands
29
30	Codex compatibility must be additive unless the user explicitly approves a
31	broader Claude regression-tested change.
32
33	## Codex Session Start
34
35	At the start of a Codex session in SDD:
36
37	1. Read `AGENTS.md`.
38	2. Read `.claude/skills/using-sdd/SKILL.md`.
39	3. Use `docs/technical/SDD_LIFECYCLE_MAP.md` for phase orientation.
40	4. Select the governing SDD skill for the user request.
41	5. Remember that Claude hooks do not auto-run in Codex.
42
43	## Tool Mapping
44
45	\| Claude-style tool \| Codex equivalent \|
46	\| --- \| --- \|
47	\| `Read` \| shell read commands or direct file inspection \|
48	\| `Glob` \| `rg --files` or shell listing \|
49	\| `Grep` \| `rg` \|
50	\| `Write` \| `apply_patch` \|
51	\| `Edit` \| `apply_patch` \|
52	\| `Bash` \| `shell_command` \|
53	\| `RunCommand` \| `shell_command` \|
54	\| `Task` \| `spawn_agent` only when explicitly authorized \|
55	\| `TodoWrite` \| `update_plan` \|
56	\| `AskUserQuestion` \| concise direct user question \|
57	\| `WebSearch` \| web search only when required or explicitly requested \|
58
59	## Manual Hook Equivalents
60
61	Claude Code hooks in `.claude/settings.json` do not run automatically in Codex.
62	Use manual equivalents:
63
64	\| Claude behavior \| Codex behavior \|
65	\| --- \| --- \|
66	\| Session bootstrap \| Read `AGENTS.md`, `using-sdd`, lifecycle map, and relevant memory. \|
67	\| Pre-code gate \| State the SDD pre-code gate before edits. \|
68	\| Bash safety \| Follow Codex sandbox and escalation rules. \|
69	\| File history \| Use `git log -- <file>` when needed. \|
70	\| Write logging \| Use git diff/status and final changed-file summary. \|
71	\| Circuit guard \| Inspect `.claude/memory/circuit-state.json` before subagent workflows. \|
72	\| Completion gate \| Use `verification-before-completion` before success claims. \|
73
74	## Pre-Code Gate
75
76	Before implementation edits, state:
77
78	```text
79	Pre-code gate: <Fast\|Spec\|Plan\|Interview\|Override> satisfied by <evidence>; next edit: <file>; verification: <command/check>.
80	```
81
82	If the gate is not satisfied, stop and ask for the missing approval or
83	clarification.
84
85	## Verification
86
87	For SDD repo changes, run:
88
89	```powershell
90	powershell -ExecutionPolicy Bypass -File scripts\codex-preflight.ps1
91	```
92
93	If verification cannot be run, say exactly what was skipped and why.
94
95	For narrower checks, use:
96
97	```powershell
98	powershell -ExecutionPolicy Bypass -File scripts\validate-skills.ps1
99	node scripts\harness-audit.js --compact
100	```
101
102	## References
103
104	- `AGENTS.md`
105	- `.codex/INSTALL.md`
106	- `docs/codex-compatibility.md`
107	- `.claude/skills/using-sdd/SKILL.md`
108	- `docs/technical/SDD_LIFECYCLE_MAP.md`

People who liked this also viewed

6 picks

Type

codex-sdd

69stars41forks

View on GitHub

How to install codex-sdd?

tranhieutt/software_development_department/codex-sdd

$npx -y skills add tranhieutt/software_development_department --skill codex-sdd

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Codex SDD
2
3	`codex-sdd` is the Codex adapter for the Software Development Department.
4
5	It does not replace Claude Code behavior. It helps Codex follow the existing
6	SDD contract without changing the Claude-native runtime.
7
8	## Core Rule
9
10	Treat these files as the SDD source of truth:
11
12	1. `CLAUDE.md`
13	2. `.claude/skills/using-sdd/SKILL.md`
14	3. `docs/technical/SDD_LIFECYCLE_MAP.md`
15	4. `.claude/settings.json` for Claude-only runtime behavior
16
17	Use `using-sdd` for routing. Use this skill only for Codex-specific adaptation.
18
19	## Non-Impact Boundary
20
21	Do not change these for Codex-only reasons:
22
23	- `.claude/settings.json`
24	- `.claude/hooks/`
25	- existing skill names or directories
26	- existing agent names or files
27	- Claude workflow semantics for `/plan`, `/spec`, `/tdd`, `/context`, or other
28	SDD commands
29
30	Codex compatibility must be additive unless the user explicitly approves a
31	broader Claude regression-tested change.
32
33	## Codex Session Start
34
35	At the start of a Codex session in SDD:
36
37	1. Read `AGENTS.md`.
38	2. Read `.claude/skills/using-sdd/SKILL.md`.
39	3. Use `docs/technical/SDD_LIFECYCLE_MAP.md` for phase orientation.
40	4. Select the governing SDD skill for the user request.
41	5. Remember that Claude hooks do not auto-run in Codex.
42
43	## Tool Mapping
44
45	\| Claude-style tool \| Codex equivalent \|
46	\| --- \| --- \|
47	\| `Read` \| shell read commands or direct file inspection \|
48	\| `Glob` \| `rg --files` or shell listing \|
49	\| `Grep` \| `rg` \|
50	\| `Write` \| `apply_patch` \|
51	\| `Edit` \| `apply_patch` \|
52	\| `Bash` \| `shell_command` \|
53	\| `RunCommand` \| `shell_command` \|
54	\| `Task` \| `spawn_agent` only when explicitly authorized \|
55	\| `TodoWrite` \| `update_plan` \|
56	\| `AskUserQuestion` \| concise direct user question \|
57	\| `WebSearch` \| web search only when required or explicitly requested \|
58
59	## Manual Hook Equivalents
60
61	Claude Code hooks in `.claude/settings.json` do not run automatically in Codex.
62	Use manual equivalents:
63
64	\| Claude behavior \| Codex behavior \|
65	\| --- \| --- \|
66	\| Session bootstrap \| Read `AGENTS.md`, `using-sdd`, lifecycle map, and relevant memory. \|
67	\| Pre-code gate \| State the SDD pre-code gate before edits. \|
68	\| Bash safety \| Follow Codex sandbox and escalation rules. \|
69	\| File history \| Use `git log -- <file>` when needed. \|
70	\| Write logging \| Use git diff/status and final changed-file summary. \|
71	\| Circuit guard \| Inspect `.claude/memory/circuit-state.json` before subagent workflows. \|
72	\| Completion gate \| Use `verification-before-completion` before success claims. \|
73
74	## Pre-Code Gate
75
76	Before implementation edits, state:
77
78	```text
79	Pre-code gate: <Fast\|Spec\|Plan\|Interview\|Override> satisfied by <evidence>; next edit: <file>; verification: <command/check>.
80	```
81
82	If the gate is not satisfied, stop and ask for the missing approval or
83	clarification.
84
85	## Verification
86
87	For SDD repo changes, run:
88
89	```powershell
90	powershell -ExecutionPolicy Bypass -File scripts\codex-preflight.ps1
91	```
92
93	If verification cannot be run, say exactly what was skipped and why.
94
95	For narrower checks, use:
96
97	```powershell
98	powershell -ExecutionPolicy Bypass -File scripts\validate-skills.ps1
99	node scripts\harness-audit.js --compact
100	```
101
102	## References
103
104	- `AGENTS.md`
105	- `.codex/INSTALL.md`
106	- `docs/codex-compatibility.md`
107	- `.claude/skills/using-sdd/SKILL.md`
108	- `docs/technical/SDD_LIFECYCLE_MAP.md`

People who liked this also viewed

6 picks

Type