メニュー
Analyzes user problems to recommend existing skills from the repository or design new ones based on available resources. Use when the user wants to solve a problem but doesn't know which skill to use, or when proposing a new skill.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | skill-strategist |
| description | Analyzes user problems to recommend existing skills from the repository or design new ones based on available resources. Use when the user wants to solve a problem but doesn't know which skill to use, or when proposing a new skill. |
Your role is to be the "Librarian" and "Architect" of the Antigravity skill ecosystem. You connect user problems to available tools, avoiding redundant work and ensuring high-leverage skill creation.
wsboson-agents or superpowers to see what capabilities are valid..agent/skills/ (Master source), which are mirrored to .cursor/skills and .claude/skills for cross-IDE compatibility.superpowers/skills/ (High-quality, ready to copy)wsboson-agents/plugins/ (Vast library of patterns and templates)Goal: Understand the real problem, not just the requested solution.
Goal: Find if we already have the tool.
.agent/skills?superpowers/skills. (e.g., writing-plans, troubleshooting).wsboson-agents/plugins. (This is a goldmine for specific domains like kubernetes-operations or database-migrations).Goal: Engage the user to select the best path. Do not immediately build. Discuss first.
Scenario A: Exact Match Found
[Name] in [Location]. It handles exactly what you need. Shall we use/install it?"Scenario B: Strong Foundation Found
wsboson-agents/plugins/[Category] contains 80% of what we need. I recommend we create a new skill [New Name] based on those patterns. Thoughts?"Scenario C: No Match (Greenfield)
If a new skill is required, create a brief proposal artifact before coding:
# Skill Proposal: [Name]
**Goal**: [One sentence objective]
**Source Material**: [List files/folders in wsboson-agents/superpowers to use as reference]
**Why**: [Brief justification for why existing skills aren't enough]
list_dir on the resource directories if you haven't recently.superpowers over inventing from scratch.Hands off completed work to QA by merging the PR into the integration branch, posting a testing guide on the Fizzy card, moving it to the QA column, assigning Elvis, and syncing qa-mirror. Auto-detects per-repo conventions (integration branch, qa-mirror presence, Supabase migrations). Use after a PR is approved (or pushed direct) and ready for QA testing.
Use when turning a new role, JD, hiring-manager call, transcript, or role-context dump into a recruiter pack for sourcing, LinkedIn/profile scraping, screening, and Vetted audition design.
Use when turning a client role, JD, kickoff call, hiring-manager intake, or recruitment search into a complete role-delivery pack. Applies to VFA/VettedAI/partner hiring work, including role calibration, internal role briefs, candidate-facing JDs, outreach emails, work-sample auditions, scoring rubrics, shortlist workflows, and live working docs.
Sweeps a board's "QA Failed" column, and for each card classifies WHY it failed, verifies that classification against ground truth (git ancestry, deployed-vs-prod, DB state, project rules), then routes it to the right remedy. Most QA-Failed cards are NOT "the code is wrong, re-review it" — they're stale checkouts, environment drift, deploy gaps, or rule-misreads. Use when a batch of cards is stuck in QA Failed and you want to clear them efficiently as the senior engineer.
Optimized for Human+AI Agent workflows. Converts high-level product intent into technical tickets that include file anchors, logic constraints, and verification protocols for coding agents.
Cross-repo engineering productivity analysis with bounty estimation. Use when the user wants contributor stats, PR velocity, workload distribution, team performance snapshots, or bounty payout projections.