Product & Planning

kody-w Bundle

Use this skill whenever the user asks to document, map, standardize, redesign, or improve a business process from notes, transcripts, interviews, or requirements, especially when they need an editable SOP, process map, RACI, controls, improvement backlog, or polished PowerPoint briefing.

kody-w Bundle

Facilitates a zero-based AI-first process redesign session that helps a team reimagine an existing work process as AI-first. Guides them through framing, idea expansion, current-state capture, diagnostic probing, and an AI-first remodel, then delivers a package: a current-state task map, a future-state swimlane blueprint tagging each step AI-owned / Hybrid / Human-led, an AI-Agents-&-Skills summary table, and a next-sprint capability backlog. Weighs the full range of AI building blocks — process change, knowledge, tools, reusable skills, agents, connected agents — instead of defaulting to an agent. Use when the user wants to redesign a process for AI, make a workflow AI-first, map which tasks AI should own, or find AI or agent opportunities in a process. It shows WHERE AI could help; it does NOT build or deploy the agents or skills themselves. Do NOT use to build a specific agent or skill, for a one-off automation with no process to rethink, or for employee performance evaluation.

kody-w Bundle

Convert a hand-drawn whiteboard photo (or sketched process/diagram) from a discovery or working session into a polished, client-ready infographic as an editable PowerPoint slide (.pptx). Use this whenever someone uploads or references a photo of a whiteboard, a hand sketch of a process or system, or session-capture notes and wants it "cleaned up", "made presentable", "turned into a diagram/infographic", "converted for the client", or similar — even if they don't say the word "infographic". Covers two layout archetypes — linear process flows (left-to-right step rails) and network/topology maps (locations, systems, or actors connected by labeled flows). Built for consulting/ERP discovery capture but works for any whiteboard-to-deliverable conversion. Do NOT use for charts/graphs from numeric data, for editing an existing polished design, or for generating diagrams with no source sketch.

broomva Bundle

Scaffold a substantive human-readable design doc (spec / plan / ADR / report / PR explainer) as native HTML using the workspace's canonical Broomva dark theme. Implements P18 (Format-Follows-Audience) for Category-C native artifacts — distinct from `bookkeeping render`, which projects Category-B markdown canonicals to HTML. Use when: (1) drafting a substantive design doc a human will actually read (>100 lines OR contains tables/diagrams/decision matrices), (2) writing an ADR (architectural decision record), (3) producing a plan a non-agent stakeholder will review, (4) writing a PR explainer for a substantive PR, (5) producing a report that synthesizes prior research. The skill ships theme.css + the spec HTML template, and generates the plan / adr / report / pr-explainer variants from that same theme + the prose skeletons below — so the agent doesn't rebuild the 70-line :root + h1-h4 + table + callout boilerplate every time. Triggers on "spec", "plan", "ADR", "decision record", "design doc", "explainer", "repo

broomva Bundle

AI-native advisory practice for the Broomva ecosystem. Encodes top-firm consulting methodology (Three Horizons, MIT CISR digital maturity, JTBD, Value Proposition Canvas, RICE/ICE/WSJF, NPV + Real Options, QuantumBlack ML lifecycle, Wardley Mapping) as runnable typed primitives. Produces 7 Discovery-grade deliverables in two modes — consultant CLI or autonomous Life Runtime endpoint. Use when: (1) running an AI/digital consulting engagement, (2) building a maturity assessment, (3) generating prioritized use-case dossiers, (4) designing an innovation roadmap, (5) modeling ROI for AI initiatives, (6) designing controlled pilots, (7) extracting reusable IP from completed engagements. Triggers on 'consulting', 'consultancy', 'advisory', 'fast discovery', 'discovery sprint', 'AI maturity', 'digital maturity', 'use case ideation', 'use case prioritization', 'innovation roadmap', 'roi model', 'consultoría', 'evaluación de madurez', 'hoja de ruta'.

broomva Bundle

