codex-sdd
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.
git clone --depth 1 https://github.com/tranhieutt/software_development_department /tmp/codex-sdd && cp -r /tmp/codex-sdd/.claude/skills/codex-sdd ~/.claude/skills/codex-sddSKILL.md
# Codex SDD `codex-sdd` is the Codex adapter for the Software Development Department. It does not replace Claude Code behavior. It helps Codex follow the existing SDD contract without changing the Claude-native runtime. ## Core Rule Treat these files as the SDD source of truth: 1. `CLAUDE.md` 2. `.claude/skills/using-sdd/SKILL.md` 3. `docs/technical/SDD_LIFECYCLE_MAP.md` 4. `.claude/settings.json` for Claude-only runtime behavior Use `using-sdd` for routing. Use this skill only for Codex-specific adaptation. ## Non-Impact Boundary Do not change these for Codex-only reasons: - `.claude/settings.json` - `.claude/hooks/` - existing skill names or directories - existing agent names or files - Claude workflow semantics for `/plan`, `/spec`, `/tdd`, `/context`, or other SDD commands Codex compatibility must be additive unless the user explicitly approves a broader Claude regression-tested change. ## Codex Session Start At the start of a Codex session in SDD: 1. Read `AGENTS.md`. 2. Read `.claude/skills/using-sdd/SKILL.md`. 3. Use `docs/technical/SDD_LIFECYCLE_MAP.md` for phase orientation. 4. Select the governing SDD skill for the user request. 5. Remember that Claude hooks do not auto-run in Codex. ## Tool Mapping | Claude-style tool | Codex equivalent | | --- | --- | | `Read` | shell read commands or direct file inspection | | `Glob` | `rg --files` or shell listing | | `Grep` | `rg` | | `Write` | `apply_patch` | | `Edit` | `apply_patch` | | `Bash` | `shell_command` | | `RunCommand` | `shell_command` | | `Task` | `spawn_agent` only when explicitly authorized | | `TodoWrite` | `update_plan` | | `AskUserQuestion` | concise direct user question | | `WebSearch` | web search only when required or explicitly requested | ## Manual Hook Equivalents Claude Code hooks in `.claude/settings.json` do not run automatically in Codex. Use manual equivalents: | Claude behavior | Codex behavior | | --- | --- | | Session bootstrap | Read `AGENTS.md`, `using-sdd`, lifecycle map, and relevant memory. | | Pre-code gate | State the SDD pre-code gate before edits. | | Bash safety | Follow Codex sandbox and escalation rules. | | File history | Use `git log -- <file>` when needed. | | Write logging | Use git diff/status and final changed-file summary. | | Circuit guard | Inspect `.claude/memory/circuit-state.json` before subagent workflows. | | Completion gate | Use `verification-before-completion` before success claims. | ## Pre-Code Gate Before implementation edits, state: ```text Pre-code gate: <Fast|Spec|Plan|Interview|Override> satisfied by <evidence>; next edit: <file>; verification: <command/check>. ``` If the gate is not satisfied, stop and ask for the missing approval or clarification. ## Verification For SDD repo changes, run: ```powershell powershell -ExecutionPolicy Bypass -File scripts\codex-preflight.ps1 ``` If verification cannot be run, say exactly what was skipped and why. For narrower checks, use: ```powershell powershell -ExecutionPolicy Bypass -File scripts\validate-skills.ps1 node scripts\harness-audit.js --compact ``` ## References - `AGENTS.md` - `.codex/INSTALL.md` - `docs/codex-compatibility.md` - `.claude/skills/using-sdd/SKILL.md` - `docs/technical/SDD_LIFECYCLE_MAP.md`
The Accessibility Specialist ensures the software is accessible to the widest possible audience. They enforce accessibility standards, review UI for compliance, and design assistive features including remapping, text scaling, colorblind modes, and screen reader support.
The AI Programmer implements intelligent system features: recommendation engines, classification pipelines, LLM integrations, decision logic, and autonomous agent behavior. Use this agent for AI/ML feature implementation, model integration, intelligent automation, or AI system debugging.
The Analytics Engineer designs telemetry systems, user behavior tracking, A/B test frameworks, and data analysis pipelines. Use this agent for event tracking design, dashboard specification, A/B test design, or user behavior analysis methodology.
The Backend Developer builds and maintains server-side logic, APIs, databases, authentication, and integrations. Use this agent for REST/GraphQL API implementation, database operations, authentication systems, background jobs, microservices, server performance, and backend testing. Works from API design contracts and PRDs.
The Community Manager handles user-facing communications, feedback synthesis, support escalation, and community engagement. Use this agent for drafting release announcements, synthesizing user feedback into actionable insights, writing support documentation, or coordinating community-facing communication around releases and incidents.
The CTO (Chief Technical Officer) owns the high-level technical vision, architecture decisions, technology choices, and technical strategy. Use this agent for architecture-level decisions, technology evaluations, cross-system conflicts, and when a technical choice will constrain or enable product possibilities. This is the highest technical authority in the department.
The Data Engineer designs database schemas, builds data pipelines, manages migrations, and owns the data infrastructure. Use this agent for schema design, complex migrations, data modeling, ETL/ELT pipelines, database performance optimization, analytics infrastructure, and data integrity strategies.
The DevOps Engineer maintains build pipelines, CI/CD configuration, version control workflow, and deployment infrastructure. Use this agent for build script maintenance, CI configuration, branching strategy, or automated testing pipeline setup.