slicing
slicing
Goal
Turn a chosen approach or clear build target into small, ordered, demo-able slices.
This is typically run after shaping, but shaping output is not required. A
valid slice lets someone see, do, or verify something after it ships.
Required Behavior
More from jssee/agents
shaping
Use when working through a fuzzy idea before implementation. Always asks clarification questions first, then produces a requirements table, one or more viable shapes, a fit-check matrix, and a recommendation. Trigger on "not sure which approach", "should we build X or Y", "what's the scope", "tradeoffs", "before we start", or any request where multiple directions are possible.
10commit
Use when committing local changes while preserving clean, reviewable git history.
9simplify
Use when code has been recently written or modified and needs refinement for clarity, consistency, and maintainability before committing
3reducing-entropy
Use when evaluating designs, reviewing code, or refactoring - measures success by total code in the final codebase, not effort to get there. Bias toward deletion.
3write-skill
Create or revise SKILL.md instruction files that agents can follow reliably under context pressure.
3diagnose
Use when a bug, failure, exception, flake, or performance regression needs disciplined root-cause work. Triggers on "diagnose this", "debug this", "why is this broken/slow/throwing/failing", or any report of incorrect runtime behavior.
2