omni-skills

Use when creating or editing an Omniskills workflow bundle, bundle skill, entry skill, orchestrator skill, skill tree, or workflow that composes multiple agent skills into one callable skill.

Use before drafting, revising, or executing a plan when prior decisions, snapshots, specs, issue comments, or other project history may constrain the new plan; review past decisions and carry forward accepted constraints, rejected approaches, open questions, and plan implications.

Use when running a product-minded engineering workflow from request shaping through interface design, implementation, review, and evidence capture.

Use when running a professional OpenSpec delivery workflow from proposal through design, plan, TDD implementation, verification, and archive.

Use when demonstrating recursive Omniskills workflow dependencies.

Use when coordinating a startup goal across CEO, CTO, product manager, engineering manager, founding engineer, and QA lead role subagents.

Use when shaping a product-development request that should be grilled before Superpowers design and planning.

Use when leading web interface direction, interaction craft, responsive behavior, and animation review.

Use when acting as a startup CEO for direction, tradeoffs, strategy, fundraising, positioning, or company-level decisions.

Use when acting as a startup CTO for architecture, technical risk, platform direction, codebase boundaries, or engineering strategy.

Use when acting as a startup engineering manager for delivery planning, execution risk, quality gates, and team process.

Use when acting as a startup founding engineer for implementation, tests, debugging, review, and verification.

Use when acting as a startup product manager for discovery, PRDs, issue slicing, roadmap tradeoffs, or customer-value sequencing.

Use when acting as a startup QA lead for acceptance checks, release risk, regression focus, and verification evidence.