loom-planslisted

# loom-plans Plans own multi-ticket strategy: decomposition, sequencing, dependencies, milestones, shared constraints, validation posture, evidence expectations, loopback conditions, and plan-level current state. Plans do not own intended behavior, investigation findings, durable policy, live execution detail, ticket closure, or raw evidence. ## Use This Skill When Use it when: - work exceeds one bounded ticket - sequencing, dependencies, rollout, or coordination matter - child tickets need one shared strategy and validation posture - a spec, research conclusion, migration, refactor, or architecture change needs ticket-ready execution units - an existing plan needs update, review, completion, blocking, or cancellation Use one ticket when one bounded ticket is enough. Route unclear behavior to specs, tradeoffs to research, and durable policy or precedent to constitution before saving a plan. ## Inspect Plans live under `.loom/plans/`. ```bash find .loom/plans -name '*.md' -print 2>/dev/null | sort grep -R '^ID: plan:' .loom/plans 2>/dev/null || true grep -R '^Status:' .loom/plans 2>/dev/null || true grep -R '^Risk:' .loom/plans 2>/dev/null || true ``` When updating or completing a plan, read the whole plan and inspect child tickets named in `## Execution Units`. ## Record Shape Use date-prefixed IDs and matching filenames: ```text ID: plan:YYYYMMDD-<slug> .loom/plans/YYYYMMDD-<slug>.md ``` Required labels: ```text ID: plan:YYYYMMDD-<slug> Type: Plan Status: open