Skill

loom-plans

Maintain sequencing and rollout strategy. Use when work needs multiple tickets, dependency order, tranches, or execution waves.

npx claudepluginhub z3z1ma/agent-loom --plugin loom

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Plans own execution strategy.

Supporting Assets

references/plan-shape.mdreferences/slicing.mdtemplates/plan.md

SKILL.md

Similar Skills

plan

Creates structured master plans (<80 lines) and phase files (<150 lines each) from requirements for enterprise-scale project management. Ideal for non-trivial tasks needing phased execution.

7 files

rune

ticket-planning

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.

3 files

rails-agent-skills

plan

Creates phased implementation plans with risks, dependencies, validation checkpoints, and rollback notes. Useful for non-trivial tasks involving multiple files, subsystems, strategies, or migrations.

oh-my-agent

Stats

Stars11

Forks1

Last CommitMay 3, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

loom-plans

Plans own execution strategy.

They explain how the work should be sequenced without trying to replace ticket truth.

What This Skill Owns

rollout strategy
decomposition
sequencing
milestones at the execution-strategy layer
explicit route from initiative/spec to ticket work

Naming

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.

Milestone Boundary

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.

Use This Skill When

multiple tickets need one sequencing owner
rollout order matters
dependencies need to be made visible
the project needs an execution strategy that should outlive one ticket

Do Not Use This Skill When

the work is already one bounded ticket
the layer should really be initiative or spec
you are tempted to use the plan as a progress log

Good Plan Questions

A strong plan answers:

what the overall route is
why the sequence is ordered this way
what milestones exist
what risks and dependencies shape the sequence
which tickets should exist beneath it

Done Means

a future agent can see the intended route without reading transcript history
the plan sequences the work without swallowing live execution state

Read In This Order

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.