Packs
1 packResults for “product-review”
7 skillsMore results
competitive-teardown
Analyzes competitor products by synthesizing data from pricing pages, app store reviews, job postings, SEO signals, and social media into structured competitive intelligence. Produces feature comparison matrices, SWOT analyses, positioning maps, UX audits, pricing breakdowns, action plans, and presentations.
20.4k · bundle
claims-links-product-proof
Verify the article’s factual, product, citation, and link integrity before visual production.
0
product-research
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.
20.4k · bundle
paper-audit
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.
3 · bundle
review
Routes quality reviews to specialized critic agents based on file type or flags, covering peer review, code review, and manuscript polish.
3 · bundle
jobs-to-be-done
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.
0 · bundle