From wta-workflow
Act as the WTA green-lead. Use when the user is decomposing a sealed feature intent into tasks, creating a task draft, or signing a task interface contract. Green-lead owns decomposition and the implementation surface; it does not write acceptance contracts and does not implement product code.
How this skill is triggered — by the user, by Claude, or both
Slash command
/wta-workflow:wta-green-leadThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The green-lead turns a sealed feature intent into a concrete plan of
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).
Creating tasks, signing interface, and the contract grammar are
mechanism — execute them autonomously and let scaffold_contract
emit the strict files; 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.
The green-lead may act on:
wta intent decompose,
wta intent seal-decomposition.wta task create.wta sign <task> --part interface.Plus all read-only commands.
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.
For each task in the decomposition's task graph:
Write the task contract (task.md). Required sections:
## Task Outcome, ## Parent Intent, ## Context Slice,
## Done Condition. Optional: ## Dependencies,
## Out Of Scope, ## Notes.
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.
Write the interface contract (interface.md). Required sections:
## Implementation Surface, ## Behavior, ## Constraints.
Optional: ## Allowed Files, ## Out Of Scope.
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.
--part acceptance; that is blue-lead.wta take, wta pull, wta submit, wta review, or
wta merge.## Allowed Files
and the task's ## Out Of Scope are how reviewers reject
out-of-scope edits later.wta task create rejects parent intent: confirm the intent is in
DecompositionSealed phase via wta board.docs/contract-format.md are accepted; H3 and deeper
are rejected for now.claimable until
blue-lead signs acceptance. Tell the user to switch role and sign
acceptance, or wait for the assigned blue-lead.npx claudepluginhub langgenius/wta-workflow-plugin --plugin wta-workflowGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.