Codex OpenSpec Propose for Design, Specs, and Implementation Tasks
Turn a defined change into OpenSpec artifacts. Use the CLI's project-specific paths and dependency order to prepare a proposal and task list.
中文Install in Codex
Codex with a doc-view or initialized OpenSpec checkout and the OpenSpec CLI.
- Copy the entire pinned `.codex/skills/openspec-propose/` directory to `.agents/skills/openspec-propose/` in the target checkout.
- Open Codex in that checkout and invoke `$openspec-propose` with the example task and desired output.
Example task
Invoke `$openspec-propose` for a practice bookmark export date column. Ask for a backward-compatibility scenario and a concrete acceptance test.What to check
The proposal, design, specifications, and tasks are present at the resolved paths and record export behavior and old-data compatibility.
Original SKILL.md on GitHub · Updated
Frequently asked question
Can I assume the artifact directory?
Use the planning home, change root, and artifact paths returned by OpenSpec for the current project.