vibeflow-implement

Name: vibeflow-implement
Availability: InStock
Author: pe-menezes

Implements software features from detailed specs with budget, scope, and coding pattern constraints.

29|2|Updated Mar 3, 2026

Search Tags:#automation #testing #implementation #coding #spec #guardrails

Ready to run

npx skills add https://github.com/pe-menezes/vibeflow --skill vibeflow-implement

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: vibeflow-implement
Source: https://github.com/pe-menezes/vibeflow/tree/main/cursor/skills/vibeflow-implement
Command: npx skills add https://github.com/pe-menezes/vibeflow --skill vibeflow-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the implementation of software features based on detailed specifications, ensuring adherence to predefined constraints like budget, scope, and coding patterns.

Core Features & Use Cases

Spec-driven Implementation: Translates a feature specification into working code.
Guardrail Enforcement: Strictly follows budget (file limits), anti-scope rules, and project patterns.
Automated Testing & Verification: Runs tests and self-verifies against the Definition of Done (DoD).
Use Case: After an architect defines a new user authentication flow in a spec, this Skill can be used to write the necessary backend code, frontend components, and tests, ensuring it matches the architect's exact requirements and project standards.

Quick Start

Use the vibeflow-implement skill to implement the feature described in the spec file located at .vibeflow/specs/user-auth.md.

Frequently Asked Questions about vibeflow-implement

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate coding from a feature specification while enforcing scope and budget limits?▼

Spec-driven implementation automates coding by translating detailed feature specifications into working code while strictly enforcing guardrails like file limits, anti-scope rules, and established project patterns.

What is the best way to implement a software feature and automatically verify it against a Definition of Done?▼

Automated implementation pipelines execute spec validation, context loading, planning, coding, testing, and self-verification to ensure the final code strictly matches the project's Definition of Done.

How does a coding agent execute spec validation and context loading for new software features?▼

A coding agent executes spec validation and context loading by running a multi-phase pipeline that validates the feature specification, loads project context, and plans the coding execution before writing any code.

Can I use automated implementation to write backend code and frontend components from an architect's spec?▼

Yes, automated spec-driven implementation can write backend code, frontend components, and tests from a detailed specification, ensuring the output matches the architect's exact requirements and coding patterns.

What are the limitations of using a coding agent for spec-driven implementation?▼

The primary limitation is that the coding agent focuses solely on execution as defined by the architect, meaning it requires a pre-existing detailed specification and strict guardrails to function correctly.

Do I need a detailed specification file before starting automated feature implementation?▼

Yes, you need a detailed specification file located in your project directory, as the implementation process relies entirely on this spec to validate constraints and execute the coding pipeline.