vibe

Automate end-to-end software development workflows with blueprint-backed pipeline stages.

8|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/jfmyers9/agent --skill vibe-jfmyers9
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vibe
Source: https://github.com/jfmyers9/agent/tree/main/skills/vibe
Command: npx skills add https://github.com/jfmyers9/agent --skill vibe-jfmyers9

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end software development workflows by chaining research, implementation, review, fix, report, commit, and submission into a single, repeatable process.

Core Features & Use Cases

  • End-to-end automation: orchestrates research, implementation, review, and release steps based on blueprint plans.
  • Blueprint-backed workflow: uses portable plan/state artifacts to track progress across stages.
  • Traceable artifacts: creates and stores plan, context, and results for audits and reviews.

Quick Start

Provide a prompt to start the autonomous Vibe pipeline.

Frequently Asked Questions about vibe

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

FAQPage Schema
How do I automate my software development pipeline end-to-end?

Automate end-to-end software development workflows by chaining research, implementation, review, fix, report, commit, and submission stages into a single, repeatable pipeline process.

What is a blueprint-driven development workflow?

A blueprint-driven development workflow uses portable plan and state artifacts to orchestrate multi-stage automation, tracking progress across research, implementation, and release steps.

How do I start an autonomous development pipeline using YAML frontmatter?

Start the autonomous pipeline by providing an initial prompt, which triggers blueprint-backed execution stages defined through YAML frontmatter and blueprint scripts.

Can I track artifacts across multiple pipeline stages?

Yes, traceable artifacts including plan, context, and results are created and stored throughout the workflow to enable audits, cross-stage coordination, and review.

Does automated software workflow execution support cross-stage coordination?

Yes, cross-stage coordination is supported through YAML frontmatter and blueprint scripts, ensuring structured pipeline stages and traceable artifacts across the entire development workflow.

What's the best way to structure a multi-stage software automation pipeline?

Structure multi-stage software automation pipelines by chaining research, implementation, review, fix, report, commit, and submit stages using blueprint-backed execution and traceable artifacts.