Menu
Start the next project iteration after the initial Sprint roadmap is complete.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Update durable context shards and run checkpoint validation when project rules, architecture, workflows, or long-running Orchestrator state changes.
Codex-compatible wrapper for the shared vibe-doctor context maintenance and Orchestrator checkpoint workflow.
Convert a fully settled design into repeated /goal + $vibe-iterate implementation cycles. Use when the user has finished a detailed design discussion, says there are no more open questions, and wants Codex to autonomously split the design into items, run mini planning/interview checkpoints only when needed, generate Planner/Sprint work, implement each item, verify it, persist handoffs/checkpoints, and continue non-stop until every item is complete or a real blocker is found.
Codex-compatible wrapper for the shared vibe-doctor goal-iteration workflow. Use when a settled design needs autonomous itemized /goal plus $vibe-iterate implementation cycles until every item is completed, blocked, or deferred with durable handoffs.
프로젝트 초기 세팅을 대화형으로 진행합니다. 환경 점검, provider 인증, 프로젝트 맞춤 설정까지 자동으로 안내합니다.
Codex-compatible wrapper for the shared vibe-doctor project initialization workflow.
| name | vibe-iterate |
| description | Start the next project iteration after the initial Sprint roadmap is complete. |
Use this skill after the first Sprint roadmap is complete and the user wants to continue the project into another iteration. The goal is to inherit prior context through durable files while keeping each Planner call fresh-context.
/vibe-iterate creates the next iteration from the latest handoff,
project-report.html, and iteration-history.json. It carries forward open
work, accepted decisions, and new user goals without replaying old context into
Planner.
Follow these shards in order. The main file is intentionally an index plus the context isolation guarantee so Codex wrapper injection can load the full iteration workflow transitively.
.claude/skills/vibe-iterate/phases/phase-0-load-state.md.claude/skills/vibe-iterate/phases/phase-1-differential-interview.md.claude/skills/vibe-iterate/phases/phase-2-roadmap-history.md.claude/skills/vibe-iterate/phases/phase-4-sprints-report.mdPlanner remains fresh-context per Sprint. Iteration state crosses boundaries
only through .vibe/agent/iteration-history.json,
docs/reports/project-report.html, the active docs/plans/sprint-roadmap.md,
archived roadmap slices under docs/plans/archive/roadmaps/, and short
Orchestrator-authored prior-sprint summaries.