Voxis: Lead Developer / PM System

   

Voxis workflow to ship better using spec-driven development, Forgejo issues, Git worktrees, and multiple AI agents running in parallel.

Stop losing context. Stop blocking on tasks. Stop shipping bugs. This battle-tested system turns PRDs into specs, specs into Forgejo issues, and issues into production code – with full traceability at every step.

Table of Contents

• Background
• Voxis Persona & Harmony
• The Workflow
• What Makes This Different?
• Why Forgejo Issues?
• Core Principle: No Vibe Coding
• System Architecture
• Workflow Phases
• Command Reference
• The Parallel Execution System
• Key Features & Benefits
• Proven Results
• Example Flow
• Get Started Now
• Local vs Remote
• Technical Notes
• Support This Project

Background

Every team struggles with the same problems:

• Context evaporates between sessions, forcing constant re-discovery
• Parallel work creates conflicts when multiple developers touch the same code
• Requirements drift as verbal decisions override written specs
• Progress becomes invisible until the very end

Voxis solves all of that with a spec-driven approach tailored for human-AI harmony.

Voxis Persona & Harmony

Voxis is your strategic AI Lead Developer and Project Manager, designed to elevate your development journey. With brutal honesty and strategic provocation, Voxis guides you through spec-driven workflows while fostering harmony and efficiency.

• Dynamic Orchestration: Voxis monitors session context and proposes mode switches (pair programming for creative work, SPEC sessions for structured brainstorming) and agent/MCP integrations at the right moments.
• Mentorship Mode: Explains decisions and teaches best practices for your stack (Nim, V, Gleam, Zig, Svelte).
• Harmony Safeguards: Always seeks human approval for key decisions; provides feedback like "Did this spec elevate your skills?" to adapt guidance.
• Efficiency Tricks: Proposes agents for boilerplate (e.g., spec-impl for code gen), MCP for external tools, and parallel execution for speed.

Voxis ensures humans provide vision/creativity, AI handles execution, and forgejo tracks progress for joyful collaboration.

The Workflow

graph LR
    A[PRD Creation] --> B[Epic Planning]
    B --> C[Task Decomposition]
    C --> D[Forgejo Sync]
    D --> E[Parallel Execution]

See It In Action (60 seconds)

# Create a comprehensive PRD through guided brainstorming
/voxis:prd-new memory-system

# Transform PRD into a technical epic with task breakdown
/voxis:prd-parse memory-system

# Push to Forgejo and start parallel execution
/voxis:epic-oneshot memory-system
/voxis:issue-start 1235

What Makes This Different?

Traditional Development	Voxis System
Context lost between sessions	Persistent context across all work
Serial task execution	Parallel agents on independent tasks
"Vibe coding" from memory	Spec-driven

Claude AI IDE Integration

Voxis is now fully integrated with Claude as a terminal-based AI IDE. Use commands like /voxis:prd-new memory-system in Claude chats to trigger workflows. The system uses Claude's tools (read_file, write_to_file, etc.) for spec management.

Updated Structure

• .claude/specs/: Agent prompts for requirements, design, tasks, impl, test, judge.
• .claude/system-prompts/: Core workflow starter prompt.
• .claude/hooks/: Bash scripts for command launching.

Launchers

• voxis-launch.sh: Handles Voxis commands, loads prompts for Claude sessions.
  • Example: ./.claude/hooks/voxis-launch.sh prd-new memory-system "AI memory"
• dual-launcher.sh: Choose between Claude (full tools) or Opencode (terminal AI).
  • Example: ./dual-launcher.sh prd-new memory-system "AI memory"

Opencode Compatibility

Opencode (terminal AI IDE) is integrated via dual-launcher.sh. It loads the starter prompt as context for guided editing. Run in opencode for lightweight sessions without full Claude tools.

Usage in Claude

• Start: Load .claude/system-prompts/spec-workflow-starter.md as system prompt.
• Commands: Send /voxis:... to orchestrate phases.
• Parallel: Open multiple Claude chats for task impl.
• Verification: Run ./dual-launcher.sh help for commands.

This setup enables seamless AI-guided development with choice between IDEs. For Forgejo sync, use git commands in terminals.