Rewrite a requirement so it can only be read one way. Distilled from ASD-STE100 Simplified Technical English — forty years of aerospace evidence about what a reader misreads when they cannot ask the author what he meant. Turns a vague ask ("handle errors gracefully", "the system should support X") into something atomic, owned, bounded, and testable, and says which of five reader-questions each defect leaves open. Ships a deterministic checker (scripts/disambiguate.py, stdlib only) that catches the mechanical ambiguity — agentless passive, noun stacks, weak modals, unquantified deltas, compound obligations, over-length sentences, condition-after-action, synonym drift — so judgment goes to the parts that need it. USE WHEN: sharpening a requirement, acceptance criterion, ticket, spec line, PRD, API contract, error message, runbook step, or agent prompt. Also when a review comment says "unclear" or "what does this mean", when two people read the same line differently, and when writing instructions for someone who

broomva Bundle

Comprehensive bioinformatics and ocean genomics skill for eDNA metabarcoding, metagenomics, protein structure prediction, and marine biodiversity analysis. Use when: (1) Working with DNA/RNA sequences (FASTQ, FASTA, SAM/BAM, VCF files), (2) Running BLAST, QIIME2, Kraken2, or Nextflow pipelines, (3) Predicting protein structures via ESMFold2, AlphaFold, or ColabFold, (4) Analyzing environmental DNA (eDNA) from marine samples, (5) Querying marine databases (OBIS, BOLD, DOO, GenBank, UniProt), (6) Using biological foundation models (Evo 2, ESMC/ESMFold2, ProGen3), (7) Setting up MCP servers for bioinformatics (gget-mcp, bio-mcp), (8) Building agentic bioinformatics workflows, (9) Ocean biodiversity research, deep-sea species discovery, extremophile enzyme characterization, (10) Any task involving genomics, proteomics, transcriptomics, or computational biology.

broomva Skill

Takes one set of project facts and generates three versions: technical for engineering, business-impact for leadership, and customer-facing for success teams. Use when the user says "stakeholder update", "write an update", "communicate this to different audiences", "translate for leadership", "customer-facing version", or needs to communicate the same information to different audiences.

broomva Bundle

Knowledge engine over the Colombian Truth Commission (CEV) final report "Hay Futuro Si Hay Verdad" (2022) — the findings, statistics, armed-actor responsibilities, differential harms, coined lexicon, and the 67-recommendation roadmap for non-repetition (no repetición). Uses a kg/LLM-wiki retrieval architecture (substrate-canonical knowledge pages + a dense catalog projection for tier-1 routing + body-grep tier-2 + the agent as query engine) plus data-backed tools, including an `align` check that scores a proposed policy/action against the report's recommendation roadmap. USE WHEN reasoning about the Colombian armed conflict, peace process, transitional justice, victims, reconciliation, paramilitarism, the FARC-EP/ELN, narcotrafficking and drug policy, land/agrarian questions, the enemigo interno, falsos positivos, the Unión Patriótica genocide, social-leader killings, differential harms (ethnic peoples, women and LGBTIQ+, children, exiles, campesinado), territorial/human security, memory, or non-repetition; w

broomva Bundle

Personalized cancer treatment navigation — maximal diagnostics, parallel therapy, therapeutic development, structure-based protein design. Use when (1) researching cancer treatments or combinations, (2) designing diagnostic strategies, (3) evaluating neoantigen vaccines or radioligand therapies, (4) navigating FDA expanded access or IRB processes, (5) interpreting ctDNA/MRD data, (6) building bioinformatics pipelines, (7) scRNA-seq target discovery, (8) AlphaFold/RFdiffusion/ProteinMPNN for neoantigen validation or de novo binder design, (9) patient advocacy. Keywords — cancer, oncology, neoantigen, vaccine, immunotherapy, radioligand, ctDNA, scRNA-seq, FAP, AlphaFold, RFdiffusion, ProteinMPNN, personalized medicine.

cratis Bundle

Draft accurate Cratis documentation content after the owning repository, page placement, document type, and authoritative product sources are known. Use for tutorials, how-to guides, explanations, and references; defer placement, existing-page discovery, and visual QA to their companion workflows.

cratis Skill

Sanitized fixture proving recursive discovery would expose an engineering skill.

yknothing Bundle

