菜单
Guide Test-Driven Development cycle adapted for AI agents with a pragmatic approach
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
One-command project setup for OpenUP - interactive initialization wizard
Mark a task as complete, update roadmap, commit changes, and prepare traceability logs
Execute an already-claimed lane's Operations boxes with script/judgment classification — script steps run directly with zero self-brief, judgment steps self-brief and execute. Handles only pick/resume; every other resolve path routes to /openup-next.
Run OpenUP Assess Results at iteration end — check evaluation criteria, demo only completed acceptance-tested work, feed discovered work back, and trigger the milestone review at a phase boundary
Run the phase milestone go/no-go — prepare derived evidence, pause for the human decision via an input-request, and record the milestone (never advance the phase itself)
Begin a new OpenUP iteration with proper phase context and task selection
| name | openup-tdd-workflow |
| description | Guide Test-Driven Development cycle adapted for AI agents with a pragmatic approach |
| model | inherit |
| fit | {"great":["well-specified features with a clear test surface","regression bug fixes (start with failing repro)"],"ok":["refactors with strong existing test coverage"],"poor":["exploratory spikes","prototyping","UI-only tweaks","throwaway scripts"]} |
| arguments | [{"name":"phase","description":"TDD phase (red, green, refactor, full)","required":false},{"name":"feature","description":"Feature or component to implement","required":true}] |
Guide the red-green-refactor cycle with a pragmatic approach. TDD is a tool, not a mandate -- use it when it helps.
Based on $ARGUMENTS[phase]:
| Phase | Description |
|---|---|
| red | Write test first (preferably before implementation) |
| green | Implement to make test pass (commit point) |
| refactor | Clean up code while tests pass (optional for small changes) |
| full | Run complete red-green-refactor cycle |
See phase-specific documentation:
After each phase:
Document the TDD cycle in docs/tdd-logs/<feature>-tdd.md:
Returns a summary of:
