Migrate Core Code to Submodules
tinyhumansai/openhuman
Plans and carries out moving non-host-specific code and its tests from the OpenHuman core into vendored tiny submodule libraries, then releases the submodule and re-pins the host.
Runs a multi-phase project from an orchestrating main thread that plans, routes and verifies but does not build.
Install Vibe Workstream Orchestration
$ npx skills add ash1794/vibe-engineering --skill vibe-workstream-orchestration -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ash1794/vibe-engineering vibe-workstream-orchestration --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-workstream-orchestration .claude/skills/vibe-workstream-orchestration && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "vibe-workstream-orchestration" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-workstream-orchestration into .claude/skills/vibe-workstream-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-workstream-orchestration", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-workstream-orchestrationType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ash1794/vibe-engineering --skill vibe-workstream-orchestration -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ash1794/vibe-engineering vibe-workstream-orchestration --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-workstream-orchestration .agents/skills/vibe-workstream-orchestration && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "vibe-workstream-orchestration" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-workstream-orchestration into .agents/skills/vibe-workstream-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-workstream-orchestration", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ash1794/vibe-engineering --skill vibe-workstream-orchestration -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ash1794/vibe-engineering vibe-workstream-orchestration --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-workstream-orchestration .cursor/skills/vibe-workstream-orchestration && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "vibe-workstream-orchestration" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-workstream-orchestration into .cursor/skills/vibe-workstream-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-workstream-orchestration", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ash1794/vibe-engineering.git --path plugins/vibe-engineering/skills/vibe-workstream-orchestration--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ash1794/vibe-engineering --skill vibe-workstream-orchestration -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ash1794/vibe-engineering vibe-workstream-orchestration --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-workstream-orchestration .gemini/skills/vibe-workstream-orchestration && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "vibe-workstream-orchestration" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-workstream-orchestration into .gemini/skills/vibe-workstream-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-workstream-orchestration", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ash1794/vibe-engineering vibe-workstream-orchestrationInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ash1794/vibe-engineering --skill vibe-workstream-orchestration -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-workstream-orchestration .github/skills/vibe-workstream-orchestration && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "vibe-workstream-orchestration" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-workstream-orchestration into .github/skills/vibe-workstream-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-workstream-orchestration", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ash1794/vibe-engineering --skill vibe-workstream-orchestration -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ash1794/vibe-engineering vibe-workstream-orchestration --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ash1794/vibe-engineering.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/vibe-engineering/skills/vibe-workstream-orchestration .opencode/skills/vibe-workstream-orchestration && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "vibe-workstream-orchestration" agent skill from https://github.com/ash1794/vibe-engineering/tree/master/plugins/vibe-engineering/skills/vibe-workstream-orchestration into .opencode/skills/vibe-workstream-orchestration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "vibe-workstream-orchestration", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
vibe-workstream-orchestration- GitHub stars
- 163
- Token cost
- ~1.1k tokens
- SKILL.md length
- 597 words
- Files
- 1
- Skills in repo
- 33
- Repo updated
- First seen
- Licence
- MIT
At a glance
Runs a multi-phase project from an orchestrating main thread that plans, routes and verifies but does not build.
- Works in 8 steps: Define workstreams by file ownership.… → Record the base. Note the base commit… → Brief once, for the whole phase. Each… → …
- A project spans several phases
- SKILL.md covers When to Use This Skill, When NOT to Use This Skill, Steps and Output Format
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Vibe Workstream Orchestration is an agent skill from ash1794/vibe-engineering. Runs a multi-phase project from an orchestrating main thread that plans, routes and verifies but does not build. Defines a few long-lived workstreams, each owning a file area end to end in its own worktree, and routes every follow-up to the owning agent instead of spawning a one-off. Covers base-SHA recording, rebase-before-commit, stale-checkout detection, and shared-machine hygiene (ports, processes, measurement noise). Use when a project spans several phases or sessions with three or more agents working at once.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Git worktrees. The repository describes itself as: 33 engineering discipline skills for Claude Code, OpenAI Codex & Gemini CLI + a CLI for CI/CD enforcement. Extracted from real-world multi-agent system development. Born from… The licence is MIT.
When your agent uses it
- A project spans several phases
- Sessions with three
- More agents working at once
Example prompts
- “/vibe-workstream-orchestration”
Workflow steps
8 steps, taken from the first numbered list in SKILL.md.
- Define workstreams by file ownership. Use three to eight streams, each owning a set of paths end to end. For each stream, write down…
- Record the base. Note the base commit SHA and branch for the phase. Each writing stream gets its own worktree (or clone) from that base…
- Brief once, for the whole phase. Each brief contains the ownership map, the gates, the commit rule ("rebase onto the remote branch…
- Owners do the whole loop. Each stream builds, verifies, commits and pushes its own work. Don't spawn separate committer, fixer, or…
- Route, don't spawn. Send each new request, review finding, or CI failure to the stream that owns the file, as a message to the running…
- Distrust every checkout. Before building or committing, compare the working tree to the remote branch. A clean local build can depend on…
- Keep the machine fair. Worktrees isolate files, not the machine. Give each agent a private port and a distinct server process. Record…
- Gate the combined head. After the streams land, run the full gates on the integrated commit, not per stream. Route failures back to their…
What it can do on your machine
Read from SKILL.md and the folder at commit 8f1d71b. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Vibe Workstream Orchestration loads about 1.1k tokens when it runs. Until then it costs about 138 tokens; SKILL.md has 597 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from ash1794/vibe-engineering at commit 8f1d71b, republished under its MIT licence (© ash1794). 597 words, ~1,121 tokens.
Download SKILL.mdSave it as
.claude/skills/vibe-workstream-orchestration/SKILL.md (or your agent's skills folder).- name
- vibe-workstream-orchestration
- description
- Runs a multi-phase project from an orchestrating main thread that plans, routes and verifies but does not build. Defines a few long-lived workstreams, each owning a file area end to end in its own worktree, and routes every follow-up to the owning agent instead of spawning a one-off. Covers base-SHA recording, rebase-before-commit, stale-checkout detection, and shared-machine hygiene (ports, processes, measurement noise). Use when a project spans several phases or sessions with three or more agents working at once.
- user-invocable
- true
vibe-workstream-orchestration
vibe-parallel-task-decomposition answers "what can run at once?" This skill answers the next question: who owns what for the rest of the project, and what does the main thread do while they work? The main thread plans, routes and verifies. If it starts building, its context fills with detail and parallelism collapses. If it delegates reactively, every request becomes a new agent that needs a fresh brief, and nobody owns the result.
When to Use This Skill
- A build runs over several phases (build, review, fix, QA) with three or more agents at once
- The task list is filling with agents that did one thing (commit, fix one CI failure, write a PR description)
- Agents are colliding: the same files, the same port, a branch moved under someone
- The main thread's context is filling with build output instead of decisions
When NOT to Use This Skill
- One agent can do the work in one sitting
- A one-shot fan-out with no follow-ups (use
vibe-parallel-task-decomposition) - The work is all in one file or in tightly coupled files
- The harness can't message a running agent (define streams anyway, but expect to re-brief)
Steps
Define workstreams by file ownership. Use three to eight streams, each owning a set of paths end to end. For each stream, write down: paths owned, acceptance criteria, gates it must pass, and paths it must not touch. Shared files (global styles, layout, config) get exactly one owner; other streams request changes to them through the orchestrator.
Record the base. Note the base commit SHA and branch for the phase. Each writing stream gets its own worktree (or clone) from that base. Read-only agents (reviewers, auditors) can share one.
Brief once, for the whole phase. Each brief contains the ownership map, the gates, the commit rule ("rebase onto the remote branch, rebuild, run gates, then push; never force"), and a bounded report format. Ask for conclusions, not file dumps.
Owners do the whole loop. Each stream builds, verifies, commits and pushes its own work. Don't spawn separate committer, fixer, or description-writer agents.
Route, don't spawn. Send each new request, review finding, or CI failure to the stream that owns the file, as a message to the running agent. Spawn a new agent only for a new file area or a new phase.
Distrust every checkout. Before building or committing, compare the working tree to the remote branch. A clean local build can depend on another agent's uncommitted edit in a shared tree, which CI won't have. If the main checkout is behind or dirty, find out which commit it matches before you reset it.
Keep the machine fair. Worktrees isolate files, not the machine. Give each agent a private port and a distinct server process. Record machine load alongside any timing measurement, and don't trust results taken under heavy load (
vibe-flake-root-cause). Each agent stops the servers it started.Gate the combined head. After the streams land, run the full gates on the integrated commit, not per stream. Route failures back to their owners. Then remove worktrees and stale branches. A subagent may not be able to remove its own worktree, so the orchestrator cleans up.
Show full SKILL.md (64 more words)Show less
Output Format
Workstream Plan: [phase]
Base: [branch] @ [sha] · Streams: N · Gates: [list]
| Stream | Owns (paths) | Must not touch | Acceptance | Gates |
|---|---|---|---|---|
| WS1 routing | app/routes, lib/redirects | global styles | all old URLs redirect | build, route check |
Routing Log
| Item | Source | Routed to | Status |
|---|---|---|---|
| CSS over budget on /x | perf gate | WS3 | fixed abc1234 |
Integration
- Combined head: [sha] · gates: [pass/fail per gate]
- Worktrees removed: [list] · open items: [list]
© ash1794, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in plugins/vibe-engineering/skills/vibe-workstream-orchestration of ash1794/vibe-engineering.
Open the folder on GitHubat commit 8f1d71b
Compare with similar skills
Vibe Workstream Orchestration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Vibe Workstream Orchestration this skillash1794/vibe-engineering | 163 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Migrate Core Code to Submodulestinyhumansai/openhuman | 42k | — | ~2.6k | Automated safety check: Pass | GPL-3.0 | |
| Build Px4 macOSPX4/PX4-Autopilot | 13k | — | ~1.1k | Automated safety check: Pass | BSD-3-Clause | |
| Git Worktree IsolationjnMetaCode/superpowers-zh | 8.3k | 1 repos | ~982 | Automated safety check: Pass | MIT | |
| WorktreeAgentsMesh/AgentsMesh | 2.4k | — | ~553 | Automated safety check: Notes | Custom licence | |
| Cursor Composer Task DelegateChachamaru127/claude-code-harness | 3.2k | — | ~4.4k | Automated safety check: Notes | MIT |
Similar skills
Build Px4 macOS
PX4/PX4-Autopilot
Build PX4 board firmware on macOS in the px4-dev Docker container, including git worktrees, and stage commit-labeled artifacts without flashing hardware.
Git Worktree Isolation
jnMetaCode/superpowers-zh
Sets up an isolated workspace before feature work or plan execution, preferring native worktree tools and falling back to git worktree, with instructions in Chinese.
Worktree
AgentsMesh/AgentsMesh
Creates or reuses an isolated AgentsMesh Git worktree from a verified base branch, preserves existing changes, and optionally starts the worktree-scoped development environment.
Cursor Composer Task Delegate
Chachamaru127/claude-code-harness
Hands one implementation task to Cursor Composer in an isolated git worktree, then reviews its diff and cherry-picks the result into the main branch.
Git Worktree Setup
k8zdev/k8z
Automate git worktree creation and copy private files (not tracked in git) to new workdirs.
More from ash1794/vibe-engineering
All 33 skills in this repoVibe Concurrent Test Safety
ash1794/vibe-engineering
Audits tests for concurrency safety — race conditions, shared mock state, cleanup ordering.
Vibe Fuzz Parser Inputs
ash1794/vibe-engineering
Generates fuzz test scaffolding for parsers handling external input (YAML, JSON, config files, user input).
Vibe Golden File Testing
ash1794/vibe-engineering
Implements snapshot/golden file tests with temporal normalization so tests don't break daily.
Vibe Parallel Task Decomposition
ash1794/vibe-engineering
Analyzes large tasks for independent subtasks that can be safely parallelized.
Vibe Slop Filter
ash1794/vibe-engineering
Strips AI-generation "smell" from prose before it ships (READMEs, docs, release notes, PR descriptions, posts, emails).
Vibe Spec Sync
ash1794/vibe-engineering
Keeps specification documents and code in agreement. An agent skill from ash1794/vibe-engineering.
Related
Categories
Questions about Vibe Workstream Orchestration
What does Vibe Workstream Orchestration do?
Runs a multi-phase project from an orchestrating main thread that plans, routes and verifies but does not build. Vibe Workstream Orchestration is an agent skill from ash1794/vibe-engineering. Runs a multi-phase project from an orchestrating main thread that plans, routes and verifies but does not build.
When should I use Vibe Workstream Orchestration?
Vibe Workstream Orchestration fits situations like: A project spans several phases; sessions with three; more agents working at once.
How do I install Vibe Workstream Orchestration in Claude Code?
Run `npx skills add ash1794/vibe-engineering --skill vibe-workstream-orchestration -a claude-code`. Or copy the skill folder (plugins/vibe-engineering/skills/vibe-workstream-orchestration in ash1794/vibe-engineering) into .claude/skills/vibe-workstream-orchestration in your project. Claude Code loads it when a task matches its description.
How do I install Vibe Workstream Orchestration in Codex?
Run `npx skills add ash1794/vibe-engineering --skill vibe-workstream-orchestration -a codex`. Or copy the skill folder (plugins/vibe-engineering/skills/vibe-workstream-orchestration in ash1794/vibe-engineering) into .agents/skills/vibe-workstream-orchestration in your project. Codex loads it when a task matches its description.
Can I use Vibe Workstream Orchestration in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ash1794/vibe-engineering --skill vibe-workstream-orchestration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/vibe-workstream-orchestration, .gemini/skills/vibe-workstream-orchestration, .github/skills/vibe-workstream-orchestration and .opencode/skills/vibe-workstream-orchestration in your project.
What does Vibe Workstream Orchestration need to run?
SKILL.md names no scripts, command-line tools or credentials: Vibe Workstream Orchestration is instructions for the agent only.
Does Vibe Workstream Orchestration access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Vibe Workstream Orchestration safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Vibe Workstream Orchestration use?
Vibe Workstream Orchestration is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Vibe Workstream Orchestration use?
About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Vibe Workstream Orchestration?
Skills that share tags, products or a category with Vibe Workstream Orchestration: Migrate Core Code to Submodules (tinyhumansai/openhuman, 42k stars), Build Px4 macOS (PX4/PX4-Autopilot, 13k stars), Git Worktree Isolation (jnMetaCode/superpowers-zh, 8.3k stars) and Worktree (AgentsMesh/AgentsMesh, 2.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Vibe Workstream Orchestration?
ash1794 (a GitHub user) maintains it in ash1794/vibe-engineering, which has 163 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 7, 2026.
Source: ash1794/vibe-engineering on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.