Spec Tree skills for spec-driven development
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/spec-tree| Skill | Description |
|---|---|
aligning |
reviewing, auditing, or checking spec file conformance |
applying |
ALWAYS invoke this skill before implementing any spec-tree work item |
auditing-product-decisions |
auditing PDRs or after writing a PDR |
auditing-tests |
auditing test evidence quality, after writing tests for a spec node, or before closing an outcome |
authoring |
adding, defining, or creating specs, decisions, or nodes |
bootstrapping |
setting up a new spec tree or when /authoring detects an empty spx/ directory |
committing-changes |
committing changes or when user says "commit" |
contextualizing |
asking about status, progress, or what exists in the spec tree |
decomposing |
breaking down, splitting, scoping, or structuring spec tree nodes |
refactoring |
moving nodes, re-scoping content, or extracting shared enablers |
testing |
ALWAYS invoke this skill before writing tests or when learning the testing approach |
understanding |
ALWAYS invoke this skill before any spec-tree work to load methodology |
MIT