What if you could adopt a development methodology by pointing AI at a URL?
Not "read this book and internalize it over six months." Not "hire a consultant to train your team." Just: "read this spec and work this way."
What exists today
- Cursor rules / AGENTS.md — project-level instructions for AI. Coding style, conventions. But not methodology.
- Architecture Decision Records — document decisions for humans to read. Not for AI to execute from.
- Spec-driven development (Kiro) — tool-specific. Not portable.
- Infrastructure as Code — captures infrastructure as files. Not the development process itself.
Nobody's sharing executable development workflows as specs that AI implements from. People share coding standards. Nobody shares methodology.
What theTube proves
The specs and skills in this repo capture a complete development methodology:
- How to think about a problem (journal entry)
- How to structure the thinking (spec)
- How to implement (code from spec)
- How to track the process (journey block)
- What principles to follow (steering file)
- What constraints to respect (platform spec)
Any AI that reads these files can work this way on any project. No fork needed. No installation. Just a reference to a URL.
The methodology is the product
The blog is the proof of concept. The platform is the implementation. But the methodology — journal-driven development, files at URLs, specs as the source code — that's the thing that's actually new. And it's portable because it's just files.
A company could adopt this by pointing their AI at these specs. A solo developer could adopt it the same way. The barrier is zero because the methodology is a URL, not a training program.
The journey
prev: plugins-are-specs-not-code The plugin model applied to methodology itself. If plugins are specs that AI reads and implements, then workflows are too. The development methodology is just another spec at a URL. Nobody else seems to have proposed this specific idea — methodology as a portable, AI-executable file.