Results for “feasibility”

Design prospective clinical studies by selecting and classifying endpoints, estimating sample size and power for two-arm designs, and scoring study plans for feasibility with phase-gate decisions.

Quick feasibility and novelty check — go/no-go decision for this week's build

Validate whether an OSS tool is worth building through staged namespace, existing-solution, and feasibility review

Use this when reviewing database, storage, config, queue, or integration migrations for rollout safety, rollback feasibility, data correctness, and environment-specific deployment risk.

Turn assumptions, funnel opportunities, and product questions into a prioritised, feasibility-checked experiment backlog. Filters by traffic reality, metric latency, and method feasibility — not just ICE/RICE scoring. Maintains a living portfolio with status (idea → designed → running → readout → archived). Load when the user says "what should we test next", "build an experiment backlog", "prioritise our tests", "where should we experiment", "what's worth testing", or when the experimentation orchestrator routes here.

Helps find and analyze competitors to imitate using a five-filter method, focusing on profitability and feasibility while eliminating personal bias.

Guides authorized RF/SDR security research for signal identification, demodulation analysis, and replay feasibility studies in shielded lab environments.

Use when a research proposal needs work packages, milestones, deliverables, a timeline, a risk register, and budget-justification scaffolding, while keeping scientific claims and feasibility honest and human-owned.

Orchestrate token-heavy research, coding, and testing by delegating bounded tasks to cheaper subagents while reserving Claude Fable for architecture, synthesis, and final review.

Configures GKE workload reliability with PodDisruptionBudgets, health probes, topology spread constraints, and graceful shutdown patterns.

Build reproducible ML experiment plans with hypotheses, metrics, and ablations. Use when: (1) planning experiments, (2) comparing variants, (3) defining acceptance thresholds. NOT for: long-running experiment execution.

Stress-test a feature idea for an existing product by surfacing risky assumptions across Value, Usability, Viability, and Feasibility using multi-perspective devil's advocate thinking.

List Available Fabric Capacities

Analyzes encryption algorithms, key management, and file encryption routines used by ransomware families to assess decryption feasibility, identify implementation weaknesses, and support recovery efforts.

Executes authorized phishing simulation campaigns to assess an organization's susceptibility to email-based social engineering attacks, including scenario design, infrastructure setup, and metric tracking.

Implements WCAG-compliant accessibility in Flutter apps with semantic widgets, screen reader support, focus management, and contrast ratio checks.

当需要在众多机会中筛选出投入产出比最高的选项，以最小化风险并最大化潜在回报时

当完成一个创作（文章、产品原型等）后，因自我怀疑或追求完美而犹豫是否发布时

当需要在多个领域积累独特竞争优势，避免单一技能风险时

Design lean validation experiments — hypothesis, method, success criteria, sample size, timeline, and decision rules

当个人希望提升自身在职业或社会中的不可替代性，以应对环境变化和不确定性时

Strategic patterns for solving intractable problems through cascading approximation, self-improvement, and heterogeneous evaluation from DeepMind's AlphaGo system

Multi-phase dialectical stress-test for HIGH-STAKES decisions only (architecture choices, irreversible product calls, strategic bets). Heavy-cost skill — do NOT use for routine questions, brainstorming, or simple tradeoffs. User must explicitly invoke or describe a decision they call "high-stakes", "irreversible", or "needs stress-testing". Triggers: "stress test this decision", "dialectic on", "challenge this thesis", "should I really".

Verify implemented work meets acceptance criteria — run tests, check PHPCS, validate Blade output, lando phpunit, lando phpcs, lando yarn test, Playwright tests, accessibility check, post-implementation verification, done criteria validation, checklist review, verification phase

Run structured What-If scenario analysis with 4-6 branch possibility exploration (best, likely, worst, wild card, contrarian, second-order). Use for speculative questions about uncertain futures, strategic forks, contingency planning, or stress-testing decisions.

Mental models and decision frameworks for building autonomous agents that continuously learn, explore, and accumulate skills in open-ended environments without human supervision

Frame an epic as a testable hypothesis with target user, expected outcome, and validation method. Use when defining a major initiative before roadmap, discovery, or delivery planning.

在启动高风险项目或重要决策前，需要预先识别潜在失败点以增强心理韧性和方案鲁棒性时

Surface every assumption embedded in a plan, strategy, or document, assess how critical and how validated each one is, and identify which ones to test first. Load when the user asks to map assumptions, surface hidden beliefs, find what must be true for this to work, run an assumption audit, or when deep-thinking diagnoses an assumption frame. Also triggers on "what are we assuming", "what must be true for this to work", or "find the untested beliefs". Based on David Bland and Alex Osterwalder's assumption mapping method from Testing Business Ideas.

Turn "what's the plan" into a GTM plan you can defend, verdict-first. Names the two or three bets, the motions behind each, the targets, the capacity math that says whether the number is reachable, and the risks that would break it. Built for B2B GTM leaders, customizable to your model and stage. Trigger on "build our GTM plan", "plan the quarter", "is this number reachable", "what are our bets", "annual GTM planning", "do we have the capacity", or any planning cycle.