vibeeval/vibecosystem/build
- community
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/buildSKILL.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
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
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"):
Phase 1: Project Context
Mapping:
- "New feature from scratch" → greenfield mode
- "Adding to existing codebase" → brownfield mode
- "Refactoring existing code" → refactor mode
If Answer is Unclear (via "Other"):
Phase 2: Requirements Clarity
Mapping:
- "Clear spec" → --skip-discovery
- "Rough idea" → run discovery-interview first
- "Exploring" → run discovery-interview with broader scope
If Answer is Unclear (via "Other"):
Phase 3: Development Approach
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"):
Phase 4: Post-Implementation
Mapping:
- No "Auto-commit" selected → --skip-commit
- No "Create PR" selected → --skip-pr
If Answer is Unclear (via "Other"):
Phase 5: Description
Finally, ask for the feature description:
Summary Before Execution
Before starting, show what will run:
This ensures the user knows exactly what will happen before any agents spawn.
Modes
| Mode | Chain | Use Case | |
|---|---|---|---|
greenfield | discovery-interview -> plan-agent -> validate-agent -> implement_plan -> commit -> describe_pr | New feature from scratch | |
brownfield | onboard -> research-codebase -> plan-agent -> validate-agent -> implement_plan | Feature in existing codebase | |
tdd | plan-agent -> test-driven-development -> implement_plan | Test-first implementation | |
refactor | tldr-code (impact) -> plan-agent -> test-driven-development -> implement_plan | Safe refactoring with impact analysis |
Options
| Option | Effect | |
|---|---|---|
--skip-discovery | Skip interview phase (use existing spec or description) | |
--skip-validate | Skip validation phase (trust plan as-is) | |
--skip-commit | Don't auto-commit after implementation | |
--skip-pr | Don't create PR description | |
--parallel | Run independent research agents in parallel |
Handoff Directory
All handoffs go to: thoughts/shared/handoffs/<session>/
Session name derived from:
- Existing continuity ledger name, OR
- Generated from feature description:
build-<date>-<kebab-description>
Orchestration Process
Step 0: Parse Arguments
Parse the mode and options from user input:
Build the skill chain based on mode:
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
- Create handoff directory:
``bash SESSION="build-$(date +%Y%m%d)-<kebab-description>" mkdir -p "thoughts/shared/handoffs/$SESSION" ``
- 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
Skill Execution Details
discovery-interview:
Output: Spec file at thoughts/shared/specs/<name>-spec.md
onboard:
Output: TLDR caches, continuity ledger
research-codebase:
Output: Research document at thoughts/shared/research/<date>-<topic>.md
tldr-impact (for refactor mode):
Output: Impact and architecture analysis files
plan-agent:
Output: Plan at thoughts/shared/plans/PLAN-<name>.md, handoff at <session>/plan-<name>.md
CHECKPOINT: After plan-agent
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
- SKILL.md in the repositoryCheckingskills/build/SKILL.md
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
[](https://verified-skill.com/skills/vibeeval/vibecosystem/build)