Menu

Individual skill

skill-fusion

0upvotes

Fuse two skills from this library into one hybrid brief for a task that sits between them — the meta-skill. Use when a task straddles two skills (a PRD that's also a pitch; a postmortem that must double as a board update) and running them separately would produce two documents where one is needed. Produces the fused operating brief: combined structure, merged quality bar, precedence rules for where the parents disagree, and the fused output itself if input was provided.

plugins/pm-advanced/skills/skill-fusion/SKILL.md

Read pinned source

Source commit f7c90bc09ee05dc25cf257bdb1826f2c2552c2cb

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,540
Repository last updated
Nov 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Skill Fusion

Real tasks ignore taxonomy: the investor update that's half postmortem, the launch plan that's half legal review. Running two skills sequentially produces a stapled document. Fusion produces a *hybrid* — one structure that inherits deliberately from both parents, with explicit rules for their disagreements.

## Required Inputs

- **The two parent skills** — by name if known; otherwise describe the task and identify the two best parents first (say which and why).
- **The task itself** — what's being produced, for whom. The audience decides which parent leads.
- The actual input material, if the fused skill should run immediately after being forged.

## The Fusion Method

1. **Declare the dominant parent** — the audience's primary job determines it (a board reads the postmortem-update as an *update* first). The dominant parent contributes the skeleton; the recessive parent contributes organs.
2. **Merge structures section by section** — for each parent section: keep / merge / drop, with one-line reasons. A fused doc is SHORTER than the parents combined or the fusion failed.
Back to top