Deprecated Outcome Engineering skills (superseded by spec-tree)
This repo is auto-generated from outcomeeng/claude. For the Claude Code plugin marketplace, use
claude plugin marketplace add outcomeeng/claude.
npx skills add outcomeeng/legacy| Skill | Description |
|---|---|
decomposing-capability-to-features |
breaking down a capability into features |
decomposing-feature-to-stories |
breaking down a feature into stories |
decomposing-prd-to-capabilities |
breaking down a PRD into capabilities |
managing-spx |
creating or organizing specs, capabilities, features, stories, or ADRs |
migrating-spec-to-spx |
migrating specs to spx, reviewing migrations, or debugging migration issues |
understanding-durable-map |
agents think in tasks or backlogs, want to "close" items, or ask where "done" work goes |
understanding-outcome-decomposition |
ALWAYS invoke this skill before using any decomposition skill or when understanding outcome levels |
understanding-spx |
ALWAYS invoke this skill before implementing any work item to load complete context |
writing-prd |
writing PRDs or product requirements |
managing-specs |
creating or organizing specs, capabilities, features, stories, or ADRs |
understanding-specs |
ALWAYS invoke this skill before implementing any work item to load complete context |
committing-changes |
committing changes or when user says "commit" |
reviewing-tests |
Foundational test review methodology |
testing |
ALWAYS invoke this skill before writing tests or when learning the testing approach |
MIT