Vibe-Coder

What it is

A structured development workflow over MCP. It walks a feature from clarifying questions to a PRD and implementation plan, then into phases and tasks whose status the agent updates as it works.

What you get

• start_feature_clarification — begin the guided questioning for a new feature
• provide_clarification — answer those questions and build up the requirements
• generate_prd — produce a Product Requirements Document and an implementation plan from the clarified requirements
• create_phase and add_task — break the plan into development phases with tasks under each
• update_phase_status and update_task_status — record progress as work lands
• get_next_phase_action — ask what to do next rather than deciding from memory
• get_document_path and save_document — find a generated document, or write it to a location you choose
• Generated documents are written to disk automatically and kept in memory for quick access
• A feature-planning prompt template for the whole flow

Requirements

Node with the project cloned and built; the client is pointed at the built server file. No API keys. Documents land in a documents directory keyed by feature id, with the PRD and implementation plan under fixed names, unless you save them elsewhere.

Setup effort

Build from source

Tools you get

10 tools named in the project's documentation.

Where it runs

The documented client runs the server on your machine.