Results for “artifacts”

Traces design decisions and concepts through session history, handoffs, git, and artifacts, producing a chronological timeline report with citations.

Compiles research inputs—PDFs, code, logs, notes—into structured Agent-Native Research Artifacts with cognitive and physical layers.

Performs a semantic epistemic review of Agent-Native Research Artifacts, scoring six dimensions and producing a constructive report with a recommendation.

Compile deep repository evidence into artifact-bound correctness doctrine, including authority/law/proof maps, owned invariants, failure archaeology, and knowledge routing, with an optional minimal repository-specific skill portfolio.

Wraps the notebooklm-py CLI to ingest sources and generate synthesized artifacts like podcasts, slide decks, and quizzes from Google NotebookLM.

Use when a research design spec exists and the user is ready to translate it into a concrete implementation plan with phased tasks, artifacts, and verification criteria. Produces a research execution plan organized in canonical research phases — collection, preparation, analysis, robustness, writing, submission.

Evaluates the trade-off between file size reduction and image fidelity when encoding radio astronomy data using JPEG2000, benchmarking both lossless and lossy compression modes to determine the compression ratio at which visual artifacts first appear.

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.