tsadoq/deep-plan
Deep planning for non-trivial work: triangulated research, decisions put to you, deep web research per branch, and an AI-consumable plan file in your repo.
Plans a non-trivial change before any code is written: parallel research, every meaningful sub-decision put to the user as an AskUserQuestion, then a plan file whose tasks each carry a failing test. Slash command only: /deep-plan.
Use after a /deep-plan plan is approved and you are ready to build it: "implement the plan", or /deep-plan:deep-plan-execute <plan-path>. Dispatches the plan's tasks in dependency order, one writable agent each. Not for plans produced outside /deep-plan.
Use when the user asks to design-review code, a diff, or a plan file, or to check for shallow modules, leaked implementation detail, unclear names, or missing comments. A parallel critic fleet reviews it, then verifies each finding adversarially.
Turns a raw product idea into a PR-FAQ brief at docs/product/<slug>/brief.md. Interviews you and researches in parallel, then marks every value nobody has established instead of inventing one.
Turns a written brief into product discovery at docs/product/<slug>/discovery.md: an opportunity solution tree, an assumption map, and the riskiest-assumption tests worth running first. Refuses when no brief has been written.
Turns the items in docs/product/<slug>/roadmap.md into implementable slices at docs/product/<slug>/issues/, one markdown file each, then files them as GitHub issues if you ask. Refuses when no roadmap has been written.
Turns a written discovery into testable requirements at docs/product/<slug>/requirements.md: one EARS sentence per thing that must be true, functional and non-functional, each traced to the opportunity it answers. Refuses when no discovery has been written.
Runs a critic-fleet review of one docs/product/ artifact, judged against the rubric its owning beat ships. Reports findings and never edits what it read.
Turns the requirements in docs/product/<slug>/spec.md into a roadmap at docs/product/<slug>/roadmap.md: every item RICE-scored, given a fixed appetite, and placed in a sequence that carries no dates. Refuses when no spec has been written.
Turns validated requirements into a self-contained spec at docs/product/<slug>/spec.md: the problem, every in-scope requirement carried over verbatim, and the non-goals. Names no technology. Refuses when no requirements have been written.
Reports the status of a docs/product/ slug: which chain artifacts exist, which have gone stale, and the one beat to run next.
Use when the user asks to review the planned tests in a /deep-plan plan file: their assertions, doubles, fixtures, level, or flake risk. Reads the plan's Tests (TDD) blocks only -- not diffs, pull requests, or implemented code.