Results for “docs-repo”

Search Notion pages, synthesize findings, and publish structured briefs, summaries, comparisons, or reports with citations and source links.

Query documented public database APIs with explicit endpoints, filters, pagination, and provenance for reproducible retrieval of scientific, regulatory, or financial facts.

Simulates a NeurIPS/SC/ICSE-style peer review with five reviewer personas (HPC, ML, Stats, Reproducibility, Devil's Advocate) that verify every claim against actual result data before submission.

Search, browse, and retrieve scientific protocols from protocols.io via REST API, including private protocols with client token authentication.

Search and fetch Notion pages, synthesize findings, and publish structured briefs, summaries, comparisons, or reports with citations and source links.

Interrogates a plan against real third-party documentation, extracting hard constraints and asking doc-cited questions before producing a constraints appendix.

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.