From 7a9caf141c195c864123e9afd7355aa32241bca1 Mon Sep 17 00:00:00 2001 From: Joseph Doherty Date: Fri, 24 Jul 2026 13:24:36 -0400 Subject: [PATCH] docs(drivers): add worktree + subagent execution commands to the tracking doc Per-plan copy-paste command (subagent-driven-development in a git worktree), plus the slash-command and executing-plans/resume alternatives, and a note that the four independent plans can run in concurrent worktrees. Claude-Session: https://claude.ai/code/session_01GASWkNEi68FSCtvr6rLoEW --- .../2026-07-24-driver-expansion-tracking.md | 33 +++++++++++++++++-- 1 file changed, 30 insertions(+), 3 deletions(-) diff --git a/docs/plans/2026-07-24-driver-expansion-tracking.md b/docs/plans/2026-07-24-driver-expansion-tracking.md index 3975bb5b..9b88fb66 100644 --- a/docs/plans/2026-07-24-driver-expansion-tracking.md +++ b/docs/plans/2026-07-24-driver-expansion-tracking.md @@ -41,6 +41,33 @@ it reaches 📝. --- +## Executing a plan (git worktree + subagent-per-task) + +Each 📝 plan is executed with the **subagent-driven-development** skill: it sets up an isolated +**git worktree** first (via `using-git-worktrees`), then dispatches a **fresh subagent per task**, +running the classification-driven review chain (`trivial` = implement only … `high-risk` = +spec-review → code-review → integration review) between tasks. The `.tasks.json` next to each plan +tracks progress and lets a later session resume. + +**Paste one of these into Claude Code to build a driver:** + +| Deliverable | Command | +|---|---| +| Modbus RTU (Wave 1) | `Use superpowers-extended-cc:subagent-driven-development to execute docs/plans/2026-07-24-modbus-rtu-driver.md in a new git worktree` | +| SQL poll (Wave 1) | `Use superpowers-extended-cc:subagent-driven-development to execute docs/plans/2026-07-24-sql-poll-driver.md in a new git worktree` | +| MTConnect (Wave 2) | `Use superpowers-extended-cc:subagent-driven-development to execute docs/plans/2026-07-24-mtconnect-driver.md in a new git worktree` | +| MQTT/Sparkplug (Wave 2) | `Use superpowers-extended-cc:subagent-driven-development to execute docs/plans/2026-07-24-mqtt-sparkplug-driver.md in a new git worktree` | + +- **Slash-command form** (equivalent): `/superpowers-extended-cc:subagent-driven-development `. +- **Parallel-session / resume form** (batch execution with checkpoints, no fresh-subagent-per-task): + `/superpowers-extended-cc:executing-plans ` — reads the same `.tasks.json` and continues + from the first pending task. +- **Recommended order:** Modbus RTU → SQL poll → MTConnect → MQTT/Sparkplug (lowest effort first; + see each wave below for the gating notes). Run one plan per worktree; the four plans are + independent, so separate worktrees may run concurrently. + +--- + ## Wave 0 — Universal Discover-backed browser 🟡 **What it is.** One generic `DiscoveryDriverBrowser` (+ `CapturingAddressSpaceBuilder`, @@ -120,9 +147,9 @@ Both CI-simulatable on the shared docker host, no hardware. ## Next actions 1. **Close the Wave-0 live gate** (Gitea #468) — unblocks browse verification for MTConnect/BACnet. -2. **Build Wave 1** via subagent-driven development — Modbus RTU first (lowest effort, no new infra), - then SQL poll. Both plans are 📝 ready; execute with - `/superpowers-extended-cc:executing-plans docs/plans/2026-07-24-modbus-rtu-driver.md`. +2. **Build Wave 1** — Modbus RTU first (lowest effort, no new infra), then SQL poll. Both plans are + 📝 ready; run the command from the [Executing a plan](#executing-a-plan-git-worktree--subagent-per-task) + table (subagent-driven-development in a git worktree). 3. **Build Wave 2** (MTConnect, then MQTT/Sparkplug) — both plans 📝 ready. MTConnect's browse leg wants #468 closed first; MQTT's Task 0 pinning spike gates everything after it.