Codex technical-plan-guard for Feature Implementation Plans
Create a per-change plan for a feature, refactor, or repository rule change. The plan records scope, affected modules, risks, and validation before implementation starts.
中文Install in Codex
Codex with a writable skill-doctor checkout and access to the repository's documentation directory.
- Copy the entire pinned `.codex/skills/technical-plan-guard/` directory to `.agents/skills/technical-plan-guard/` in the target checkout.
- Open Codex in that checkout and invoke `$technical-plan-guard` with the example task and desired output.
Example task
In a sandbox checkout, invoke `$technical-plan-guard` to plan a two-field CSV export for comparison reports. Ask for a plan and one acceptance case before any implementation.What to check
A separate Markdown plan records field scope, affected code, and a concrete acceptance check for review.
Original SKILL.md on GitHub · Updated
Frequently asked question
Does a spelling fix need its own plan?
The upstream workflow exempts wording fixes, trivial one-line bug fixes, and exploratory requests without edits.