spec-conductor SKILL.md skillA
spec-conductor from dpalfery/kyber-weave is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add dpalfery/kyber-weave/spec-conductor@v0.1.0Pins v0.1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- dpalfery/kyber-weave
- Path
.apm/skills/spec-conductor/SKILL.md- Versions recorded
- 3
- Latest version
- v0.1.0, committed Oct 21, 2026
- First version recorded
- Sep 10, 2026
- Size
- 15,185 bytes
- Repository stars
- 23
- License
- MIT
Orchestrate delivery of a three-file specification bundle whose task list is already written — requirements.md, design.md, tasks.md under the repository's specification index. Use when the work is to execute an existing spec: the architect round-trip is already done and the task graph, acceptance criteria, and closeout task all exist. Not for work with no spec, only a plan, or only a todo — that is `conductor`. Not for a single failing test or a one-line fix — that is `bug-crusher`. Not for…
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
# Spec Conductor ## Why this exists `conductor` buys its quality with an `architect` round-trip on every request. A `product-owner` specification bundle **already contains that output**: requirements with numbered acceptance criteria, a design with its decisions and rejected alternatives, and a task list where every task cites the criteria it satisfies and the files it touches. Sending that bundle to `architect` re-plans work a human has already signed off, and pays for the plan twice. This skill is `conductor` with the planning stage removed and the spec bundle read in its place. Everything that makes conductor work — the orchestration boundary, parallel worker pools, the review ladder, the findings collection, the end-of-run council — is unchanged and is **not restated here**. > **Interim skill.** This exists as a standalone skill only because the canonical Kyber-Squad > tree is being changed on another branch. Once that lands, this file becomes the `spec-flow` > reference inside the `conductor` skill and this skill is deleted. See > the final section, *Folding this into conductor* — it is written to make that a move, not a …
Read the whole file at its exact version.
How to install
mdr add dpalfery/kyber-weave/spec-conductor@sha256:2e6b88d8b2c11b5bThe line at the top of this page pins the label v0.1.0, 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_4ze7eho3yi6jpvkp)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Sep 10, 2026 and Oct 21, 2026, about one every 20 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v0.1.0 latest | 2026-10-21 | 26ee555 | 15,185 B | A | view · diff |
| v0.1.0 | 2026-10-19 | 7555554 | 15,145 B | A | view · diff |
| v0.1.0 | 2026-09-10 | 3ffad26 | 14,949 B | A | view |
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 (15185 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
dpalfery/kyber-weave · 23 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_4ze7eho3yi6jpvkp GET https://markdownregistry.com/api/v1/resolve?ref=dpalfery/kyber-weave/spec-conductor GET https://markdownregistry.com/api/v1/blob/2e6b88d8b2c11b5b34c59c28b48571ac2a503e4cd2ee65e38b8186b2db671fc8
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.