Name: planning-workflow
Author: lucasvu1302

Prompt file imported from lucasvu1302/codex-usage (.github/prompts/planning-workflow.prompt.md). Copyright stays with the author.

Choose the lightest useful mode: brainstorm, option comparison, implementation plan, plan review, or execution.

Anchor the work to files, symbols, Hono routes, shared contracts, schema fields, errors, or user flows.
Separate verified facts from assumptions and ask only blocking questions.
For alternatives, compare two or three options by local fit, effort, compatibility, migration risk, and verification cost.
For a plan, include goal, scope/non-goals, affected paths, ordered steps with acceptance checks, Vitest/Playwright impact, verification, rollback, and open questions.
For plan review or execution, check stale paths, missing coverage, unsafe commands, contract drift, migration/backfill gaps, and skipped verification.
Always preserve immutable session JSONL, an external runtime database default, 127.0.0.1 binding, and the ban on reading or writing real .env files.

Do not create a planning document, require approval for a trivial edit, or mutate Git/PM2/persistent data unless explicitly requested.

Choose the lightest useful mode: brainstorm, option comparison, implementation plan, plan review, or execution. 1. Anchor the work to files, symbols, Hono routes, shared contracts, schema fields, errors, or user flows. 2. Separate verified facts from assumptions and ask only blocking questions. 3. For alternatives, compare two or three options by local fit, effort, compatibility, migration risk, and verification cost. 4. For a plan, include goal, scope/non-goals, affected paths, ordered steps with acceptance checks, Vitest/Playwright impact, verification, rollback, and open questions. 5. For plan review or execution, check stale paths, missing coverage, unsafe commands, contract drift, migration/backfill gaps, and skipped verification. 6. Always preserve immutable session JSONL, an external runtime database default, `127.0.0.1` binding, and the ban on reading or writing real `.env` files. Do not create a planning document, require approval for a trivial edit, or mutate Git/PM2/persistent data unless explicitly requested.

{ "prompt": "Choose the lightest useful mode: brainstorm, option comparison, implementation plan, plan review, or execution.\n\n1. Anchor the work to files, symbols, Hono routes, shared contracts, schema fields, errors, or user flows.\n2. Separate verified facts from assumptions and ask only blocking questions.\n3. For alternatives, compare two or three options by local fit, effort, compatibility, migration risk, and verification cost.\n4. For a plan, include goal, scope/non-goals, affected paths, ordered steps with acceptance checks, Vitest/Playwright impact, verification, rollback, and open questions.\n5. For plan review or execution, check stale paths, missing coverage, unsafe commands, contract drift, migration/backfill gaps, and skipped verification.\n6. Always preserve immutable session JSONL, an external runtime database default, `127.0.0.1` binding, and the ban on reading or writing real `.env` files.\n\nDo not create a planning document, require approval for a trivial edit, or mutate Git/PM2/persistent data unless explicitly requested.", "variables": [], "notes": "Brainstorm, compare, write, review, or execute a Codex Usage plan without imposing a heavy process on small tasks. Tools: search/codebase, search/usages, read_file, run_in_terminal. Arguments: [idea, requested behavior, plan, changed scope, or implementation request].", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/lucasvu1302/codex-usage", "path": ".github/prompts/planning-workflow.prompt.md", "ref": "768b4f59ac055d0a7a18fbf51a82fa9217b52707", "url": "https://github.com/lucasvu1302/codex-usage/blob/768b4f59ac055d0a7a18fbf51a82fa9217b52707/.github/prompts/planning-workflow.prompt.md", "key": "lucasvu1302/codex-usage/.github/prompts/planning-workflow.prompt.md" } } }

planning-workflow

About

Use it

Manifest

Reviews