Omniskills

Use when writing or reviewing GetSuperpower workflow skill files, entry skills, local role skills, step instructions, approval gates, handoffs, or Superpowers/Matt Pocock dependency choices.

Startup-team CEO role for company direction, tradeoffs, and strategic decisions.

Startup-team CTO role for architecture, technical risk, and engineering strategy.

Startup-team engineering manager role for delivery sequencing and quality gates.

Startup-team founding engineer role for implementation, tests, debugging, review, and verification.

Startup-team product manager role for discovery, PRDs, and issue slicing.

Startup-team QA lead role for acceptance checks, regression risk, and release verification.

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

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 making one playful Haaland, JTS, tap-in, striker, or football-finisher meme caption with an original profile icon.

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.

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

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 creating or editing a GetSuperpower workflow bundle, bundle skill, entry skill, orchestrator skill, skill tree, or workflow that composes multiple agent skills into one callable skill.

Use when an agent is about to create, edit, move, or delete files and must preserve decision snapshots, action rationale, file-change intent, rollback context, or a git-like audit trail for every file mutation.

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 an OpenSpec proposal, tasks.md handoff, or archive checkpoint must stay aligned with a Superpowers implementation workflow.

Use the repository command wrapper for shell commands.

Review release changes for rollout, rollback, observability, and user-impact risks.