feat: orchestrate confirmed workstreams

Author: Howe829

.agents/plugins/marketplace.json

@@ -9,7 +9,7 @@
       "source": {
         "source": "local",
         "path": "./plugins/tfd",
-        "version": "3.1.0"
+        "version": "3.4.0"
       },
       "policy": {
         "installation": "AVAILABLE",

CHANGELOG.md

@@ -4,6 +4,28 @@ All notable public changes to Team First Development are documented here.
 
 ## Unreleased
 
+## 3.4.0 - 2026-08-05
+
+- Make the Coordinator decompose a `TEAM` outcome into the minimum useful
+  workstreams and map each one to exactly one accountable selected member.
+- Include the session-only workstream map, write scopes, dependencies,
+  handoffs, and parallel or serial order in the exact confirmation proposal.
+- Allow only the Coordinator to activate members; prohibit member
+  re-delegation and unconfirmed helper Agents.
+- Run only dependency-free, non-overlapping workstreams in parallel, stop
+  dependent work after a `BLOCKER`, and integrate accepted outputs into one
+  immutable candidate before review.
+
+## 3.3.0 - 2026-08-01
+
+- Add one progressively loaded engineering contract for every source-code or
+  architecture change, including `SOLO` work.
+- Require one concern owner, inward dependencies, fake or in-memory unit-test
+  seams, one authoritative capability implementation, add/remove feature
+  units, one canonical paradigm, current callers, and current-need minimalism.
+- Scale evidence depth with risk while retaining `PASS`, `BLOCKER`, and
+  `UNVERIFIED` as the exact review verdicts.
+
 ## 3.2.0 - 2026-07-31
 
 - Add an exact per-member Runtime binding with `codex_spawn`,

README-CN.md

@@ -7,8 +7,8 @@
 Team First Development（TFD）是一套选择性使用的 Codex 团队开发方法。它通过
 目标对齐、模型与职责匹配、聚焦上下文和独立审核，改善一个边界明确的开发结果。
 
-源码树当前是本地 `3.3.0` 候选；当前已发布版本仍是 `3.2.0`。本地检出本身不能
-证明已经安装、部署或发布。
+当前源码版本为 `3.4.0`。是否已发布以 `v3.4.0` 标签和 GitHub Release 为准；
+本地检出本身不能证明已经安装、部署或发布。
 
 ## 使用
 
@@ -22,6 +22,16 @@ TFD 首先判断协作收益是否高于协调成本。简单任务由单 Agent
 `.tfd/`。当任务包含可分离的专业职责，或风险确实要求独立审核时，才考虑使用
 项目已配置的团队。
 
+## Coordinator workstream
+
+对于 `TEAM`，Coordinator 在激活成员前把有界目标拆成最少且有用的
+workstream。精确确认方案必须展示每个 workstream 的责任成员、验收条件、写入
+范围、依赖、交接，以及并行或串行顺序。
+
+只有 Coordinator 可以激活成员；成员不能继续委派，也不能创建未经确认的辅助
+Agent。只有无依赖且写入范围不重叠的 workstream 才可并行；`BLOCKER` 会停止
+下游，Coordinator 最后把已接受的产出整合成一个不可变审核候选。
+
 ## 工程合同
 
 凡是修改源码或软件架构的任务，TFD 都必须在最终确定 `PLAN` 前完整读取
@@ -200,7 +210,7 @@ Wiki 存在后，最终交付只记录一个 `delivery` activity，不再创建
 推送、打标签、发布、部署、对外消息、破坏性清理、特权命令、付费动作或扩大
 范围；这些动作继续遵循各自的正常审批边界。
 
-本地检出目录中的版本号本身不能证明已经安装或部署。请以 `v3.2.0` 标签和
+本地检出目录中的版本号本身不能证明已经安装或部署。请以 `v3.4.0` 标签和
 GitHub Release 作为发布证据。
 
 ## 仓库结构

README.md

@@ -8,8 +8,8 @@ Team First Development (TFD) is a selective Codex team-development method.
 It improves a bounded development result through alignment, model-role fit,
 focused context, and independent review.
 
-The source tree is a local `3.3.0` candidate. The current published release
-remains `3.2.0`. A local checkout does not by itself prove installation,
+This source tree is version `3.4.0`. The `v3.4.0` tag and GitHub Release are
+the publication evidence; a local checkout alone does not prove installation,
 deployment, or publication.
 
 ## Use
@@ -25,6 +25,18 @@ Simple work stays with one Agent and does not read or write `.tfd/`. Work with
 separable professional responsibilities, or enough risk to require an
 independent reviewer, may use a project-configured team.
 
+## Coordinator workstreams
+
+For `TEAM`, the Coordinator decomposes the bounded outcome into the minimum
+useful workstreams before activation. The exact confirmation proposal shows
+each workstream's accountable member, acceptance conditions, write scope,
+dependencies, handoff, and parallel or serial order.
+
+Only the Coordinator activates members. Members do not re-delegate or create
+unconfirmed helper Agents. Dependency-free workstreams may run in parallel only
+when their write scopes do not overlap; a blocker stops its dependents, and the
+Coordinator integrates accepted outputs into one immutable review candidate.
+
 ## Engineering contract
 
 For every source-code or architecture change, TFD reads
@@ -235,7 +247,7 @@ commands, paid actions, or scope expansion. Each keeps its normal approval
 boundary.
 
 A version in a local checkout does not by itself prove installation or
-deployment. Use the `v3.2.0` tag and GitHub Release as publication evidence.
+deployment. Use the `v3.4.0` tag and GitHub Release as publication evidence.
 
 ## Repository layout
 

plugins/tfd/.codex-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "tfd",
-  "version": "3.3.0",
-  "description": "Session-first development with YAML team profiles, member-selected Codex Runtimes, a progressively loaded engineering contract, and a per-team Markdown Team Wiki.",
+  "version": "3.4.0",
+  "description": "Session-first development with Coordinator-decomposed workstreams, YAML team profiles, member-selected Codex Runtimes, a progressively loaded engineering contract, and a per-team Markdown Team Wiki.",
   "author": {
     "name": "Howe829",
     "url": "https://github.com/Howe829"
@@ -13,8 +13,8 @@
   "skills": "./skills/",
   "interface": {
     "displayName": "Team First Development",
-    "shortDescription": "按需求从 YAML 配置组建最小团队",
-    "longDescription": "Route simple work to one Agent, or select one configured YAML team and its minimum useful members with exact Codex Runtime bindings; apply one progressively loaded engineering contract to code changes; and retain session-scoped delivery, independent review, and a Git-native per-team Markdown Team Wiki.",
+    "shortDescription": "按需求拆分 workstream 并组建最小团队",
+    "longDescription": "Route simple work to one Agent, or decompose TEAM work into confirmed workstreams assigned to the minimum configured members with exact Codex Runtime bindings; apply one progressively loaded engineering contract to code changes; and retain session-scoped delivery, independent review, and a Git-native per-team Markdown Team Wiki.",
     "developerName": "Howe829",
     "category": "Developer Tools",
     "capabilities": ["Interactive", "Write"],

plugins/tfd/scripts/test_tfd_skill_contract.py

@@ -141,6 +141,27 @@ def test_skill_confirms_runtime_binding_without_fallback(self) -> None:
             with self.subTest(clause=clause):
                 self.assertIn(clause, skill)
 
+    def test_coordinator_decomposes_and_dispatches_confirmed_workstreams(
+        self,
+    ) -> None:
+        skill = _squash_whitespace(
+            SKILL_PATH.read_text(encoding="utf-8")
+        )
+        for clause in (
+            "minimum useful workstreams",
+            "exactly one accountable selected member",
+            "spawning per microtask",
+            "workstream map",
+            "write scope",
+            "dependency-free workstreams",
+            "Only the Coordinator activates",
+            "must not re-delegate",
+            "stops its dependent workstreams",
+            "one integrated candidate",
+        ):
+            with self.subTest(clause=clause):
+                self.assertIn(clause, skill)
+
     def test_team_wiki_reference_is_packaged_and_routed_on_demand(self) -> None:
         self.assertTrue(WIKI_REFERENCE_PATH.is_file())
         skill = SKILL_PATH.read_text(encoding="utf-8")
@@ -258,11 +279,20 @@ def test_wiki_protocol_keeps_v1_and_safety_boundaries_explicit(self) -> None:
             with self.subTest(clause=clause):
                 self.assertIn(clause, protocol)
 
-    def test_agent_metadata_mentions_wiki_confirmation_boundary(self) -> None:
+    def test_agent_metadata_matches_confirmation_and_dispatch_boundaries(
+        self,
+    ) -> None:
         metadata = yaml.safe_load(AGENT_METADATA_PATH.read_text(encoding="utf-8"))
         prompt = metadata["interface"]["default_prompt"]
-        self.assertIn("per-team Wiki", prompt)
-        self.assertIn("exact proposal confirmation", prompt)
+        for clause in (
+            "$using-tfd",
+            "workstream map",
+            "dispatch only confirmed members",
+            "per-team Wiki",
+            "exact proposal confirmation",
+        ):
+            with self.subTest(clause=clause):
+                self.assertIn(clause, prompt)
 
     def test_example_team_graph_is_valid(self) -> None:
         manifest = yaml.safe_load(

plugins/tfd/skills/using-tfd/SKILL.md

@@ -40,6 +40,11 @@ State a lightweight development plan with:
 - separable responsibilities;
 - verification and independent-review needs.
 
+For `TEAM`, decompose the bounded outcome into the minimum useful workstreams.
+Give each a distinct result or evidence obligation; combine related work instead
+of spawning per microtask. Declare dependencies and whether independent work
+may run in parallel.
+
 After the required team confirmation, normal reversible work inside the
 confirmed scope needs no repeated TFD approval. Deployment, publication, push,
 external messages, destructive changes, paid resources, privileges, and scope
@@ -68,6 +73,9 @@ one configured team whose purpose fits the plan, then the minimum member subset
 whose responsibilities cover it. Never combine teams for one requirement. A
 recurring cross-functional composition must be its own configured team.
 
+Map each workstream to exactly one accountable selected member; each active
+member owns one workstream. Do not select a member without current work.
+
 For project setup, draft the same manifest, team, and member structure from the
 plan, but do not create or update `.tfd` before `CONFIRM`.
 
@@ -115,6 +123,9 @@ containing:
 - exact Runtime and model, explicit reasoning effort or the Runtime/model
   default, available eligibility evidence and its source, and the Runtime's
   user-visible behavior;
+- the session-only workstream map: outcome and acceptance, accountable member,
+  allowed write scope, dependencies, output and handoff, and parallel or serial
+  order;
 - the minimum active subset, including any independent reviewer.
 
 `codex_spawn` creates a child Agent in the current task. `codex_thread` creates
@@ -132,9 +143,9 @@ when both actions are named in the same proposal. Any material change to any
 proposal field invalidates the confirmation and requires a new proposal,
 including a changed outcome, acceptance condition, scope, exclusion, action
 mode, team identity or purpose, member identity, responsibility, output, model,
-Runtime, reasoning effort, Skill, active subset, or reviewer. Confirmation
-authorizes only the named local actions; all separate approval gates remain in
-force.
+Runtime, reasoning effort, Skill, active subset, workstream map, order, or
+reviewer. Confirmation authorizes only the named local actions; all separate
+approval gates remain in force.
 
 ## TEAM WIKI
 
@@ -157,7 +168,7 @@ work, and audit-record statuses distinct.
 For profile-only setup, write exactly the confirmed profiles and stop without
 creating members. After confirmation, start each selected member once through
 its exact Runtime, model, and reasoning effort. Give each member a focused brief
-containing:
+for its confirmed workstream containing:
 
 - shared outcome and acceptance conditions;
 - its configured responsibility and expected output;
@@ -166,6 +177,17 @@ containing:
 - its configured Skills as the required working method;
 - required verification and next handoff.
 
+Only the Coordinator activates members and dispatches confirmed workstreams.
+Members must not re-delegate or create unconfirmed Agents. Start dependency-free
+workstreams in parallel only when their write scopes do not overlap and Runtime
+capacity is available; otherwise sequence them.
+
+Validate each handoff against its acceptance conditions before releasing its
+dependents. A `BLOCKER` stops its dependent workstreams, and `UNVERIFIED`
+evidence remains unresolved. Integrate accepted outputs into one integrated
+candidate, run whole-candidate verification, then route its immutable reference
+to review. Member self-report alone is not delivery.
+
 Do not forward unrelated project context, secrets, credentials, full
 conversations, or hidden reasoning. A Skill list scopes the brief; it does not
 prove the host hides other Skills or provides operating-system isolation.
@@ -178,9 +200,9 @@ and verify explicit reasoning effort when the Runtime exposes it.
 Missing proof remains `UNVERIFIED`; startup failure or a mismatch cannot become
 successful delivery.
 
-Do not automatically retry, switch Runtime, substitute a model, or reduce
-reasoning effort. A user-requested retry of the same unchanged binding does not
-require a new member proposal; any binding change does.
+Do not automatically retry or reassign work, switch Runtime, substitute a model,
+or reduce reasoning effort. A user-requested retry of the same unchanged binding
+does not require a new member proposal; any binding change does.
 
 Runtime-owned tasks, sessions, and logs remain Runtime-owned. Do not copy them
 into `.tfd` or automatically delete or archive them.

plugins/tfd/skills/using-tfd/agents/openai.yaml

@@ -1,4 +1,4 @@
 interface:
   display_name: "TFD"
   short_description: "Suitability-first team orchestration for development"
-  default_prompt: "Start by assessing whether TFD has a credible net benefit for this task. Then follow the single TFD Skill and preserve its exact-team confirmation gate, per-team Wiki exact proposal confirmation, session-only execution, focused briefs, independent review, evidence boundaries, and separate approval gates."
+  default_prompt: "Use $using-tfd to assess suitability, confirm the exact roster and session-only workstream map, dispatch only confirmed members, integrate one candidate, and preserve the per-team Wiki exact proposal confirmation, independent review, evidence boundaries, and separate approval gates."

scripts/test_plugin_contract.py

@@ -57,19 +57,30 @@ def test_manifest_points_to_the_single_skill_package(self) -> None:
         self.assertEqual(manifest["skills"], "./skills/")
         self.assertEqual(skill_dirs, ["using-tfd"])
 
-    def test_candidate_metadata_describes_all_tfd_capabilities(self) -> None:
+    def test_release_metadata_describes_all_tfd_capabilities(self) -> None:
         manifest = json.loads(
             (PLUGIN_ROOT / ".codex-plugin" / "plugin.json").read_text(
                 encoding="utf-8"
             )
         )
-        self.assertEqual(manifest["version"], "3.3.0")
+        self.assertEqual(manifest["version"], "3.4.0")
+        marketplace = json.loads(
+            (ROOT / ".agents" / "plugins" / "marketplace.json").read_text(
+                encoding="utf-8"
+            )
+        )
+        self.assertEqual(
+            marketplace["plugins"][0]["source"]["version"],
+            manifest["version"],
+        )
         self.assertIn("YAML", manifest["description"])
         self.assertIn("Runtimes", manifest["description"])
         self.assertIn("Team Wiki", manifest["description"])
+        self.assertIn("workstreams", manifest["description"])
         self.assertIn("engineering contract", manifest["description"].lower())
         self.assertIn("Runtime", manifest["interface"]["longDescription"])
         self.assertIn("Team Wiki", manifest["interface"]["longDescription"])
+        self.assertIn("workstreams", manifest["interface"]["longDescription"])
         self.assertIn(
             "engineering contract",
             manifest["interface"]["longDescription"].lower(),
@@ -161,26 +172,27 @@ def test_readmes_document_member_runtime_contract(self) -> None:
                 with self.subTest(path=path.name, clause=clause):
                     self.assertIn(clause, content)
 
-    def test_readmes_route_code_changes_to_engineering_contract(self) -> None:
+    def test_readmes_document_release_and_engineering_contract(self) -> None:
         expectations = {
             "README.md": (
-                "candidate",
-                "published",
+                "publication evidence",
+                "Coordinator workstreams",
                 "rules remain fixed",
                 "evidence depth scales with risk",
             ),
             "README-CN.md": (
-                "候选",
-                "已发布",
+                "是否已发布",
+                "Coordinator workstream",
                 "规则保持不变",
                 "证据深度按风险",
             ),
         }
         for filename, localized in expectations.items():
             content = (ROOT / filename).read_text(encoding="utf-8")
             for clause in (
-                "3.3.0",
-                "3.2.0",
+                "3.4.0",
+                "v3.4.0",
+                "workstream",
                 "references/engineering-constraints.md",
                 "`SOLO`",
                 "`PLAN`",