name	source-command-new-user-spec
description	Converted Codex workflow from Claude slash command `new-user-spec`. Use when the user asks to run the equivalent command or describes this workflow.

Command Workflow: new-user-spec

Treat Claude-only tool names as conceptual workflow steps and use available Codex tools/policies.

Ask before external actions such as GitHub repository creation, git push, deploys, or sending messages unless the user explicitly requested that exact action.
Deployments must go through GitHub CI/CD; direct server access is only for emergency debugging of broken production.
Never ask the user to paste secrets in chat. Direct them to .env files or GitHub Actions secrets.

Instructions

If this command changes any project-local .claude/** file, immediately run:

~/.claude/scripts/sync-to-codex.sh --project "$PWD" --apply

If sync reports a conflict, stop and report it. Include generated .codex/** changes in the same commit as the .claude/** source change.

Use the user-spec-planning skill.

name	source-command-new-user-spec
description	Converted Codex workflow from Claude slash command `new-user-spec`. Use when the user asks to run the equivalent command or describes this workflow.

Treat Claude-only tool names as conceptual workflow steps and use available Codex tools/policies.

Ask before external actions such as GitHub repository creation, git push, deploys, or sending messages unless the user explicitly requested that exact action.
Deployments must go through GitHub CI/CD; direct server access is only for emergency debugging of broken production.
Never ask the user to paste secrets in chat. Direct them to .env files or GitHub Actions secrets.

If this command changes any project-local .claude/** file, immediately run:

~/.claude/scripts/sync-to-codex.sh --project "$PWD" --apply

If sync reports a conflict, stop and report it. Include generated .codex/** changes in the same commit as the .claude/** source change.

Use the user-spec-planning skill.