Plan & spec
10,724 rows, by stacks then stars
2,010 of these skill files have been read, by 1,360 distinct authors, and what they tell an agent counted. What Plan & spec authors agree on, and what they forbid
VRIL-LABS/skill-jam/skills/ai-ml/financial-services-plugins-main/financial-services-plugins-main/wealth-management/skills/financial-plan Skill
no license2★ repoWelcome to the skill-jam ☄️🏀
The same file is in 1 other repository
VRIL-LABS/skill-jam/skills/ai-ml/financial-services-plugins-main/financial-services-plugins-main/wealth-management/skills/investment-proposal Skill
no license2★ repoWelcome to the skill-jam ☄️🏀
The same file is in 1 other repository
VRIL-LABS/skill-jam/skills/ai-ml/knowledge-work-plugins-main/knowledge-work-plugins-main/bio-research/skills/scientific-problem-selection Skill
no license2★ repoThis skill should be used when scientists need help with research problem selection, project ideation, troubleshooting stuck projects, or strategic scientific decisions. Use this skill when users ask to pitch a new research idea, work through a project problem, evaluate project risks, plan research strategy, navigate decision trees, or get help choosing what scientific problem to work on. Typical requests include "I have an idea for a project", "I'm stuck on my research", "help me evaluate this project", "what should I work on", or "I need strategic advice about my research".
The same file is in 7 other repositories
VRIL-LABS/skill-jam/skills/ai-ml/knowledge-work-plugins-main/knowledge-work-plugins-main/engineering/skills/testing-strategy Skill
no license2★ repoDesign test strategies and test plans. Trigger with "how should we test", "test strategy for", "write tests for", "test plan", "what tests do we need", or when the user needs help with testing approaches, coverage, or test architecture.
The same file is in 5 other repositories
VRIL-LABS/skill-jam/skills/ai-ml/knowledge-work-plugins-main/knowledge-work-plugins-main/enterprise-search/skills/search-strategy Skill
no license2★ repoQuery decomposition and multi-source search orchestration. Breaks natural language questions into targeted searches per source, translates queries into source-specific syntax, ranks results by relevance, and handles ambiguity and fallback strategies.
The same file is in 1 other repository
VRIL-LABS/skill-jam/skills/ai-ml/knowledge-work-plugins-main/knowledge-work-plugins-main/human-resources/skills/org-planning Skill
no license2★ repoHeadcount planning, org design, and team structure optimization. Trigger with "org planning", "headcount plan", "team structure", "reorg", "who should we hire next", or when the user is thinking about team size, reporting structure, or organizational design.
The same file is in 2 other repositories
VRIL-LABS/skill-jam/skills/ai-ml/knowledge-work-plugins-main/knowledge-work-plugins-main/legal/skills/brief Skill
no license2★ repoGenerate contextual briefings for legal work — daily summary, topic research, or incident response. Use when starting your day and need a scan of legal-relevant items across email, calendar, and contracts, when researching a specific legal question across internal sources, or when a developing situation (data breach, litigation threat, regulatory inquiry) needs rapid context.
The same file is in 1 other repository
VRIL-LABS/skill-jam/skills/ai-ml/knowledge-work-plugins-main/knowledge-work-plugins-main/marketing/skills/campaign-plan Skill
no license2★ repoGenerate a full campaign brief with objectives, audience, messaging, channel strategy, content calendar, and success metrics. Use when planning a product launch, lead-gen push, or awareness campaign, when you need a week-by-week content calendar with dependencies, or when translating a marketing goal into a structured, executable plan.
The same file is in 2 other repositories
VRIL-LABS/skill-jam/skills/ai-ml/knowledge-work-plugins-main/knowledge-work-plugins-main/marketing/skills/competitive-brief Skill
no license2★ repoResearch competitors and generate a positioning and messaging comparison with content gaps, opportunities, and threats. Use when building sales battlecards, when finding positioning gaps and messaging angles competitors haven't claimed, or when a competitor makes a move and you need to assess the impact.
The same file is in 2 other repositories
VRIL-LABS/skill-jam/skills/ai-ml/knowledge-work-plugins-main/knowledge-work-plugins-main/operations/skills/capacity-plan Skill
no license2★ repoPlan resource capacity — workload analysis and utilization forecasting. Use when heading into quarterly planning, the team feels overallocated and you need the numbers, deciding whether to hire or deprioritize, or stress-testing whether upcoming projects fit the people you have.
The same file is in 1 other repository
VRIL-LABS/skill-jam/skills/ai-ml/knowledge-work-plugins-main/knowledge-work-plugins-main/operations/skills/change-request Skill
no license2★ repoCreate a change management request with impact analysis and rollback plan. Use when proposing a system or process change that needs approval, preparing a change record for CAB review, documenting risk and rollback steps before a deployment, or planning stakeholder communications for a rollout.
The same file is in 1 other repository
VRIL-LABS/skill-jam/skills/ai-ml/knowledge-work-plugins-main/knowledge-work-plugins-main/partner-built/common-room/skills/weekly-prep-brief Skill
no license2★ repoGenerate a comprehensive weekly briefing for all external calls in the next 7 days. Triggers on 'weekly prep brief', 'prepare my week', 'what calls do I have this week', 'Monday prep', or any weekly planning request.
The same file is in 2 other repositories
VRIL-LABS/skill-jam/skills/ai-ml/knowledge-work-plugins-main/knowledge-work-plugins-main/product-management/skills/competitive-brief Skill
no license2★ repoCreate a competitive analysis brief for one or more competitors or a feature area. Use when informing product strategy or feature prioritization, building sales battle cards, prepping board or investor materials, or deciding where to differentiate vs. achieve parity.
The same file is in 1 other repository
VRIL-LABS/skill-jam/skills/ai-ml/knowledge-work-plugins-main/knowledge-work-plugins-main/product-management/skills/roadmap-update Skill
no license2★ repoUpdate, create, or reprioritize your product roadmap. Use when adding a new initiative and deciding what moves to make room, shifting priorities after new information comes in, moving timelines due to a dependency slip, or building a Now/Next/Later view from scratch.
The same file is in 1 other repository
VRIL-LABS/skill-jam/skills/ai-ml/knowledge-work-plugins-main/knowledge-work-plugins-main/product-management/skills/sprint-planning Skill
no license2★ repoPlan a sprint — scope work, estimate capacity, set goals, and draft a sprint plan. Use when kicking off a new sprint, sizing a backlog against team availability (accounting for PTO and meetings), deciding what's P0 vs. stretch, or handling carryover from the last sprint.
The same file is in 1 other repository
VRIL-LABS/skill-jam/skills/ai-ml/knowledge-work-plugins-main/knowledge-work-plugins-main/product-management/skills/stakeholder-update Skill
no license2★ repoGenerate a stakeholder update tailored to audience and cadence. Use when writing a weekly or monthly status for leadership, announcing a launch, escalating a risk or blocker, or translating the same progress into exec-brief, engineering-detail, or customer-facing versions.
The same file is in 1 other repository
VRIL-LABS/skill-jam/skills/ai-ml/knowledge-work-plugins-main/knowledge-work-plugins-main/product-management/skills/write-spec Skill
no license2★ repoWrite a feature spec or PRD from a problem statement or feature idea. Use when turning a vague idea or user request into a structured document, scoping a feature with goals and non-goals, defining success metrics and acceptance criteria, or breaking a big ask into a phased spec.
The same file is in 2 other repositories
VRIL-LABS/skill-jam/skills/ai-ml/sap-skills-main/sap-skills-main/plugins/sap-sac-planning/skills/sap-sac-planning Skill
no license2★ repoThis skill should be used when developing SAP Analytics Cloud (SAC) planning applications, including building planning-enabled stories, analytics designer applications with planning functionality, data actions, multi actions, version management, and planning workflows. Use when creating planning models, implementing data entry forms, configuring spreading/distribution/allocation, setting up data locking, building calendar-based planning processes with approval workflows, writing JavaScript scripts for planning automation, using the getPlanning() API, PlanningModel API, or DataSource API for planning scenarios, troubleshooting planning performance issues, integrating predictive forecasting into planning workflows, implementing Seamless Planning with SAP Datasphere, configuring BPC live connections for BW on HANA integration, building value driver trees for what-if analysis, or debugging data actions with tracing.
VRIL-LABS/skill-jam/skills/ai-ml/skills-main/skills-main/guides/writing/seo-content-brief Skill
no license2★ repoSEO content brief creation with keyword research, search intent analysis, and content structure. Covers SERP analysis, heading hierarchy, word count targets, and internal linking strategy. Use for: content briefs, SEO writing, blog strategy, content planning, keyword targeting. Triggers: seo content brief, content brief, seo brief, keyword research, search intent, content strategy, blog brief, seo writing, content planning, keyword targeting, serp analysis, content outline, seo article, blog seo
VRIL-LABS/skill-jam/skills/core-collections/new-skills-2026/devops-infrastructure/cloud-migration-planner Skill
no license2★ repoPlan and execute cloud migrations — assessment, strategy, and execution roadmap. Use when moving to cloud, planning migration waves, or evaluating migration approaches.
VRIL-LABS/skill-jam/skills/core-collections/new-skills-2026/devops-infrastructure/disaster-recovery-planner Skill
no license2★ repoDesign disaster recovery strategies — RTO/RPO planning, backup strategies, and failover procedures. Use when planning business continuity, implementing DR, or testing recovery procedures.
VRIL-LABS/skill-jam/skills/core-collections/new-skills-2026/performance-optimization/cache-strategy-advisor Skill
no license2★ repoDesign caching strategies — cache policies, invalidation, and TTL. Use when implementing caching, improving performance, or reducing database load.
VRIL-LABS/skill-jam/skills/core-collections/spellbook-master/spellbook-master/skills/shape Skill
no license2★ repoShape a raw idea into something buildable. Product + technical exploration. Spec, design, critique, plan. Output is a context packet. Use when: "shape this", "write a spec", "design this feature", "plan this", "spec out", "context packet", "technical design". Trigger: /shape, /spec, /plan, /cp.
VRIL-LABS/skill-jam/skills/travel-planner Skill
no license2★ repoBuilds complete travel itineraries from flights, hotels, and activities; accounts for budget, preferences, and transit times. Invoke when asked to plan a trip, build a travel itinerary, find flights and hotels, suggest activities for a destination, or organize a vacation.
ajaygodbole7/rest-api-skill/skills/api-contract-review Skill
no license2★ repoUse when reviewing or auditing an existing OpenAPI 3.1 specification for compliance with Zalando RESTful API Guidelines. Produces a structured checklist report (BLOCKER / WARNING / INFO severity) covering naming, security, HTTP usage, pagination, compatibility, and all other rule categories. Activate for API review, contract audit, or spec compliance checking tasks.
t4sh/dotfiles/agents/skills/paseo-committee Skill
no license2★ repoForm a committee of two high-reasoning agents to step back, do root cause analysis, and produce a plan. Use when stuck, looping, tunnel-visioning, or facing a hard planning problem.
t4sh/dotfiles/agents/skills/request-refactor-plan Skill
no license2★ repoCreate a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.
The same file is in 13 other repositories
t4sh/dotfiles/agents/skills/to-spec Skill
no license2★ repoTurn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
The same file is in 11 other repositories
t4sh/dotfiles/agents/skills/to-tickets Skill
no license2★ repoBreak a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker — edges as text in one file per ticket locally, or native blocking links on a real tracker.
The same file is in 5 other repositories
Sagargupta16/craftsmanship/skills/plan Skill
2★ repoUse when implementing features spanning 3+ files, when requirements are unclear, or when structuring multi-step work. Covers when to plan vs just code, plan structure, interview-then-execute, and prototype-over-spec patterns.
GlamgarOnDiscord/claude-saas-blueprint/.claude/skills/prd Skill
2★ repoWorkflow complet "PRD to Tasks" pour construire un SaaS de A à Z. Brainstorm → PRD → Architecture → Tasks → Exécution automatique.
jacob-balslev/skills/skills/ai-engineering/tool-call-strategy Skill
2★ repoUse when an agent is making too many tool calls, when context is filling from verbose tool outputs, when the same operation could be a script instead of N individual calls, or when designing a tool-use protocol for a new agent or harness. Covers the three costs of every call (token, latency, context pollution), the script-vs-call decision gate, tool-selection decision trees (file-search vs content-search vs targeted-read vs full-read), call batching and parallelization, redundancy avoidance, the poka-yoke principle, subagent delegation for context protection, and cost-benchmark heuristics by task type. Do NOT use for prompt wording (use `prompt-craft`), broader context stack design across the five layers (use `context-engineering`), runtime tool failures or production debugging (use `debugging`), or behaviour-preserving refactor mechanics (use `refactor`).
jacob-balslev/skills/skills/data-engineering/indexing-strategy Skill
2★ repoUse when designing or auditing the maintained index set for a database workload: choosing index structures, matching access patterns, setting composite order, balancing read speed against write/storage cost, and deciding when to add, keep, or drop indexes. Do NOT use for tuning one slow query (use query-optimization), applying production DDL (use database-migration), isolation choices, schema design, or sharding.
jacob-balslev/skills/skills/data-engineering/query-optimization Skill
2★ repoDiagnosing and tuning a specific slow relational-database query from plan evidence: workload impact, exact query context, EXPLAIN / actual execution plans, row-estimate accuracy, access path choice, join order, sort/hash spills, JIT/planning overhead, parameter-sensitive plans, plan regressions, statistics, and rewrite-vs-index-vs-operational response selection. Start from the actual plan and runtime evidence, not from the reflex to add an index; modern engine features such as Query Store, PSP/OPPO, SQL Plan Management, pg_stat_statements, auto_explain, MySQL histograms, Oracle DBMS_XPLAN, and PostgreSQL planner improvements are evidence sources and response tools, not replacements for diagnosis. Do NOT use for designing the durable index portfolio (use indexing-strategy), schema design (use entity-relationship-modeling), distributed partitioning (use sharding-strategy), isolation-level correctness (use transaction-isolation), or whole-system load testing (use performance-testing).
jacob-balslev/skills/skills/data-engineering/sharding-strategy Skill
2★ repoUse when reasoning about horizontal partitioning of data across nodes for storage capacity and write throughput beyond a single node: the three foundational partitioning schemes (range, hash, directory/lookup), the shard-key choice that determines whether the system scales or hotspots, the resharding problem and how consistent hashing addresses it, cross-shard queries and the joins-and-transactions trade-off, the relationship to replication (sharding partitions data; replication copies each shard), and the failure modes (hot shard, skewed distribution, cross-shard transactions, range-end overload). Do NOT use for replicating the same data across nodes (use replication-patterns), the CAP/PACELC frame (use cap-theorem-tradeoffs), single-node performance tuning (use query-optimization), or indexing within a shard (use indexing-strategy).
jacob-balslev/skills/skills/quality-assurance/lint-overlay Skill
2★ repoUse when adding or enforcing lint rules as part of a test or verification plan. Extends testing-strategy with lint-specific guidance: rule selection, gate placement, failure triage, and migration planning when introducing rules to an existing codebase. Do NOT use standalone — load the base testing-strategy skill alongside it — and do NOT use for chasing a specific lint failure in one file (that is debugging).
jacob-balslev/skills/skills/quality-assurance/mutation-testing Skill
2★ repoUse when reasoning about mutation testing as a behavioral signal of test-suite quality: the mutant-operator vocabulary (replace operator, negate condition, flip Boolean, remove statement, alter constant), the mutation-score metric (killed mutants / total non-equivalent mutants), why mutation testing is a stronger signal than code coverage (coverage measures execution; mutation measures whether the tests would catch a defect), the equivalent-mutant problem (mutants that produce no observable behavior change despite syntactic difference), selective and incremental mutation strategies that make the technique practical for large codebases (PIT, Stryker), and the relationship between mutation testing and TDD. Do NOT use for the structural signal of how much code tests reach (use test-coverage-strategy), the construction of test doubles (use test-doubles-design), the strategic question of what to test at which level (use testing-strategy), or generic fault injection at runtime (use chaos-engineering).
jacob-balslev/skills/skills/quality-assurance/seo-strategy Skill
2★ repoSEO implementation strategy for building pages that rank -- covering content strategy, programmatic SEO at scale, marketplace-specific SEO, and AI search optimization.
jacob-balslev/skills/skills/quality-assurance/test-coverage-strategy Skill
2★ repoUse when reasoning about code coverage as a strategic measurement rather than a quality target: structural reach versus behavioral verification (covered vs tested), the coverage-criterion hierarchy (function, line, branch, decision, condition, MC/DC, path) and matching the criterion to where a module's failure modes hide, Marick's floor-vs-ceiling distinction, Goodhart's Law applied to coverage and Goodhart-resistant policy (diagnostic use, diff/patch floors, risk-weighting, behavioral panels), denominator hygiene and cross-tool counter semantics, safety-critical MC/DC (DO-178C Level A required; ISO 26262 ASIL-D highly recommended) as requirements-based evidence, and interpreting coverage from AI-generated tests. Do NOT use for choosing test levels (use testing-strategy), mutation testing as a behavioral signal (use mutation-testing), test-double construction (use test-doubles-design), LLM eval iteration (use eval-driven-development), or specific coverage-tooling configuration (tool docs).
jacob-balslev/skills/skills/quality-assurance/testing-strategy Skill
2★ repoUse when planning tests for a bug fix, feature, or refactor — deciding what deserves a test, at which level, with what evidence. Covers test-scope decisions, test-level selection (unit / integration / contract / e2e), effort-to-risk matching, regression targeting, evidence quality, and failure-case coverage. Do NOT use for chasing a known failure (that is `debugging`), for pure doc writing (that is `documentation`), or for conceptual architecture discussion with no verification target (no dedicated skill — treat as strategy, not testing).
jacob-balslev/skills/skills/reasoning-strategy/ansoff-matrix Skill
2★ repoUse when choosing or reviewing growth strategy options with the Ansoff product-market matrix: market penetration, market development, product development, diversification, existing vs new products, existing vs new markets, strategic distance, risk, assumptions, and sequencing. Covers growth-option framing, quadrant classification, evidence needs, option comparison, and handoff to deeper validation methods. Do NOT use for internal/external factor inventory (use swot-tows), macro-environment scanning (use pestel), industry profit-pressure diagnosis (use porters-five-forces), integrated strategy cascades (use playing-to-win), durable moat classification (use seven-powers), or quantified option valuation (use expected-value).
jacob-balslev/skills/skills/reasoning-strategy/balanced-scorecard Skill
2★ repoUse when building, reviewing, or applying a Balanced Scorecard for strategy execution and performance management: destination statement, strategy map, perspectives, strategic objectives, strategic readiness, measures/KPIs, targets, initiatives, owners, review cadence, cascading, and learning from performance gaps. Covers financial/stewardship, customer/stakeholder, internal process, and learning/growth or organizational-capacity perspectives, with sustainability/ESG embedded or added as a fifth perspective when strategic, and adaptation for business, nonprofit, public-sector, product, and transformation contexts. Do NOT use for upstream strategy formulation alone (use playing-to-win), quarterly goal-setting alone (use okrs), technical service thresholds (use performance-budgets), portfolio allocation (use bcg-matrix), generic internal/external factor inventory (use swot-tows), probability-weighted option valuation (use expected-value), or activity-level value/cost decomposition (use value-chain-analysis).
jacob-balslev/skills/skills/reasoning-strategy/bayesian-reasoning Skill
2★ repoUse when updating beliefs, forecasts, diagnoses, or decision assumptions under uncertainty using Bayesian reasoning: priors/base rates, likelihood, evidence strength, posterior direction, and residual uncertainty. Covers base-rate discipline, likelihood-vs-posterior separation, independent evidence updates, natural-frequency examples, confidence calibration, and when to stop at qualitative probability instead of fake precision. Do NOT use for expected monetary value calculations, strategy-cascade choices (use playing-to-win), industry-structure analysis (use porters-five-forces), or generic task prioritization (use prioritization).
jacob-balslev/skills/skills/reasoning-strategy/blue-ocean-strategy Skill
2★ repoUse when creating, auditing, or pressure-testing a Blue Ocean Strategy: value innovation, strategy canvas, Four Actions Framework, ERRC grid, six paths, buyer utility, noncustomers, and commercial viability. Covers reconstructing market boundaries, breaking the value-cost trade-off, shifting from competitor benchmarking to alternative/noncustomer insight, and turning the result into a new value curve. Do NOT use for industry-structure diagnosis alone (use porters-five-forces), durable moat classification (use seven-powers), or integrated five-choice strategy cascades (use playing-to-win).
jacob-balslev/skills/skills/reasoning-strategy/inversion Skill
2★ repoUse when a goal, plan, design, strategy, metric, or assumption should be examined by reversing it: ask how to guarantee failure, how the opposite could be true, what would have to happen for the desired outcome not to occur, or how an apparent win could backfire. Covers objective reversal, prospective-hindsight framing, failure-path enumeration, obstacle-first planning, consider-the-opposite debiasing, opposite-hypothesis testing, metric inversion, architectural non-goal definition, red-team-style self-review, and prevention design. Do NOT use for decomposing a problem to irreducible premises (use first-principles-thinking), post-failure root-cause analysis (use debugging), recurring failure clustering (use pattern-recognition), claim/source grounding (use epistemic-grounding), full FMEA scoring, full pre-mortem facilitation, or full AI/security red-team programs.
jacob-balslev/skills/skills/reasoning-strategy/kano-model Skill
2★ repoUse when classifying product features, service attributes, customer needs, or roadmap candidates with the Kano model: must-be/basic quality, performance/one-dimensional quality, attractive/delighter quality, indifferent quality, reverse quality, and questionable responses. Covers paired functional/dysfunctional survey design, segment-specific classification, feature-priority implications, category migration over time, and the boundary between Kano analysis and general backlog scoring. Do NOT use for generic RICE/ICE/MoSCoW ranking without customer-response evidence (use prioritization), open-ended research synthesis (use user-research or research-synthesis), or product-market positioning (use positioning).
jacob-balslev/skills/skills/reasoning-strategy/pestel Skill
2★ repoUse when scanning an external macro environment with PESTEL/PESTLE (and its variant family STEEPLE, STEEPLED, PESTLIED, STEEP, DESTEP, LoNGPESTLE): political, economic, social, technological, environmental, and legal forces; evidence quality and recency; geography/jurisdiction and local/national/global level; time horizon; uncertainty; weak signals; impact/probability scoring; factor interactions; bias checks; opportunity/threat implications; assumptions; action conversion; and monitoring triggers. Covers external-environment scanning before strategy choices, market-entry reviews, strategic planning, product/service context, policy-aware planning, and risk/opportunity surfacing. Do NOT use for internal capability diagnosis (use swot-tows or a capability method), industry profit-pressure diagnosis (use porters-five-forces), value-curve redesign (use blue-ocean-strategy), integrated strategy cascades (use playing-to-win), product positioning (use positioning), or quantified option comparison (use expected-value).
jacob-balslev/skills/skills/reasoning-strategy/playing-to-win Skill
2★ repoUse when turning a vague business strategy, product strategy, market-entry decision, or initiative plan into an integrated Playing to Win strategy cascade: winning aspiration, where to play, how to win, must-have capabilities, and management systems. Covers Lafley/Martin choice-making, fit across the five choices, trade-off pressure, reverse tests, capability-system alignment, and the difference between strategy and planning. Do NOT use for competitive-industry structure analysis (use a five-forces skill when available), generic backlog scoring (use prioritization), or broad process-gate design (use methodology).
jacob-balslev/skills/skills/reasoning-strategy/porters-five-forces Skill
2★ repoUse when analyzing an industry's competitive structure and profit pool using Porter's Five Forces: rivalry among existing competitors, threat of new entrants, bargaining power of suppliers, bargaining power of buyers, and threat of substitutes. Covers industry-boundary definition, force-by-force diagnostics, structural drivers, dynamic trends, profitability implications, strategic positioning options, and the distinction between industry attractiveness and firm-specific advantage. Do NOT use for creating an integrated strategy cascade (use playing-to-win), classifying durable moat sources (use Seven Powers when available), backlog scoring (use prioritization), or generic market sizing.
jacob-balslev/skills/skills/reasoning-strategy/principled-negotiation Skill
2★ repoUse when preparing, structuring, or pressure-testing a negotiation with principled negotiation / BATNA: separate people from the problem, focus on interests rather than positions, invent options for mutual gain, use objective criteria, define BATNA / reservation value / ZOPA, and decide whether to accept, improve, or walk away. Do NOT use for generic persuasion copy (use microcopy or writing-humanizer), unilateral conflict diagnosis without a deal table, competitive strategy analysis (use playing-to-win, porters-five-forces, or seven-powers), or broad decision scoring without counterparties (use expected-value or prioritization).
jacob-balslev/skills/skills/reasoning-strategy/scenario-planning Skill
2★ repoScenario planning: a strategic-foresight method for making decisions under deep uncertainty by constructing and stress-testing several plausible future worlds.
jacob-balslev/skills/skills/reasoning-strategy/seven-powers Skill
2★ repoUse when diagnosing whether a business has, can build, or is falsely claiming durable strategic power using Hamilton Helmer's Seven Powers: scale economies, network economies, counter-positioning, switching costs, branding, cornered resource, and process power. Covers Power as benefit plus barrier, persistent differential returns, moat-source classification, Power Progression by company phase, false-positive checks, and strategy implications. Do NOT use for industry-structure analysis alone (use porters-five-forces), integrated strategy-cascade formulation (use playing-to-win), generic prioritization, financial valuation, or surface-level SWOT lists.
jacob-balslev/skills/skills/reasoning-strategy/swot-tows Skill
2★ repoUse when turning internal/external situation analysis into strategic options with SWOT and TOWS: strengths, weaknesses, opportunities, threats, evidence quality, SO/WO/ST/WT option generation, and action hypotheses. Covers separating internal from external factors, avoiding unsupported laundry lists, crossing quadrants into strategy options, and naming what evidence or method should follow. Do NOT use for industry profit-pressure diagnosis (use porters-five-forces), durable moat classification (use seven-powers), value-curve redesign (use blue-ocean-strategy), integrated strategy cascades (use playing-to-win), or quantified option comparison (use expected-value).
jacob-balslev/skills/skills/reasoning-strategy/task-analysis Skill
2★ repoUse when auditing a route, defining a route contract, reviewing onboarding or setup flows, diagnosing why a page feels confusing, or when the user asks about top tasks, time-to-value, branching, dead ends, or task complexity. Provides goal-driven UX analysis that turns vague critique into explicit goal -> task -> subtask decomposition and a primary / secondary / supporting hierarchy contract for the first viewport. Do NOT use for control-pattern choice (use `interaction-patterns`), visual craft (use `visual-design-foundations`), responsive layout (use `layout-composition`), or accessibility-only QA (use `a11y`).
jacob-balslev/skills/skills/reasoning-strategy/three-horizons Skill
2★ repoUse when balancing an innovation, growth, transformation, or venture portfolio across McKinsey's Three Horizons: Horizon 1 current core businesses, Horizon 2 emerging growth businesses, and Horizon 3 future options. Covers concurrent portfolio balance, resource allocation (the 70-20-10 benchmark and its caveats), evidence maturity, governance and metrics by horizon, metered funding, ring-fenced budgets, transitions from option to emerging business to core, the collapsed-time critique that disruption can now arrive on core timelines, and the risk that short-term core demands or incentives starve future growth. Do NOT use for BCG growth-share portfolio allocation (use bcg-matrix), Ansoff product-market growth path selection (use ansoff-matrix), Blue Ocean value-curve redesign (use blue-ocean-strategy), scenario construction and stress-testing across alternative futures (use scenario-planning), OKR goal-setting (use okrs), or quantified probability-weighted valuation (use expected-value).
jacob-balslev/skills/skills/software-engineering-method/prioritization Skill
2★ repoThis skill provides prioritization frameworks for AI engineering: RICE-A (adding AI Ambiguity to RICE) for product features, ICE for research experiments, and MoSCoW for MVP/Release scoping. Use when ranking the backlog, deciding which model research path to follow, or defining the scope of a new feature. Do NOT use for one-off task sequencing (use task skill) or personal time management.
jacob-balslev/skills/skills/software-engineering-method/spec-driven-development Skill
2★ repoUse when starting a non-trivial feature, refactor, or agent implementation that needs a written spec, plan, task breakdown, and verification path before code changes. Covers Spec Kit-style SDD phases, requirements-vs-plan separation, task traceability, review gates, and spec-compliance verification. Do NOT use for one-line edits, README-only fixes, post-implementation code review (use `code-review`), or test-level decisions (use `testing-strategy`).
Competitor marketing strategy analysis
DoomDeity/new-media-core-skills/skills/01-research-insight/R04-competitor-marketing-strategy-analysis/dist/standard/competitor-marketing-strategy-analysis Skill
no license2★ repo拆解竞品传播矩阵、获客触点、私域承接与转化路径。当用户要弄清竞品怎么获客、公域到私域怎么走或转化链路如何时使用。不推测投放占比、转化率或成交数据;渠道贡献仅按证据强弱标注。
JacobStephens2/skills/plan Skill
2★ repoWrite a plan.
makigjuro/cloudstack-ai-plugins/plugins/cloud-infra/skills/infra-plan Skill
2★ repoPlan infrastructure changes — Terraform modules, Helm charts, CI/CD pipelines. Use when the user wants to add or modify cloud infrastructure, Kubernetes resources, or deployment pipelines.