协作头脑风暴
brainstorming
在实现前澄清需求、探索设计选择,并形成清晰的开发方向。
checkpoint【开发与工程】Imported from everything-codex command checkpoint
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
Codex supports native subagents. Delegate with spawn_agent, coordinate with send_input, collect via wait_agent, and clean up with close_agent.
Execution preference:
[ANALYST]/[ARCHITECT]/[EXECUTOR]/[REVIEWER] structure in a single response.Minimal orchestration pattern:
spawn_agent -> send_input (optional) -> wait_agent -> close_agent
Create or verify a checkpoint in your workflow.
$checkpoint [create|verify|list] [name]
When creating a checkpoint:
$verify (quick mode if supported) to ensure current state is clean.codex/checkpoints.log:echo "$(date +%Y-%m-%d-%H:%M) | $CHECKPOINT_NAME | $(git rev-parse --short HEAD)" >> .codex/checkpoints.log
When verifying against a checkpoint:
Read checkpoint from log
Compare current state to checkpoint:
Report:
CHECKPOINT COMPARISON: $NAME
============================
Files changed: X
Tests: +Y passed / -Z failed
Coverage: +X% / -Y%
Build: [PASS/FAIL]
Show all checkpoints with:
Typical checkpoint flow:
[Start] --> $checkpoint create "feature-start"
|
[Implement] --> $checkpoint create "core-done"
|
[Test] --> $checkpoint verify "core-done"
|
[Refactor] --> $checkpoint create "refactor-done"
|
[PR] --> $checkpoint verify "feature-start"
$ARGUMENTS:
create <name> - Create named checkpointverify <name> - Verify against named checkpointlist - Show all checkpointsclear - Remove old checkpoints (keeps last 5)