strategist

Structure technology decisions with risk assessment and trade-off analysis.

12|4|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/TurnaboutHero/oh-my-antigravity --skill strategist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: strategist
Source: https://github.com/TurnaboutHero/oh-my-antigravity/tree/main/skills/strategist
Command: npx skills add https://github.com/TurnaboutHero/oh-my-antigravity --skill strategist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Strategist helps teams make structured technology decisions.

Core Features & Use Cases

  • Decision frameworks for technology selection and architectural planning.
  • Risk assessment, trade-off analysis, and clear recommendations.
  • Use Case: When evaluating frontend frameworks for a SaaS dashboard, Strategist compares options, documents trade-offs, and delivers a recommended approach.

Quick Start

Ask Strategist to draft a technology decision brief for a SaaS dashboard, including options, pros/cons, and a recommended path.

Frequently Asked Questions about strategist

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make structured technology decisions for my project?

Structured technology decisions use decision frameworks to evaluate options systematically. Apply risk assessment and trade-off analysis to compare candidates, document reasoning, and deliver a clear recommendation backed by evidence rather than intuition alone.

What should I consider when selecting a frontend framework?

Framework selection requires comparing options across multiple dimensions: performance, ecosystem maturity, team familiarity, maintenance burden, and alignment with your product roadmap. Document trade-offs explicitly—speed-to-market versus long-term scalability—and assess risks for each option before committing.

How do I evaluate architecture trade-offs?

Architecture trade-off analysis documents what each approach gains and sacrifices: cost, performance, complexity, and operational overhead. Use a decision framework to weight these factors against your constraints and strategic goals, then recommend the path that best balances them.

When should I conduct a formal technology decision review?

Conduct a technology decision review before major commitments: new framework adoption, infrastructure migration, or significant architectural changes. Formal review prevents costly mistakes by forcing explicit risk assessment and documented reasoning across the team.

What's the difference between evaluating options and making a recommendation?

Evaluation compares candidates objectively; recommendation selects the best fit for your specific constraints and goals. A decision framework ties them together: evaluation surfaces trade-offs, recommendation weighs them against your priorities and delivers a justified path forward.