Skip to content

Add vibe-flow skill (multi-agent orchestration for vibe-kanban)#567

Open
OdinHoang03 wants to merge 1 commit into
davila7:mainfrom
OdinHoang03:add-vibe-flow-skill
Open

Add vibe-flow skill (multi-agent orchestration for vibe-kanban)#567
OdinHoang03 wants to merge 1 commit into
davila7:mainfrom
OdinHoang03:add-vibe-flow-skill

Conversation

@OdinHoang03
Copy link
Copy Markdown

@OdinHoang03 OdinHoang03 commented May 6, 2026

Summary

Adds a new skill: vibe-flow under skills/workflow-automation/vibe-flow/.

vibe-flow is a Claude Code plugin that orchestrates the full spec-to-merge lifecycle on a vibe-kanban board:

  • plan — decompose a spec into an issue tree (epic + sub-issues + deps)
  • ship — wave-based parallel dispatch with tier-based executor routing (T0 Gemini flash through T4 Opus)
  • link — auto-open / link the GitHub PR for each workspace branch
  • review — two-stage code review (spec compliance, then quality), posted to PR
  • merge — verify CI green, rebase, squash merge, archive workspace
  • Plus: dispatch-fix, rebase, status, standup, and a meta vibe-flow orchestrator

The skill file points users to the upstream plugin (which is the source of truth) so we don't duplicate the 11 individual slash-command files in this registry.

Test plan

  • SKILL.md placed at cli-tool/components/skills/workflow-automation/vibe-flow/SKILL.md
  • Frontmatter: name, description, author, license, metadata.version/homepage/repository
  • Description is action-oriented ("Use when the user wants to...")
  • Install instructions, prerequisites, and external links included
  • No bypass-permissions, no telemetry beyond the vibe-kanban MCP server and GitHub API

Links


Summary by cubic

Adds a new vibe-flow skill that orchestrates spec-to-merge workflows on a vibe-kanban board via the upstream Claude Code plugin. Provides install steps and command references without changing runtime code.

  • Area: components (cli-tool/components/)
  • Added skills/workflow-automation/vibe-flow/SKILL.md with install/prereqs and commands (vibe-init, vibe-plan, vibe-ship, vibe-link, vibe-review, vibe-merge, vibe-dispatch-fix, vibe-rebase, vibe-status, vibe-standup, vibe-flow)
  • References the upstream vibe-flow plugin; no CLI/API runtime changes
  • New component added — regenerate catalog (docs/components.json)
  • No new env vars or secrets; requires gh auth and vibe-kanban MCP server configuration

Written for commit fee15ff. Summary will update on new commits.

@vercel
Copy link
Copy Markdown

vercel Bot commented May 6, 2026

@OdinHoang03 is attempting to deploy a commit to the Daniel Avila's projects Team on Vercel.

A member of the Team first needs to authorize it.

@github-actions github-actions Bot added the review-pending Component PR awaiting maintainer review label May 6, 2026
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 6, 2026

👋 Thanks for contributing, @OdinHoang03!

This PR touches cli-tool/components/** and has been marked review-pending.

What happens next

  1. 🤖 Automated security audit runs and posts results on this PR.
  2. 👀 Maintainer review — a human reviewer validates the component with the component-reviewer agent (format, naming, security, clarity).
  3. Merge — once approved, your PR is merged to main.
  4. 📦 Catalog regeneration — the component catalog is rebuilt automatically.
  5. 🚀 Live on aitmpl.com — your component appears on the website after deploy.

While you wait

  • Check the Security Audit comment below for any issues to fix.
  • Make sure your component follows the contribution guide.

This is an automated message. No action is required from you right now — a maintainer will review soon.

Copy link
Copy Markdown
Contributor

@cubic-dev-ai cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1 issue found across 1 file

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="cli-tool/components/skills/workflow-automation/vibe-flow/SKILL.md">

<violation number="1" location="cli-tool/components/skills/workflow-automation/vibe-flow/SKILL.md:32">
P2: Custom agent: **Component Reviewer**

Uses a home-directory path (`~/.claude.json`) in a component file, which conflicts with the rule's prohibition on absolute paths.</violation>
</file>

Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.

/reload-plugins
```

Configure the vibe-kanban MCP server in `~/.claude.json`:
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2: Custom agent: Component Reviewer

Uses a home-directory path (~/.claude.json) in a component file, which conflicts with the rule's prohibition on absolute paths.

Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At cli-tool/components/skills/workflow-automation/vibe-flow/SKILL.md, line 32:

<comment>Uses a home-directory path (`~/.claude.json`) in a component file, which conflicts with the rule's prohibition on absolute paths.</comment>

<file context>
@@ -0,0 +1,95 @@
+/reload-plugins
+```
+
+Configure the vibe-kanban MCP server in `~/.claude.json`:
+
+```json
</file context>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

review-pending Component PR awaiting maintainer review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant