Paretofilm

Adapt an existing project to the Superpowers + GStack workflow. Analyzes the project, identifies gaps, updates CLAUDE.md routing without losing existing content, and sets up required structure.

Generate a tailored CLAUDE.md with routing rules for the Superpowers + GStack workflow. Asks about project type, evaluates relevant skills from both frameworks, and produces a project-specific routing plan.

After any PRD, spec, plan, or code change: verify artifact-specific pitfalls don't apply before declaring done. For ship-worthy changes, auto-chains Codex + a third model house + adversarial synthesis.

Auto-advance a multi-phase plan: dispatch a subagent per phase, chain /review + /pitfall-verification at each boundary, stop on actionable findings. Use for "autoimplement", "run this plan end-to-end", "auto-advance phases".

Pure dispatcher: picks the right E2E executor for a Swift test request from context (platform × intent × verification kind) and hands off. Routes to the scaffold/MCP-sim/QA/design-review skills.

Generate beautiful, pedagogical HTML companions for superpowers-gstack MD artifacts (design docs, handoffs, plans). Auto-opens via --open; generates per-directory dashboards. Triggered manually or via PostToolUse hook.

One-shot XCUITest scaffolding for iOS SwiftUI apps: audits the Scene tree, generates ranked TIER-1/2/3 stubs, suggests accessibility identifiers, emits an xcresult runner. Manual only — modifies project files.

After a PRD/spec/plan for an iOS app, before implementation: validate the artifact against Apple HIG (iOS) via WebFetch citations. Asks "is this iOS-native?" — complements pitfall-verification and quality-review.

Use before running git reset, git add -A/./-a, editing .gitignore when it's not excluding expected paths, or cleaning up committed files. Prevents four common operational failure modes that cascade into long recovery sessions: reset without state check, catchall staging of build artifacts, gitignore pattern trial-and-error, and per-file iteration when a single bulk command suffices.

Use when an E2E test or integration test reveals an architecture problem — a bug that can't be fixed by changing a single function, but requires restructuring code, changing interfaces, or modifying contracts between modules.