ttfv-tracelisted

# Time-to-first-value trace Walk a quickstart the way a stranger would and time it. Most teams have never measured this; the industry-standard method is still a stopwatch, which is why nobody does it twice. The output is a per-step timing table with the blockers named. That table is the finding — a single number tells a team they are slow, the table tells them which paragraph to fix. ## Applies to | | | |---|---| | **Project types** | Anything with a self-serve onboarding path — APIs, SDKs, CLIs, frameworks, developer platforms | | **Stage** | Any product with a published quickstart. Most valuable immediately before a launch or paid campaign, since traffic pointed at slow onboarding wastes the spend | | **Needs** | A quickstart, getting-started guide, or a README with setup steps | | **Skip if** | No public onboarding path exists yet, or the product is sales-led with an implementation team — there is no cold-developer journey to time | Also worth running after any change to auth, installation, or the first-call flow. Those edits are where onboarding silently regresses. ## How to use ``` /agentrel:ttfv-trace trace this repository's quickstart /agentrel:ttfv-trace https://docs.acme.com trace a public onboarding path /agentrel:ttfv-trace ./docs/getting-started.md trace a specific document ``` Produces `ttfv-report.md` and a printed timing summary. Read-only. Safe commands are executed for real timings. Paid signups and destructive ste