Results for “select”

The meta-framework for how a company runs — the connective tissue between all C-suite roles. Covers operating system selection (EOS, Scaling Up, OKR-native, hybrid), accountability charts, scorecards, meeting pulse, issue resolution, and 90-day rocks. Use when setting up company operations, selecting a management framework, designing meeting rhythms, building accountability systems, implementing OKRs, or when user mentions EOS, Scaling Up, operating system, L10 meetings, rocks, scorecard, accountability chart, or quarterly planning.

Guides SaaS pricing strategy: selecting models, value metrics, packaging tiers, and applying psychology tactics to optimize revenue.

Treats rough ideas as competing organisms on an evolution island, scoring, selecting, crossing, and evolving them through structured rounds to surface the strongest concepts.

Guides selection of Qdrant search strategies including hybrid search, reranking, relevance feedback, MMR, and discovery APIs to improve retrieval quality.

Creates a professional paid-advertising strategy covering objectives, economics, platform selection, campaign architecture, audiences, budget, creative, measurement, experiments, governance, rollout, and reporting.

Transforms business requirements, use case descriptions, or meeting transcripts into a technical Power Platform solution architecture, including component selection and Mermaid.js diagrams.

Select the right Proof of Life (PoL) probe type based on hypothesis, risk, and resources to match validation method to the real learning goal.

Provides battle-tested PyTorch training recipes for LLMs, vision, diffusion, and biomedical domains, covering training loops, optimizer selection, LR scheduling, mixed precision, and debugging.

Build an Opportunity Solution Tree from outcomes to opportunities, solutions, and tests. Use when a stakeholder request needs problem framing before you decide what to build.

BluOS CLI (blu) for discovery, playback, grouping, and volume.

Selects pricing models (subscription, usage-based, value-based, freemium, hybrid), analyzes willingness-to-pay survey data with Van Westendorp PSM, and designs Good/Better/Best packaging tiers with anti-pattern detection.

BluOS CLI (blu) for discovery, playback, grouping, and volume.

Scans a project for stack signals and pain points, searches the skills-hub registry and local skills, scores candidates, and presents a ranked shortlist with install commands.

Navigate the technology adoption lifecycle to cross from early adopters to mainstream markets using the D-Day strategy, beachhead selection, whole product assembly, and competitive positioning.

Plan and synthesize product/user research with method rigor: select the right method for the goal, compute defensible sample sizes with confidence labels, and cluster coded observations into insights while flagging single-source anecdotes.

Plans a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, or balancing scope against velocity. Triggers on: sprint planning, sprint plan, capacity planning, sprint scope, story points, sprint goal, backlog grooming, sprint prep, what do we build this sprint.

Battle-tested PyTorch training recipes for all domains — LLMs, vision, diffusion, medical imaging, protein/drug discovery, spatial omics, genomics. Covers training loops, optimizer selection (AdamW, Muon), LR scheduling, mixed precision, debugging, and systematic experimentation. Use when training or fine-tuning neural networks, debugging loss spikes or OOM, choosing architectures, or optimizing GPU throughput.

Security leadership for growth-stage companies. Risk quantification in dollars, compliance roadmap (SOC 2/ISO 27001/HIPAA/GDPR), security architecture strategy, incident response leadership, and board-level security reporting. Use when building security programs, justifying security budget, selecting compliance frameworks, managing incidents, assessing vendor risk, or when user mentions CISO, security strategy, compliance roadmap, zero trust, or board security reporting.

Review an open GitHub issue for a selected repository against the current codebase, then either close it as already implemented with an evidence comment, label it needs clarification with an explanatory comment, or create a fleshed-out Jira story in the requested board/project when the remaining work is clear. Use when triaging GitHub issues into Jira backlog work or closing stale implemented GitHub issues.

Use when a user asks to use, run, delegate, or fulfill a task through a capability that may exist as an online Bot/MetaBot skill-service, especially when no local specialized skill matches. Treat Bot, bot, and MetaBot wording as equivalent and case-insensitive for remote service requests; select from the local cached online service list first, then call the remote service and continue through trace get/watch, optional conversation view opening, and rating closure. Do not use for browse-only service discovery, network source registry management, identity creation/switching, or private chat-only requests.