| name | conductor-distill |
| description | Distill methodology from superpowers and BMAD-METHOD docs into the active conductor track's spec.md / plan.md / review.md as intent-layer overlays. Use when user asks to "distill superpowers into conductor", "把 superpowers/bmad 提炼到 conductor", "import method docs to track", "seed conductor with brainstorming/TDD/verification gates", or "feed BMAD PRD/architecture/story/QA principles into the track". Writes only inside marker blocks so it never competes with code-derived facts and re-runs cleanly. DO NOT use for general superpowers invocation, code refactors, or to summarize this codebase. |
| argument-hint | [--track <slug>] [--source superpowers|bmad|both] [--target spec|plan|review|all] [--dry-run] [--refresh] |
| disable-model-invocation | false |
| user-invocable | true |
| allowed-tools | ["read","grep","glob","edit","question"] |
| model | glm-5.2 |
Conductor Distill
Pull intent-layer content from external methodology docs (Anthropic superpowers, BMAD-METHOD) into the active conductor track artifacts. The skill seeds `spec.md`, `plan.md`, and `review.md` with phase gates, principles, and checklists drawn from those upstream sources, while staying out of the fact layer the code itself owns.
<Use_When>
- User asks to distill / 提炼 / import superpowers into a conductor track
- User asks to fold BMAD agent prompts (analyst, PM, architect, dev, QA) into a track
- A new conductor track was created and lacks methodology scaffolding
- An existing track is drifting from the agreed gates and needs re-seeding
</Use_When>
<Do_Not_Use_When>
- No conductor track exists yet — run
conductor setup and conductor track <title> first
- User wants to actually invoke superpowers / write code — go to those skills directly
- User wants to summarize the local codebase or extract facts from source — that is the fact layer; this skill stays out of it
- The conductor artifacts already contain the same blocks and the user did not ask for
--refresh
</Do_Not_Use_When>
<Core_Invariant>
Conductor's intent layer is document-driven and does not compete with code for the fact layer.
This means:
- Distilled blocks contain methodology (principles, gates, checklists, prompts, role expectations).
- Distilled blocks must NOT contain claims about the local code: file names, line numbers, function bodies, test counts, config values, or any observed runtime state.
- If a fact about the code belongs anywhere, it goes in the human-authored sections of
spec.md / plan.md, not inside distilled blocks.
- Distilled blocks are clearly fenced with markers so reviewers can tell methodology from project-specific content at a glance.
If a distillation candidate would only make sense by referencing this repo's code, drop it. The intent layer is the wrong place for it.
</Core_Invariant>
<Distillation_Block_Format>
Every distilled section is wrapped in HTML-style markers so it is idempotent and machine-replaceable:
<!-- conductor:distilled BEGIN source=<source-id> target=<artifact> layer=intent version=YYYY-MM-DD -->
> Source: < >. This block is intent-layer guidance distilled from upstream methodology and contains no claims about the local code.
<!-- conductor:distilled END source= -->
Sources (read-only, scanned at runtime):
- `bundled/upstream/superpowers/skills//SKILL.md` — primary superpowers source in this repo.
- `.upstream/superpowers/skills//SKILL.md` — fallback if the bundled copy is missing.
- BMAD-METHOD: not vendored in this repo. Either (a) read a user-supplied local clone path, or (b) fetch via Context7 (`mcp__plugin_context7_context7__query-docs` with library `bmad-code-org/bmad-method`). Prefer (a) when available.
1. **Resolve track.** Locate active track from `conductor-state.json`. Verify `tracks//metadata.json` exists. If not, stop with a clear "no active track" message.
User: "distill superpowers into the active conductor track, dry run first"
Action: resolve active track → plan blocks for spec/plan/review from the superpowers mapping → print preview → ask for approval before applying.
User: "把 BMAD 的 PRD 和 architect 的部分塞进 spec.md，plan.md 不要动"
Action: source=bmad, target=spec, write `bmad/agent-pm + bmad/template-prd` and `bmad/agent-architect + bmad/template-architecture` blocks into `spec.md` only.
User: "refresh distilled blocks on payment-webhook-retry"
Action: --track payment-webhook-retry --refresh, replace existing blocks in place by `source=` id, leave non-block content untouched.
User: "use superpowers TDD now to fix this bug"
Why bad: the user wants to actually do TDD on the codebase. Route to the TDD skill, not this distiller.
User: "summarize what our auth code does into spec.md"
Why bad: that is fact-layer content. This skill writes methodology only. Decline and suggest a code-reading agent.
