vbounce

V-Bounce SDLC Orchestrator v5.1

Agent-first SDLC framework with explicit contracts, shared workspace, state management, unified TDD, and per-phase specialized QG agents.

Based on arXiv 2408.03416 (Hymel, 2024): AI handles implementation, humans shift to validators/verifiers.

Core Principles

1. Agent-First — agents are the execution units; orchestrator manages state and contracts
2. Explicit Contracts — every agent declares input/output files with validation patterns
3. Shared Workspace — all artifacts live in .vbounce/cycles/{cycle_id}/
4. State Machine — orchestrator reads/writes state.yaml, determines next action
5. Multi-Layer QA — input validation, output validation, semantic QG, cross-agent compatibility
6. 7-Activity Phase Anatomy — see references/phase-anatomy.md
7. Technology-Aware — detect project tech stack and inject framework context into all agent dispatches

Cycle Initialization

When the user provides a PRD or says "start vbounce cycle":

1. Generate cycle ID: CYCLE-{PROJECT}-{YYYYMMDD}-{SEQ} (derive PROJECT from directory name, SEQ starts at 001)
2. Create workspace: mkdir -p .vbounce/cycles/{cycle_id}/{requirements,design,contracts,implementation,review,deployment,knowledge,quality-gates}
3. Copy PRD: Write/copy the user's PRD to .vbounce/cycles/{cycle_id}/prd.md
4. Tech Stack Detection: Scan the project for manifest files to detect the tech stack:
   • Check in order: package.json (JS/TS), pyproject.toml / requirements.txt (Python), *.csproj (C#), go.mod (Go), Cargo.toml (Rust), pom.xml / build.gradle (Java/Kotlin)
   • Read CLAUDE.md for explicit tech stack declarations (overrides auto-detection)
   • If no manifest found, scan top 5 source files for import patterns and file extensions
   • Write {workspace}/tech-context.yaml with: language, runtime, package_manager, frameworks (list of {name, version, role}), build_tool, install_command, compile_command, test_command, source_dirs, test_dirs, detected_from
   • Resolve install/compile/test commands per language + package manager — see references/tech-stack-commands.md
5. Framework Context Loading: Based on tech-context.yaml, check for relevant installed skills:
   • For each detected framework, search installed skills for matching trigger phrases (skill descriptions contain framework names)
   • If match found, read that skill's SKILL.md + key reference files
   • Extract: framework patterns, testing conventions, security considerations, known anti-patterns
   • Always check: hallucination-patterns.md for entries matching detected ecosystem, coding-standards.md for detected language, CLAUDE.md for project-specific conventions
   • If no skill matches any detected framework, graceful degradation: agents work without framework context (tech-context-prompt.md will only contain language + framework names + versions)
   • Write {workspace}/tech-context-prompt.md with: primary stack info, key patterns, known hallucination risks, testing conventions
6. Initialize state: Write .vbounce/cycles/{cycle_id}/state.yaml with v5.1 state schema (all phases including contracts set to not_started, current_phase: requirements, anatomy_step: input, tech_context populated from detection)
7. Set active cycle: Write .vbounce/state.yaml with just active_cycle: {cycle_id} and workspace: .vbounce/cycles/{cycle_id}
8. Proceed: Begin requirements phase (validate input contract, dispatch requirements-analyst)