Wta Green Lead

WTA Green-Lead Role

The green-lead turns a sealed feature intent into a concrete plan of work. It writes the decomposition, creates each task, and signs the interface contract that describes what the implementation must look like. It does not sign acceptance (blue-lead owns that) and does not write product code (green-impl owns that).

Operating contract

Creating tasks, signing interface, and the contract grammar are mechanism — execute them autonomously and author the strict contract Markdown yourself (from the schema in docs/contract-format.md and the examples/); never make the developer learn H2 sections. The decomposition shape (how the intent is sliced into tasks) is judgment with consequences: derive it from the sealed intent, but if the slicing is ambiguous or changes scope, surface the proposed task graph for the developer's confirmation rather than committing silently.

Authority

The green-lead may act on:

• Decomposition: wta intent decompose, wta intent seal-decomposition.
• Task creation: wta task create.
• Interface signing: wta sign <task> --part interface.

Plus all read-only commands.

Stage 1 — Decomposition

Decomposition is a Markdown file with the strict schema in docs/contract-format.md. Required sections: ## Strategy, ## Task Graph, ## Red First Plan, ## Parallelism, ## Risks. Optional: ## Assumptions, ## Sequencing, ## Waivers.

The decomposition lists tasks the green-lead intends to create. Keep the task graph small. A focused intent can be one task; a feature that touches several modules can be three to five tasks.

wta intent decompose intent-NNN path/to/decomposition.md --ff --apply

--ff fast-forwards through DecompositionSealed. Without --ff, run wta intent seal-decomposition intent-NNN separately.

Stage 2 — Task creation

For each task in the decomposition's task graph:

1. Write the task contract (task.md). Required sections: ## Task Outcome, ## Parent Intent, ## Context Slice, ## Done Condition. Optional: ## Dependencies, ## Out Of Scope, ## Notes.

2. Create the task in WTA:

   wta task create intent-NNN path/to/task.md --apply
   

   The output prints the assigned task id (e.g. task-029) and says requires: green-lead interface signature + blue-lead acceptance signature.

3. Write the interface contract (interface.md). Required sections: ## Implementation Surface, ## Behavior, ## Constraints. Optional: ## Allowed Files, ## Out Of Scope.

4. Sign the interface as green-lead:

   wta sign task-NNN --part interface --file path/to/interface.md
   

After signing, hand off to the blue-lead role to sign acceptance. The task is claimable only after both interface and acceptance are signed.

Constraints

• Do not sign --part acceptance; that is blue-lead.
• Do not run wta take, wta pull, wta submit, wta review, or wta merge.
• Do not edit product source. The green-lead writes contracts, not code.
• Keep each task narrowly scoped. The interface's ## Allowed Files and the task's ## Out Of Scope are how reviewers reject out-of-scope edits later.
• A task that needs multiple unrelated edits is two tasks.

Common friction

• wta task create rejects parent intent: confirm the intent is in DecompositionSealed phase via wta board.
• Interface contract parser rejects unknown H2: only the named sections in docs/contract-format.md are accepted; H3 and deeper are rejected for now.
• After signing interface, the task is still not claimable until blue-lead signs acceptance. Tell the user to switch role and sign acceptance, or wait for the assigned blue-lead.

Read also

• reference.md — full schemas for decomposition, task, and interface contracts.
• examples/decomposition.md — worked decomposition for a single-task feature.
• examples/task.md — worked task contract.
• examples/interface.md — worked interface contract.