Vibe Engineer: A Document-Driven Development Workflow for AI Collaboration

Vibe Engineer is an open-source tool that helps developers maintain code maintainability in "vibe coding" through structured document workflows, balancing AI-assisted development with traditional engineering discipline. Its core philosophy is "documents as contracts", using Chunks as work units to solve technical debt issues when vibe coding projects scale up, while preserving a smooth development experience.

"Vibe Coding" is highly efficient in the prototyping phase, but it has the problem of "amazing on day one, chaotic on day two"—when projects scale up or require maintenance, code lacking documentation and structure easily becomes technical debt. Vibe Engineer was born to address this; it is not a framework that restricts AI creativity, but a lightweight document workflow that allows developers to enjoy AI acceleration while maintaining code understandability and maintainability.

Vibe Engineer's design philosophy is "good documentation leads to confident code implementation, new code leads to necessary documentation", forming a bidirectional reinforcement loop: before coding, clarify goals and plans through documents; AI generates code based on documents; code changes automatically trigger document updates; documents become contracts for human-AI collaboration. The core work unit is the Chunk, each containing three key documents:

1. Goal Document: Clarifies the problem and value (why);
2. Plan Document: Describes the implementation path (how);
3. Implementation and Retrospection: Automatically updates references and status after code completion to keep documents in sync.

Vibe Engineer is deeply integrated with Claude Code, providing slash commands:

• /chunk-create: Create a new Chunk and refine the goal;
• /chunk-plan: Generate a technical implementation plan;
• /chunk-implement: Execute code implementation;
• /chunk-complete: Update references and mark as completed;
• /chunk-commit: Generate a standardized Git commit. In addition, the ve CLI supports Chunk listing, validation, task directory management, etc. For cross-repository scenarios, it supports task directories and orchestrator mode, allowing parallel execution of multiple Chunks.

The Steward mode is a long-running agent that supports:

• Monitoring message channels like Slack and email;
• Classifying requests according to SOPs;
• Automatically creating Chunks and delegating execution to the orchestrator;
• Publishing result summaries to the change log channel. This mode evolves AI-assisted development from "on-demand calls" to "continuous service", making it suitable for 7x24 operation and maintenance or support scenarios.

Suitable Scenarios:

• Teams that need AI assistance but are worried about code quality getting out of control;
• Projects with multi-person collaboration or human-AI collaboration;
• Production code that requires long-term maintenance;
• Organizations that want to establish reproducible development processes.

Potentially Unsuitable Scenarios:

• One-time scripts or quick prototypes;
• Personal toy projects;
• Large teams that already have mature development processes.

Vibe Engineer represents the evolutionary direction of AI-assisted development tools: establishing structured contracts for human-AI collaboration, acknowledging the value of vibe coding while solving maintainability pain points. As AI coding assistants become more powerful, such "AI-native workflow tools" will become standard components of developers' toolchains—clear context and contracts allow AI to make more accurate judgments and produce high-quality outputs, which are not shackles but a stage for AI to play a greater role.