| name | wta-using-wta |
| description | Operate WTA, the role-gated workflow controller for teams collaborating with humans and AI coding agents. Use when the user wants to set up a new WTA project, configure the SSH/VPS pair, register an identity, or follow the Blue-Green role lifecycle from intent through release. |
| license | MIT |
Using WTA
WTA is a CLI for teams that share a product repository with both
human engineers and AI coding agents. It records the intent of a
change, breaks it into role-gated tasks, and exports clean commits
back to the public repository, keeping a reviewable main branch
even under parallel agent work.
This skill is the entry point. It does not cover every command. Once
you are inside an active WTA project, run wta agent render and
read the role-scoped skills WTA generates for you (named like
wta-implementing-task, wta-reviewing-task, etc.) for stage-specific
guidance.
Operating contract (assisting agents)
You are assisting a developer, not replacing them. WTA's roles,
stages, identity switches, contract grammar, and pushes are
mechanism — the developer should not have to think about them. Your
job splits cleanly in two:
- Mechanism you may execute autonomously. Switching active role
to whatever a gate requires, running gated commands
(
take/pull/submit/review/merge/release), satisfying the
contract format (author the strict Markdown yourself from the schema
in docs/contract-format.md and the examples/; never make the
developer learn H2 sections), pushing artifact/product. Do these
without asking; they are reversible plumbing and the FSM enforces
correctness.
