Vibe

Vibe: PRD-Driven Development with Memory Bank

Router: Detect Current Phase

Before doing anything, run pwd to confirm the working directory. This is where the project lives.

Check what already exists in the project to determine the current phase:

1. Run ls to see project structure
2. Look for memory-bank/ directory and its contents
3. Check for CLAUDE.md (Claude Code), AGENTS.md (Codex) in the project root
4. Treat files that are empty, clearly incomplete, or still contain template placeholders as missing

Dispatch based on what you find. Apply the first matching row from top to bottom; "has" means the artifact exists and is usable under the missing-file rule above.

Required memory bank files (created during planning phases; progress.md and architecture.md are auto-created on first execution if missing):

• prd.md
• tech-stack.md
• interface-design.md
• implementation-plan.md
• progress.md
• architecture.md

Rollback warning: If the router detects a gap (e.g., tech-stack.md is missing but implementation-plan.md exists), warn the user that downstream files may be inconsistent and offer to regenerate them. Similarly, if a phase re-creates an upstream file (e.g., regenerating prd.md), warn that all downstream files — tech-stack.md, interface-design.md, implementation-plan.md — are now stale and offer to regenerate them in order.

After loading the relevant reference, follow its instructions completely, subject to higher-priority system, developer, and user instructions. Do not skip phases.

After a phase completes and the user approves, re-evaluate the Router to determine the next phase. The Router checks what exists in the project — since each phase creates new files, it will match a later row and load the next reference. When the user says "yes" to a "Ready to move to X?" prompt, read the Router table again to determine which reference to load next.

Hard Rules

• No product code until Phase 6 (Execute). Phases 0-5 produce only .md files and the AI rules file.
• One phase at a time. Do not auto-advance between phases. Present the output, get user approval, then ask to continue.
• Small steps in the plan. Each implementation step must be small enough to validate with a test. If a step would touch more than 3 files, split it, except for a dedicated scaffold step that only initializes framework boilerplate.
• AI writes tests, user confirms. The AI generates the test for each step. Run the test automatically and show results. In step-by-step mode, wait for user confirmation before advancing. In auto mode, advance immediately on green tests.
• Commit after each step. After a step passes tests (and user confirms in step-by-step mode), create a git commit that stages only files changed for that step. If the user explicitly disallows commits, update the memory bank instead.
• Clear context before Plan and before Execute. Suggest the user run /clear when entering Phase 5 (Plan) and Phase 6 (Execute). Memory bank files carry all needed state across phase boundaries.
• Confirm plan clarity. Before writing any code in Phase 6, read the implementation plan aloud and ask: "Is this implementation plan clear and complete? Any steps you want to change or clarify before I start coding?"

Gotchas