In development · Unreleased · Not currently in use
This is a research prototype. It has not been released for use. APIs, skills, and workflows may change. Do not treat historical test evidence as proof that the product is production-ready.
ITDD Control Plane explores a small, human-invoked planning workflow: clarify a request, collect and verify relevant project data, publish a spec and human-agreed tickets through the configured issue tracker, then stop with links and a suggested next move.
For a new or existing repository:
- Collect facts first. Inspect the current code, docs, tracker, prior decisions, and relevant research or evidence. Record sources and unknowns. Do not turn unverified history into current requirements.
- If the repository lacks project-specific Matt Pocock skill configuration, run
/setup-matt-pocock-skillsto configure the tracker, triage labels, and domain docs. - Run
/itdd-prepareto clarify the request and prepare the planning handoff. - Agree on the spec and ticket breakdown. Publish them through the configured tracker.
- Stop with the links, unresolved questions, and suggested next move. A
ready-for-agentlabel or planning agreement does not authorize execution.
See Getting Started and the Prime planning guide.
/itdd-new is optional later-stage execution setup. It is not required for planning. The current planning path does not invoke BUILD, TEST, VERIFY, or the controller runtime.
- The product is in development, unreleased, and not in use.
- The planning-first workflow is the current product direction. The controller, schemas, broader skill manifest, and execution architecture are research/prototype material, not a supported production service.
- This repository contains historical reports, experiments, and evidence. Their status applies only to the specific dated work they describe; it does not establish a product release or current acceptance.
- No formal approval record should be claimed unless a supported controller interface actually records it.
This checkout is for contributors and research. It is not a published package installation guide. The commands below install this source checkout for local development and tests; they do not indicate a published distribution or supported end-user installation.
git clone https://github.com/Sailor422/itdd-control-plane.git
cd itdd-control-plane
python -m venv .venv
source .venv/bin/activate
python -m pip install -e ".[dev]"
python -m pytest -qSee Contributing for the development workflow. Collect source data before proposing changes; keep evidence and failed attempts intact, and clearly label drafts, historical reports, and unverified claims.
- Contributor archive and source inventory — curated research, historical guides, and evidence pointers.
- Research notes — dated research, not normative policy.
- Architecture notes and ADRs — broader prototype design; not the current planning quick start.
- Planning-first Wayfinder map — product decisions and follow-up work.
MIT. See LICENSE.