From loom
Maintain strategic outcome framing. Use when work spans tickets, needs success metrics, delegated autonomy, or a long-lived objective owner.
npx claudepluginhub z3z1ma/agent-loom --plugin loomThis skill uses the workspace's default tool permissions.
Initiatives own strategic outcomes.
Provides template for SKILL.md files on cross-functional initiatives, with frontmatter, charter sections, and auto-invoke guidance. Useful for creating strategic overview skills.
Coordinates multi-project initiative planning across services and repositories. Collects context, defines boundaries, analyzes dependencies, and spawns sub-agents for detailed plans.
Maintain sequencing and rollout strategy. Use when work needs multiple tickets, dependency order, tranches, or execution waves.
Share bugs, ideas, or general feedback.
Initiatives own strategic outcomes.
They are the place where the project says, "this cross-cutting result matters enough to deserve its own durable owner."
OBJ-* objective criteria under success metricsCreate new initiative records as .loom/initiatives/<YYYYMMDD>-<slug>.md.
The canonical ID remains initiative:<slug> without the date prefix. Use the
record creation date for the filename prefix so initiatives support temporal
discovery and future retention or cleanup decisions.
Initiative milestones are outcome checkpoints for a strategic result.
They are not constitutional roadmap commitments, plan sequencing details, or ticket progress logs. Use them to show whether the broader outcome is advancing, then let plans own execution order and tickets own live state.
A strong initiative answers:
OBJ-* criteria downstream work may citeRead immediately when the strategic outcome needs an initiative owner:
references/initiative-shape.md when deciding what belongs in the
initiative and how success should be framed.templates/initiative.md only when creating or substantially reshaping an
initiative record.