skills.rest
paleo
paleoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

vibe-flow

Generate specs, plans, and PR messages for ticket-driven AI workflows.

84|7|Updated Aug 4, 2025
Search Tags:#workflow#spec#plan#agent-skills#pr-message#dtdp
One-click install
npx skills add https://github.com/paleo/vibe-flow --skill vibe-flow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vibe-flow
Source: https://github.com/paleo/vibe-flow/tree/main/.claude/skills/vibe-flow
Command: npx skills add https://github.com/paleo/vibe-flow --skill vibe-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Vibe Flow provides a lightweight, protocol-driven workflow for AI agents to convert ideas into structured work artefacts: specs, plans, and handovers, reducing back-and-forth and maintaining an auditable history.

Core Features & Use Cases

  • Spec generation: collaborate to write precise technical specifications before coding.
  • Plan generation: translate a spec into executable implementation steps and orchestration.
  • Discuss-Then-Do (DTDP): a guided, discussion-first approach for small tasks.
  • PR message generation: produce concise PR summaries from completed work.
  • Workflow continuity: stores artifacts in a local, git-ignored workspace to enable resuming tasks later.

Quick Start

  1. Install the vibe-flow skill as described in the installation prompt.
  2. Start a ticket-driven workflow by asking the agent to write a spec for a task (e.g., "Help me write a spec for feature X"). Then generate plans and a handover as you go.
  3. When ready to close a task, generate a PR message summarizing the changes and push the update.

Frequently Asked Questions about vibe-flow

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

FAQPage Schema
How do I automate spec and plan generation for AI agent workflows?▼

Spec-driven workflows automate the creation of technical specifications and implementation plans by applying protocol-driven templates to ticket-based tasks. Vibe Flow converts ideas into structured artifacts—specs, plans, and handover summaries—stored in a local _plans directory with standardized file naming (A1-spec.md, A2-plan.md, A3-summary.md), reducing back-and-forth and maintaining an auditable history.

What's the best way to structure handover documentation for completed work?▼

Handover documentation follows the discuss-then-do (DTDP) protocol, generating concise PR messages and summaries from completed work artifacts. Vibe Flow enforces protocol reference files and per-ticket organization in a git-ignored workspace, enabling resumable tasks and clear handoff between agents without manual re-documentation.

Can I use protocol-driven workflows with ticket-based project management?▼

Yes. Vibe Flow applies to ticket-driven workflows that use spec, plan, and DTDP protocols with organized _plans directories. It manages TASK_DIR per-ticket structure and protocol reference files (spec-protocol.md, plan-protocol.md, dtdp-protocol.md, pr-message-protocol.md), supporting both collaborative spec writing and automated plan generation from specifications.

How do I generate PR messages from completed implementation work?▼

PR message generation translates completed work artifacts into concise pull request summaries using the pr-message-protocol.md template. Vibe Flow extracts changes from your spec, plan, and implementation artifacts to produce structured handover summaries that document what was done and why.

What happens if my generated documentation has lint issues?▼

Vibe Flow tolerates lint issues in generated docs, prioritizing workflow continuity and artifact completion over strict formatting compliance. Protocol-driven generation focuses on content structure and auditability; minor lint violations do not block task progression or artifact storage.

Can I resume workflows after closing a task?▼

Yes. Vibe Flow stores all artifacts—specs, plans, and handovers—in a local git-ignored _plans workspace, enabling you to resume tasks later. Per-ticket organization and consistent file naming (A1-spec.md, A2-plan.md, A3-summary.md) make it straightforward to pick up where you left off without re-documenting prior work.

Related Skills

Explore More Software Engineering Skills→
duronextduronext
15

pr-create

Create pull requests with descriptions and test plans from branch commits using gh.

Official
Advanced
adryanmoldokkr32-pixeladryanmoldokkr32-pixel

land-and-deploy

Merge pull requests, monitor CI, deploy to production, and verify health with canary checks.

Community
Intermediate
basilisk-labsbasilisk-labs
72

agentplane

Plan, execute, and verify AI agent tasks with git-native evidence.

Official
Advanced
JsplixJsplix

git-commit

Generate standardized conventional commit messages for the AX-WMS monorepo.

Community
Intermediate