Guides you through running a technical spike or experiment yourself instead of handing you a conclusion. You frame the unknown, the decision it unblocks, and what result would kill the hypothesis; Claude builds and runs the throwaway experiment and reports observations with evidence; you interpret the results and state a verdict checked against what actually ran.
1 on GitHubby gvillenavev0.1.0MITupdated 1 month agoexperimentation
/
Plugin spike-coach from marketplace humantouch in gvillenave/humantouch. Commands read from the repo's manifest — 1 month ago.
Walks you through reading an unfamiliar codebase instead of summarizing it for you. Presents a map, then guides you component by component while you read the code, predict what it does, and build your own working model.
Guides you through diagnosing and fixing a bug yourself instead of patching it for you. Gathers the evidence, poses ranked hypotheses, and walks the investigation one step at a time while you form the diagnosis and write the fix.
Stress-tests your system design decisions instead of producing an architecture for you. Interviews you about constraints, poses one trade-off at a time, and challenges each decision you make with concrete failure scenarios.
Guides you through writing your own technical document instead of generating one for you. Covers design docs, RFCs, ADRs, runbooks, postmortems, specs, PRDs, proposals (change proposals included), one-pagers, project plans and briefs, READMEs, and more.
Guides you through estimating your own work instead of producing estimates for you. Maps what each ticket actually touches — hidden work, unknowns, and how AI-assisted coding reshapes the effort — then you name every estimate and defend it against concrete stress tests. Ends with an estimate sheet verified against your words and sources.
Guides you through decomposing a coding project into an execution plan you own instead of generating a plan for you. Mines your docs, tickets, and codebase for the real work and dependencies while you make every scoping, sequencing, and milestone decision — ending with an outline of steps, milestones, and tickets, verified claim by claim against your sources, plus a handoff to doc-coach for the shareable writeup.
Statically analyze a local JS/Electron app you're authorized to study, with file+line evidence, and build an original reimplementation of what you find. Experimental. Phase 1: JS/Electron static analysis. Phase 2: native ELF/PE/Mach-O container inspection. Phase 3: .NET assembly metadata. Phase 4: EVM bytecode inventory. Phase 5: CUDA fatbin, cubin and PTX inventory. Parses, never executes. Dynamic analysis is a future phase, not yet implemented.
Query Trackio projects, runs, and metrics using the `trackio` CLI. Use when the user needs to list projects/runs/metrics, get summaries, or retrieve metric values from local Trackio databases. Supports both human-readable and JSON output formats. Covers project discovery, run inspection, metric querying, and system metrics. Designed for LLM agents and automation scripts.
Use Amplitude as an expert analyst — instrument Amplitude, discover product opportunities, analyze charts, create dashboards, manage experiments, and understand users and accounts.
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.