vibe-workstream-orchestration SKILL.md skillA
vibe-workstream-orchestration from ash1794/vibe-engineering is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ash1794/vibe-engineering/vibe-workstream-orchestration@git:20260928.7d7cde1Pins git:20260928.7d7cde1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ash1794/vibe-engineering
- Path
plugins/vibe-engineering/skills/vibe-workstream-orchestration/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260928.7d7cde1, committed Sep 28, 2026
- Size
- 4,486 bytes
- Repository stars
- 165
- License
- MIT
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…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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 …
Read the whole file at its exact version.
How to install
mdr add ash1794/vibe-engineering/vibe-workstream-orchestration@sha256:7c252230d05156edThe line at the top of this page pins the label git:20260928.7d7cde1, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_5i3ogshk7rjmskeu)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 28, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4486 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
ash1794/vibe-engineering · 165 stars · license MIT · pushed 2026-10-07 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_5i3ogshk7rjmskeu GET https://markdownregistry.com/api/v1/resolve?ref=ash1794/vibe-engineering/vibe-workstream-orchestration GET https://markdownregistry.com/api/v1/blob/7c252230d05156ede9f76db78a8a906f9209a3591e48adcdbf9c320842cfe64f
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.