Use when discovery needs evidence about target users, behaviors, and pain points, especially after intake or problem-framing surfaces open questions that must be validated before requirements are written

yknothing Bundle

Use when a live production issue needs coordinated containment, severity triage, stakeholder communication, and evidence capture, especially when a recent release, brownfield coexistence rules, rollback decisions, or unresolved contract boundaries must be handled before root-cause work.

yknothing Bundle

Use when discovery needs evidence about market demand, competitors, pricing pressure, or underserved segments for a new product or expansion idea before feasibility, user research, or requirements are finalized.

yknothing Bundle

Use when discovery has narrowed an idea enough that the team must make a go/no-go, pivot, or scope-down decision based on technical, economic, operational, or timeline viability before requirements, architecture, or major implementation.

yknothing Bundle

Use when the work is still at the “what should we build” stage and approved discovery inputs or entry-stack outputs must become prioritized requirements and scope boundaries before specification, architecture, planning, or coding. Not for acceptance criteria, spec review, or implementation.

yknothing Skill

Use when intake has identified the likely lifecycle path but the problem statement, solution direction, or key trade-offs are still too fuzzy for requirements, research, or architecture work to start cleanly

yknothing Skill

Use when discovery needs evidence about target users, behaviors, and pain points, especially after intake or problem-framing surfaces open questions that must be validated before requirements are written

yknothing Skill

Use when the work is still at the “what should we build” stage rather than design or implementation. Apply before spec-writing, architecture, API design, planning, or coding when interviews, personas, stakeholder notes, or discovery artifacts must be turned into prioritized functional requirements, non-functional requirements, scope boundaries, traceable sources, and explicit “the system shall” statements; not for acceptance criteria, PRD drafting from an approved requirements doc, spec review, or implementation.

frankxai Skill

Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning

nandanosql Skill

Set clear Objectives and Key Results that connect team work to company strategy. Covers OKR writing, alignment, grading, and common mistakes that make OKRs useless.

nandanosql Skill

Create hypothesis-driven user personas before doing full research. Uses behavioral attributes, goals, and frustrations to model target users quickly for early-stage alignment.

nandanosql Skill

Design effective customer surveys that yield actionable insights. Covers question types, bias avoidance, sampling, and analysis frameworks to replace vanity feedback with real signal.

equinor Skill

Field development workflows, concept selection, and integrated project evaluation using NeqSim. USE WHEN: performing field development studies, concept screening, tieback analysis, production forecasting, or integrated field planning. Covers the full lifecycle from discovery through operations with NeqSim's field development classes.

equinor Skill

Autonomous investigation loop for operational and engineering anomalies — turns an agent from 'told what to look for' into 'discovers relationships and hypotheses on its own'. USE WHEN: solving a PEPR action, root-cause, or operational study where the symptom, driver, or important relationships are NOT given up front. Runs an observe -> hypothesize -> predict -> test -> discriminate loop, using neqsim.process.diagnostics.RelationshipGraph for unsupervised lead-lag relationship discovery across historian tags, then hands the discovered relationships to neqsim-root-cause-analysis. Anchors on neqsim.process.diagnostics classes.

the-utopia-studio Bundle

Fires when a fellow asks which numbers matter for a launched product — "what metrics should we track", "what should our North Star be", "is our retention any good / does the curve flatten", "our MAU is up-and-to-the-right, is that real or vanity", "what's our cost per outcome". Returns a metric scorecard: one customer-centric North Star, an AARRR one-metric skeleton, the flattening-retention truth test that GATES the North Star, and cost-per-outcome priced to the cent. Do NOT fire to design the post-launch improvement loop or promote autonomy (use refine-flywheel), to turn production traces into discovery interviews (use trace-to-interview), or to build the actual cohort dashboard, SQL, or alert thresholds (use the M9 retention-dashboard / cohort-analysis skills).

the-utopia-studio Bundle

