Break intent into required behaviors
tr-decomposecommandsetup L1★6
imix/taproot ↗What it does
Break intent down into behaviors and use cases needed to fulfill it
Best for
Breaking down a user intent into concrete taproot UseCase behaviors and documenting the decomposition
Inputs
- · Intent specification from taproot project
- · Focus area argument (optional)
Outputs
- · Set of required UseCase behaviors documented
- · Decomposition saved to taproot project output directory
- · Updated OVERVIEW.md with current project state
Requires
- · taproot skills (@{project-root}/taproot/agent/skills/decompose.md)
- · node dist/cli.js CLI (not bare taproot command)
Preconditions
- · taproot project initialized
- · decompose.md skill file exists at project-root/taproot/agent/skills/
- · node and dist/cli.js available
Failure modes
- · taproot project not initialized
- · decompose.md skill file missing
- · node dist/cli.js command fails or not found
Trust signals
- · Uses node dist/cli.js instead of bare taproot (enforces CLI consistency)
- · Calls node dist/cli.js overview to update OVERVIEW.md automatically
- · Reads full skill definition from decompose.md before executing
- · Follows taproot command naming conventions (tr-decompose mapped to /taproot:decompose)