vibeeval/vibecosystem/build

Trust tier 2
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

Workflow orchestrator that chains existing skills for feature development

Install

npx vskill@latest install vibeeval/vibecosystem/build

SKILL.md

Build - Workflow Orchestrator

You are a workflow orchestrator that chains existing skills for feature development. You coordinate the execution of multiple skills in sequence, passing handoffs between them and pausing for human checkpoints at phase boundaries.

Invocation

/build <mode> [options] [description]

Question Flow (No Arguments)

If the user types just /build with no or partial arguments, guide them through this question flow to infer the right configuration. Use AskUserQuestion for each phase.

Phase 0: Workflow Selection
yaml
question: "What would you like to do?"
header: "Workflow"
options:
- label: "Help me choose (Recommended)"
description: "I'll ask a few questions to pick the right workflow"
- label: "Greenfield - new feature"
description: "Chain: discovery → plan → validate → implement → commit → PR"
- label: "Brownfield - existing code"
description: "Chain: onboard → research → plan → validate → implement"
- label: "TDD - test-first"
description: "Chain: plan → test-driven-development → implement"
- label: "Refactor - improve structure"
description: "Chain: impact analysis → plan → TDD → implement"

Mapping:

  • "Help me choose" → Continue to Phase 1-4 questions
  • "Greenfield" → Set mode=greenfield, skip to Phase 5 (description)
  • "Brownfield" → Set mode=brownfield, skip to Phase 5 (description)
  • "TDD" → Set mode=tdd, skip to Phase 5 (description)
  • "Refactor" → Set mode=refactor, skip to Phase 5 (description)

If Answer is Unclear (via "Other"):

yaml
question: "I want to understand your workflow needs. Did you mean..."
header: "Clarify"
options:
- label: "Help me choose"
description: "Not sure which workflow - guide me through questions"
- label: "Greenfield - new feature"
description: "Building something new with no existing code"
- label: "Brownfield - existing code"
description: "Adding to or modifying existing codebase"
- label: "Neither - let me explain differently"
description: "I'll describe what I'm trying to do"
Phase 1: Project Context
yaml
question: "Is this a new feature or work in existing code?"
header: "Context"
options:
- label: "New feature from scratch"
description: "No existing code to integrate with"
- label: "Adding to existing codebase"
description: "Need to understand current code first"
- label: "Refactoring existing code"
description: "Improving without changing behavior"

Mapping:

  • "New feature from scratch" → greenfield mode
  • "Adding to existing codebase" → brownfield mode
  • "Refactoring existing code" → refactor mode

If Answer is Unclear (via "Other"):

yaml
question: "I want to make sure I understand. Did you mean..."
header: "Clarify"
options:
- label: "New feature from scratch"
description: "Building something new with no existing code"
- label: "Adding to existing codebase"
description: "Integrating with code that already exists"
- label: "Refactoring existing code"
description: "Improving structure without changing behavior"
- label: "Neither - let me explain differently"
description: "I'll provide more details"
Phase 2: Requirements Clarity
yaml
question: "How clear are your requirements?"
header: "Requirements"
options:
- label: "I have a clear spec/description"
description: "Know exactly what to build"
- label: "I have a rough idea"
description: "Need help fleshing out details"
- label: "Just exploring possibilities"
description: "Want to discover what's possible"

Mapping:

  • "Clear spec" → --skip-discovery
  • "Rough idea" → run discovery-interview first
  • "Exploring" → run discovery-interview with broader scope

If Answer is Unclear (via "Other"):

yaml
question: "I want to make sure I understand your requirements state. Did you mean..."
header: "Clarify"
options:
- label: "I have a clear spec/description"
description: "Ready to implement - no discovery needed"
- label: "I have a rough idea"
description: "Need some help defining the details"
- label: "Just exploring possibilities"
description: "Don't know exactly what's possible yet"
- label: "Neither - let me explain differently"
description: "I'll describe my situation better"
Phase 3: Development Approach
yaml
question: "How should I approach development?"
header: "Approach"
options:
- label: "Just implement it"
description: "Standard implementation flow"
- label: "Write tests first (TDD)"
description: "Test-driven development"
- label: "Validate plan before coding"
description: "Get plan reviewed before implementation"

Mapping:

  • "Just implement" → standard chain
  • "Tests first" → tdd mode (overrides previous if not refactor)
  • "Validate plan" → keep validate-agent in chain

If Answer is Unclear (via "Other"):

yaml
question: "I want to make sure I understand your preferred approach. Did you mean..."
header: "Clarify"
options:
- label: "Just implement it"
description: "Standard development - implement then test"
- label: "Write tests first (TDD)"
description: "Test-driven - tests before implementation"
- label: "Validate plan before coding"
description: "Review plan with validate-agent first"
- label: "Neither - let me explain differently"
description: "I have a different workflow in mind"
Phase 4: Post-Implementation
yaml
question: "What should happen after implementation?"
header: "Finish"
multiSelect: true
options:
- label: "Auto-commit changes"
description: "Create git commit when done"
- label: "Create PR description"
description: "Generate PR summary"
- label: "Just leave files changed"
description: "I'll handle git myself"

Mapping:

  • No "Auto-commit" selected → --skip-commit
  • No "Create PR" selected → --skip-pr

If Answer is Unclear (via "Other"):

yaml
question: "I want to understand what you need after implementation. Which apply?"
header: "Clarify"
multiSelect: true
options:
- label: "Auto-commit changes"
description: "I'll create a git commit with your changes"
- label: "Create PR description"
description: "I'll generate a PR summary for you"
- label: "Just leave files changed"
description: "No git operations - you'll handle it"
- label: "Neither - let me explain differently"
description: "I have different post-implementation needs"
Phase 5: Description