Walks one validated problem up a load-bearing stack — validated problem → vision → strategy → product vision → North Star → OKRs → dual-track roadmap — and BLOCKS any layer from resting on an unvalidated problem below it. Fires on "frame the business", "vision to roadmap", "what's the strategy", "turn this validated problem into a roadmap", "give me the vision, North Star and OKRs". Output is a filled frame stack where every layer inherits the problem's evidence rung and every roadmap item ladders to a North Star. NOT the go/no-go that validates the problem in the first place (use problem-quality-scorecard / so-what-stress-test — this consumes their verdict), NOT the desirable/feasible/viable score (four-lenses-test), NOT the post-launch metric-tree and retention check (metrics-that-matter).

the-utopia-studio Skill

Interview the user and produce an Agent PRD — the planning document that must exist before any agent code is written. Use when the user wants to build, scope, spec, or plan a new agent, generator, critic, pipeline stage, harness, or autonomous system; when they say "new agent", "agent PRD", "spec this agent", "plan this agent", "I want to build an agent that...", or ask what questions they should answer before starting. Also use when an existing agent is being rebuilt or a stage is being added to a pipeline. Do not use for writing agent implementation code — this skill produces a document only.

the-utopia-studio Bundle

Splits a buying situation into four distinct people — user (feels the pain, touches the product), buyer (owns the budget line), decision-maker (final signature / veto), champion (spends internal capital to push it) — each pinned to ONE title, ONE budget (or an explicit none), ONE why-now. Fires on "who's the actual buyer", "who decides", "map the stakeholders", "map the buying committee", "the user loves it but who signs the cheque", "who's our champion and who can veto us". Output is a filled Stakeholder-Role Map that feeds the buyer-clarity row of problem-quality-scorecard. NOT the 8-dimension go/no-go (problem-quality-scorecard), NOT ranking which unmet need to build first (unserved-needs-finder), NOT a demographic day-in-the-life persona (proto-persona), NOT simulating users before interviews (synthetic-users).

the-utopia-studio Skill

Framework-driven feature and initiative prioritization using RICE, ICE, or weighted scoring. Grounds prioritization in strategic pillars and demands evidence-based scoring. Trigger phrases: "prioritize features", "prioritization", "rank these initiatives", "RICE score", "ICE score", "what should we build next", "prioritize my backlog"

the-utopia-studio Bundle

Stands up ONE living opportunity tree fed by three live inputs and keeps it current after launch. Fires when a fellow says "set up discovery", "continuous discovery", "opportunity tree", "keep learning after launch", or "discovery after launch". Returns an opportunity tree (outcome → opportunities → solutions → tests) wired to customer interviews, production traces, and eval telemetry — each feed stamped with its evidence rung, its cadence, and a named synthesis owner. NOT for scoring one signal's rung (use evidence-ladder), picking which probe tests one question (use probe-matrix), or running a single customer interview (use tacit-knowledge-interview).

zjunlp Skill

Comprehensive analysis of public companies using SEC EDGAR 10-K financial data stored in a SQLite database. Use this skill whenever the task involves analyzing a company by CIK (Central Index Key), querying SEC financial data, exploring a financial database with tables like companies, filings, financial_facts, or producing a structured financial analysis report. Covers schema navigation, metric discovery, industry-specific exploration, multi-year trend analysis, income statement structure, capital returns analysis, long-term obligations, and producing an insightful financial summary that connects metrics across dimensions.

oleg-koval Bundle

Draft policy-compliant Ukrainian Wikipedia edits: translate an English article into uk, expand or source an existing uk article, or fix a maintenance backlog item, and return ready-to-paste wikitext plus an edit summary. Use when given a uk.wikipedia.org or en.wikipedia.org URL or article title to edit, translate, source, or improve, or when planning what to contribute to ukwiki next.

muhammedadnank Bundle

This skill should be used when the user asks to "create a plugin", "scaffold a plugin", "understand plugin structure", "organize plugin components", "set up plugin.json", "use ${CLAUDE_PLUGIN_ROOT}", "add commands/agents/skills/hooks", "configure auto-discovery", or needs guidance on plugin directory layout, manifest configuration, component organization, file naming conventions, or Claude Code plugin architecture best practices.

muhammedadnank Bundle

This skill should be used when agent work needs file-backed context: durable scratchpads, tool-output offloading, just-in-time discovery, cross-agent handoff files, filesystem memory, or cleanup policies for context stored outside the prompt.