From loom
Maintain sequencing and rollout strategy. Use when work needs multiple tickets, dependency order, tranches, or execution waves.
npx claudepluginhub z3z1ma/agent-loom --plugin loomThis skill uses the workspace's default tool permissions.
Plans own execution strategy.
Drafts, classifies, and optionally creates tickets from an initiative plan. Use when the user provides a plan and wants ticket drafts, wants help shaping a plan into tickets, wants sprint-placement guidance, or wants tickets created in an issue tracker after the plan is approved.
Creates phased implementation plans with risks, dependencies, validation checkpoints, and rollback notes. Useful for non-trivial tasks involving multiple files, subsystems, strategies, or migrations.
Share bugs, ideas, or general feedback.
Plans own execution strategy.
They explain how the work should be sequenced without trying to replace ticket truth.
Create new plan records as .loom/plans/<YYYYMMDD>-<slug>.md.
The canonical ID remains plan:<slug> without the date prefix. Use the record
creation date for the filename prefix so plans support temporal discovery and
future retention or cleanup decisions.
Plan milestones are execution-sequencing checkpoints.
They are not constitutional roadmap direction, initiative outcome metrics, or ticket progress state. If a plan starts recording what happened today, move that truth into the ticket journal or evidence.
A strong plan answers:
Read immediately for normal plan creation or review:
references/plan-shape.md when creating or reviewing a plan's structure.Then read conditionally:
references/slicing.md when decomposing a plan into ticket-sized work.skills/loom-workspace/references/problem-shaping.md when the request is
still too fuzzy to become a plan.templates/plan.md only when creating or substantially reshaping a plan
record.