Roadmap

As of April 16, 2026, yt-text has a published v0.1.8 release, green self-hosted CI, release tarballs for three targets, checksum generation in the release workflow, and a materially stronger docs surface for install, integrations, agent usage, examples, troubleshooting, and planning.

The next phase is go-to-market surface: make install frictionless, deepen agent integrations, and expand the docs/examples layer so a new user can evaluate and adopt the project without maintainer hand-holding.

Shipped

  • v0.1.8 published with GitHub release tarballs for Apple Silicon macOS, Linux x86_64, Linux ARM64, and an npm wrapper asset
  • authenticated private-repo install support in install.sh and the npm wrapper bootstrap
  • public Pages mirroring of the latest release assets for anonymous installs
  • serialized honey musl release jobs with CARGO_BUILD_JOBS=1 to avoid Linux release runner OOM and artifact-upload flake
  • npm registry publication as @tummycrypt/yt-text@beta on npmjs.com (SLSA provenance) with a GitHub Packages mirror as @jesssullivan/yt-text
  • release workflow support for SHA256SUMS
  • release workflow support for yt-text-npm-package.tgz
  • MCP tools for transcript extraction, language listing, and metadata
  • opt-in po-token and whisper feature paths
  • client-specific integration guides and compatibility matrix
  • quickstart walkthroughs for common user stories
  • sample outputs and troubleshooting pages
  • install lifecycle docs for upgrade, uninstall, and platform support
  • contributor and agent scaffolding with CONTRIBUTING.md, AGENTS.md, and llms.txt
  • agent-focused usage guidance for in-session MCP workflows
  • comparison and positioning docs
  • GitHub Pages docs deployment with generated llms.txt, robots.txt, and sitemap.xml
  • release history and public release documentation
  • launch-operation templates for release notes, announcement copy, demo flow, and post-launch triage
  • GitHub release-note categorization via .github/release.yml
  • issue templates for bug reports and feature requests

Now

  • decide whether the public Pages mirror stays the primary anonymous install surface or whether the repository itself becomes public
  • decide whether npm and nixpkgs become real published channels
  • assign launch owner for the first broader push

Next

  • run the first broader announcement wave using the prepared launch collateral
  • watch docs drift by keeping integration and agent docs tied to real client behavior
  • refine public docs once GitHub Pages usage patterns are visible

Later

  • broaden community examples and templates
  • add more end-to-end agent demos
  • revisit extra packaging channels if demand justifies them
  • explore live stream agent transcription for YouTube Live, radio, Twitch, Kick, and generic audio streams
  • explore an optional hosted HTTP/SSE service for managed streaming STT and PoToken handling while keeping the local FOSS binary first-class

Planning Artifacts

Internal GTM planning docs for the current phase live under docs/plans/:

  • 2026-04-16-gtm-initiative.md
  • 2026-04-16-gtm-milestones.md
  • 2026-04-16-launch-checklist.md