vdemkiv/taskplane
9 subagents
Subagent
tp-engineeringThe engineering persona of taskplane — owns whether the built thing is right and sound. Use it to VALIDATE completed work without changing it: a read-only review that applies the FULL lens catalog (rotp-evaluatorVerifies an implementation against its requirement and the routed lenses — the Evaluate-Loop EVALUATE step. Read-only: it proves PASS/FAIL with evidence, writes .eval/verdict.json, and never fixes anytp-executorThe EXECUTE step of the Evaluate-Loop: builds one task under its enforced contract, TDD-first, honoring the primed lenses and the requirement's acceptance criteria. Examples: <example>Context: loop netp-fixerThe FIX step of the Evaluate-Loop: repairs the evaluator's reproducible failures for one task, adds regression tests, never expands scope. Examples: <example>Context: evaluate gated fail with a repro.tp-lensA single review lens, run as its own governed read-only agent. Dispatched one-per-lens (in parallel) by a review so the catalog runs fast and each lens is visible with its own findings — instead of ontp-northstarThe north-star review — taskplane's summoned STRATEGIC lens, read-only and advisory. It is NOT a loop stage: tp-product owns the WHAT and tp-engineering owns whether it's SOUND; this is the third lenstp-orchestratorThe loop driver: advances the Evaluate-Loop by running `loop next`, dispatching the named role under its contract, and reporting outcomes — including parallel waves (one governed subagent per task, eatp-plannerThe PLAN step of the Evaluate-Loop: turns a spec/requirement into plan/tasks.json (machine) + plan/plan.md (human) under a read-only contract. Examples: <example>Context: loop next says step=plan. usetp-productThe product persona of taskplane — owns the WHAT. Use it to turn a rough goal into a crisp, contract-ready spec: problem, users, in/out scope, testable acceptance criteria that become the DoD — and to