Results for “roa”

Provides reviewer-style audit and deep review for academic papers in LaTeX, Typst, and PDF formats, producing structured issue bundles, pass/fail gates, and revision roadmaps.

Red-team a PRD, roadmap, or strategy by attacking its load-bearing assumptions before reality does, ranking failure modes by impact, likelihood, and cheapness to test.

Run cloud-native molecular modeling and drug-design workflows including pKa prediction, docking, molecular dynamics, and protein-ligand cofolding via a Python API.

Build a weekly cadence of customer touchpoints using Opportunity Solution Trees, assumption mapping, and interview snapshots to keep product decisions grounded in evidence.

Pressure-test any business idea with a five-angle adversarial panel (Critic, Champion, Analyst, Investigator, Customer) that returns a single GO/RESHAPE/KILL verdict with the cheapest test to de-risk it.

Use to CREATE or REVIEW a Job to be Done (JTBD) in Alan Klement's demand-side, progress-based sense — a job is the progress a customer is trying to make, never a task or feature. Trigger whenever someone wants to write or draft a JTBD, job statement, or job story; figure out the real motivation, struggle, or progress behind a feature, request, or product; understand why customers switch, adopt, or churn; turn interview notes or research into jobs; or pressure-test, sharpen, or rewrite existing JTBDs into proper jobs. Also trigger on "grill my JTBD", "is this a real job or just a task/feature", "what's the actual job here", "why would they switch". In an A-Team target repo, jobs are durable artifacts — this skill writes docs/product/jtbd/NN-<slug>.md per CONTRACT.md and never deletes or silently rewrites a job. Do NOT use for writing PRDs, roadmaps, tickets, or acceptance criteria (those consume a finished JTBD), or for implementation user stories.