Menu
Implement a planning document end-to-end — branch, code, tests, PR. Use when the user asks to implement a planning-xxx.md file.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | task-dev |
| description | Implement a planning document end-to-end — branch, code, tests, PR. Use when the user asks to implement a planning-xxx.md file. |
| user-invocable | true |
Reference: planning-xxx-xxx.md as specified by the user.
Follow these steps in order. Report progress at each step before continuing.
main:git checkout main
git pull origin main
git checkout -b <branch-name> # e.g. feat/xxx, fix/xxx
Work through the planning doc in order. Spawn sub-agents for independent tasks when helpful. Report when each step completes before moving on.
tests/unit/ covering every test case in the planning doc.npm test — all suites must pass, zero failures.Pause and ask the user to confirm before opening a PR.
If the task involves UI changes, spin up a preview so the user can verify visually:
# Terminal 1 — dev server (kill any existing dev server first to reuse the same port)
npm run dev
# Terminal 2 — public tunnel
cloudflared tunnel --url http://localhost:<port>
Verify the tunnel is working by curling the public URL — confirm you get actual HTML from the app, not a Cloudflare error page. Only then report the URL to the user and wait for their go-ahead.
git add <files>
git commit -m "<english commit message>"
git push -u origin <branch-name>
gh pr create --title "..." --body "..."