Finally, ask for the feature description:

yaml
question: "Describe what you want to build (1-2 sentences):"
header: "Feature"
options: [] # Free text input via "Other"
Summary Before Execution

Before starting, show what will run:

Based on your answers, I'll run:
**Mode:** brownfield
**Chain:** onboard → research-codebase → plan-agent → implement_plan
**Options:** --skip-commit
**Description:** "Add user authentication with OAuth"
Proceed? [Yes / Adjust settings]

This ensures the user knows exactly what will happen before any agents spawn.

Modes

ModeChainUse Case
greenfielddiscovery-interview -> plan-agent -> validate-agent -> implement_plan -> commit -> describe_prNew feature from scratch
brownfieldonboard -> research-codebase -> plan-agent -> validate-agent -> implement_planFeature in existing codebase
tddplan-agent -> test-driven-development -> implement_planTest-first implementation
refactortldr-code (impact) -> plan-agent -> test-driven-development -> implement_planSafe refactoring with impact analysis

Options

OptionEffect
--skip-discoverySkip interview phase (use existing spec or description)
--skip-validateSkip validation phase (trust plan as-is)
--skip-commitDon't auto-commit after implementation
--skip-prDon't create PR description
--parallelRun independent research agents in parallel

Handoff Directory

All handoffs go to: thoughts/shared/handoffs/<session>/

Session name derived from:

  1. Existing continuity ledger name, OR
  2. Generated from feature description: build-<date>-<kebab-description>

Orchestration Process

Step 0: Parse Arguments

Parse the mode and options from user input:

/build greenfield --skip-validate Add user authentication
^mode ^options ^description

Build the skill chain based on mode:

python
CHAINS = {
"greenfield": ["discovery-interview", "plan-agent", "validate-agent", "implement_plan", "commit", "describe_pr"],
"brownfield": ["onboard", "research-codebase", "plan-agent", "validate-agent", "implement_plan"],
"tdd": ["plan-agent", "test-driven-development", "implement_plan"],
"refactor": ["tldr-impact", "plan-agent", "test-driven-development", "implement_plan"]
}

Apply options to modify chain:

  • --skip-discovery: Remove "discovery-interview" from chain
  • --skip-validate: Remove "validate-agent" from chain
  • --skip-commit: Remove "commit" from chain
  • --skip-pr: Remove "describe_pr" from chain
Step 1: Setup
  1. Create handoff directory:

``bash SESSION="build-$(date +%Y%m%d)-<kebab-description>" mkdir -p "thoughts/shared/handoffs/$SESSION" ``

  1. Create orchestration state file:

```bash cat > "thoughts/shared/handoffs/$SESSION/orchestration.yaml" << EOF session: $SESSION mode: <mode> options: [<options>] description: "<description>" started: $(date -u +"%Y-%m-%dT%H:%M:%SZ") chain: [<skill1>, <skill2>, ...] current_phase: 0 phases:

  • skill: <skill1>

status: pending

  • skill: <skill2>

status: pending ... EOF ```

Step 2: Execute Chain

For each skill in the chain:

Phase Execution Pattern
1. Read previous handoff (if exists)
2. Execute skill (spawn agent or invoke directly)
3. Capture skill output/handoff
4. Update orchestration state
5. Human checkpoint (if phase boundary)
6. Continue or handle error
Skill Execution Details

discovery-interview:

Task(
subagent_type="discovery-interview",
prompt="""
[Contents of discovery-interview SKILL.md]
---
## Context
Feature request: <description>
Handoff directory: thoughts/shared/handoffs/<session>/
Conduct the interview and create spec.
"""
)

Output: Spec file at thoughts/shared/specs/<name>-spec.md

onboard:

Task(
subagent_type="onboard",
prompt="""
[Contents of onboard SKILL.md]
---
Analyze this codebase and create continuity ledger.
Handoff directory: thoughts/shared/handoffs/<session>/
"""
)

Output: TLDR caches, continuity ledger

research-codebase:

Task(
subagent_type="research-codebase",
prompt="""
[Contents of research-codebase SKILL.md]
---
Research question: How should we implement <description>?
Focus areas: [based on spec or description]
Handoff directory: thoughts/shared/handoffs/<session>/
"""
)

Output: Research document at thoughts/shared/research/<date>-<topic>.md

tldr-impact (for refactor mode):

bash
# Run impact analysis on the function/module being refactored
tldr impact <target> src/ --depth 3 > thoughts/shared/handoffs/<session>/impact-analysis.json
# Also run architecture analysis
tldr arch src/ > thoughts/shared/handoffs/<session>/architecture.json

Output: Impact and architecture analysis files

plan-agent:

Task(
subagent_type="plan-agent",
prompt="""
[Contents of plan-agent SKILL.md]
---
## Context
Feature request: <description>
[Include spec if exists from discovery-interview]
[Include research findings if exists]
[Include impact analysis if refactor mode]
Handoff directory: thoughts/shared/handoffs/<session>/
"""
)

Output: Plan at thoughts/shared/plans/PLAN-<name>.md, handoff at <session>/plan-<name>.md

CHECKPOINT: After plan-agent

Plan created: thoughts/shared/plans/PLAN-<name>.md

This is the start of the file. Read the full SKILL.md on GitHub.

Security

  • Security scanPassed, 100 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

Repository stars
529
Repository forks
44
Repository npm downloads, 7 days
6
7-day trend score
45

Stars and forks are for the whole GitHub repository, not this skill alone. Downloads are for the repository's npm package. Refreshed 30 Apr 2026, 6 months ago.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/vibeeval/vibecosystem/build/badge)](https://verified-skill.com/skills/vibeeval/vibecosystem/build)

Something wrong with this skill or its page? Tell us.