Added 2 new commands that work well in Codex to replace /specify #473
+28
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I was digging into your Codex support this morning, and without the ability to use $ARGUMENTS when invoking a command in Codex, I create another 2-command step that works around that problem. I have tested this and it seems to work pretty well.
Steps:
/new
to clear the context/discuss
, Codex will ask a question like "Happy to help! To start, what’s the high-level goal for this new feature?" to which you can respond with a simple description. The agent will go back and forth with the user to clarify requirements one question at a time and then output a summary and prompt the user to continue with the next command/feature
which will take the above discussion and summary and execute the same process that/specify
would have done./plan
>/tasks
>/implement
as normalI have tested this by implementing 2 new features already this morning. Another added benefit that I can see is that maybe the discussion phase irons out a lot of the possible
NEEDS CLARIFICATION
segments during the planning phase.I added some description to the Codex-specific warning text when initializing the project. But maybe some up-for-discussion thoughts:
/specify-codex
and copy it into the project instead of the originalspecify
? Could be cleaner than this, but I thought to keep them separate for the time being, in case OpenAI decides to implement command arguments in the near future, this might all be moot.