$npx -y skills add pavel-molyanov/molyanov-ai-dev --skill source-command-new-tech-specConverted Codex workflow from Claude slash command new-tech-spec. Use when the user asks to run the equivalent command or describes this workflow.
| 1 | <!-- Generated by sync-to-codex v1. Do not edit directly. --> |
| 2 | |
| 3 | # Command Workflow: new-tech-spec |
| 4 | |
| 5 | Treat Claude-only tool names as conceptual workflow steps and use available Codex tools/policies. |
| 6 | |
| 7 | ## Codex Policy Gates |
| 8 | |
| 9 | - Ask before external actions such as GitHub repository creation, `git push`, deploys, or sending messages unless the user explicitly requested that exact action. |
| 10 | - Deployments must go through GitHub CI/CD; direct server access is only for emergency debugging of broken production. |
| 11 | - Never ask the user to paste secrets in chat. Direct them to `.env` files or GitHub Actions secrets. |
| 12 | |
| 13 | # Instructions |
| 14 | |
| 15 | ## Project Documentation Autosync |
| 16 | |
| 17 | If this command changes any project-local `.claude/**` file, immediately run: |
| 18 | |
| 19 | ```bash |
| 20 | ~/.claude/scripts/sync-to-codex.sh --project "$PWD" --apply |
| 21 | ``` |
| 22 | |
| 23 | If sync reports a conflict, stop and report it. Include generated `.codex/**` changes in the same commit as the `.claude/**` source change. |
| 24 | |
| 25 | Use the `tech-spec-planning` skill. |