Run any Skill in Manus with one click

wta-install

Stars0

Forks0

UpdatedJune 20, 2026 at 10:14

Install the WTA Rust CLI from source. Clone the public repository, build with cargo, and place the wta binary on PATH. Use when the user wants to start using WTA but does not yet have the wta binary installed, or wants to upgrade to the latest commit on main.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

langgenius

langgenius/wta-workflow-plugin

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	wta-install
description	Install the WTA Rust CLI from source. Clone the public repository, build with cargo, and place the wta binary on PATH. Use when the user wants to start using WTA but does not yet have the wta binary installed, or wants to upgrade to the latest commit on main.
license	MIT

Install WTA

WTA is a Rust binary CLI distributed as source on GitHub. There is no crates.io publish or prebuilt binary today, so installation always goes through cargo build.

Prerequisites

Confirm the user has these before continuing. If any are missing, stop and explain what to install:

cargo and rustc (Rust 1.70 or newer). Check with rustc --version.
git with SSH or HTTPS access to GitHub.
A Unix-like shell. WTA is tested on macOS and Linux.

Verify the cargo bin directory is on PATH:

echo "$PATH" | tr ':' '\n' | grep -F "$HOME/.cargo/bin"

If the output is empty, instruct the user to add ~/.cargo/bin to their shell rc file (.zshrc, .bashrc, etc.) and re-source it before continuing.

Steps

Clone the public WTA source:

git clone https://github.com/langgenius/wta-workflow.git
cd wta-workflow

Build and install with cargo install:
```
cargo install --path . --locked
```
This compiles WTA in release mode and copies the resulting binary to ~/.cargo/bin/wta.
Verify the install:
```
wta --help
```
The output should list the WTA top-level commands (init, doctor, info, board, intent, task, release, ...). If wta is not found, return to the prerequisites step and check PATH.

Upgrading later

To upgrade to the latest commit:

cd /path/to/wta-workflow
git pull --ff-only
cargo install --path . --locked --force

Common failures

error: rustc 1.x is not supported — run rustup update stable.
error: failed to run custom build command — usually a missing system dependency (pkg-config, libssl-dev on Debian, etc.). Read the error and install the named library.
wta: command not found after install — the cargo bin directory is not on PATH. Re-read the cargo install output for the exact install location.
Permission denied (publickey) when cloning — use HTTPS instead of SSH for the clone, or run ssh-add to load the user's key.

After install

WTA is now available as wta. The next step depends on the user's goal:

To start operating an existing WTA project or set up a new one, load the wta-using-wta skill.
To create a new WTA project from scratch, run wta init --project NAME --ssh-host HOST inside an empty directory. Setup commands are dry-run/plan by default and apply only with --apply. Run wta next once a project is bound to see what to do.

More from this repository

same repository

wta-green-impl

langgenius/wta-workflow-plugin

Act as the WTA green-impl. Use when the user is claiming a contract-sealed task, pulling its worktree, implementing the task, running checks, and submitting for review. Green-impl is the only role that edits product source code; it must stay inside the task contract's allowed files.

2026-06-200

wta-green-lead

langgenius/wta-workflow-plugin

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.

2026-06-200

wta-orchestrator

langgenius/wta-workflow-plugin

Act as the WTA orchestrator. Use when the user is bootstrapping a WTA project, publishing or sealing a feature intent, registering team members or release targets, closing an intent, or running a release push. The orchestrator owns intent and release; it does not implement code or sign acceptance.

2026-06-200

wta-using-wta

langgenius/wta-workflow-plugin

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.

2026-06-200

wta-blue-harness

langgenius/wta-workflow-plugin

Act as the WTA blue-harness reviewer. Use when the user is reviewing a Delivered task by pulling a reviewer worktree, running the acceptance contract's Required Checks, and recording a verdict. Blue-harness is independent of green-impl; the same person should not implement and review the same task except in solo dogfood scenarios.

2026-05-190

wta-blue-lead

langgenius/wta-workflow-plugin

Act as the WTA blue-lead. Use when the user is signing a task acceptance contract, sealing a green-lead decomposition, or merging a Green-reviewed task into product main. Blue-lead is the gate that protects product main; it does not implement code and does not run the review checks itself (blue-harness does).

2026-05-190

name	wta-install
description	Install the WTA Rust CLI from source. Clone the public repository, build with cargo, and place the wta binary on PATH. Use when the user wants to start using WTA but does not yet have the wta binary installed, or wants to upgrade to the latest commit on main.
license	MIT

Install WTA

WTA is a Rust binary CLI distributed as source on GitHub. There is no crates.io publish or prebuilt binary today, so installation always goes through cargo build.

Prerequisites

Confirm the user has these before continuing. If any are missing, stop and explain what to install:

cargo and rustc (Rust 1.70 or newer). Check with rustc --version.
git with SSH or HTTPS access to GitHub.
A Unix-like shell. WTA is tested on macOS and Linux.

Verify the cargo bin directory is on PATH:

echo "$PATH" | tr ':' '\n' | grep -F "$HOME/.cargo/bin"

If the output is empty, instruct the user to add ~/.cargo/bin to their shell rc file (.zshrc, .bashrc, etc.) and re-source it before continuing.

Steps

Clone the public WTA source:

git clone https://github.com/langgenius/wta-workflow.git
cd wta-workflow

Build and install with cargo install:
```
cargo install --path . --locked
```
This compiles WTA in release mode and copies the resulting binary to ~/.cargo/bin/wta.
Verify the install:
```
wta --help
```
The output should list the WTA top-level commands (init, doctor, info, board, intent, task, release, ...). If wta is not found, return to the prerequisites step and check PATH.

Upgrading later

To upgrade to the latest commit:

cd /path/to/wta-workflow
git pull --ff-only
cargo install --path . --locked --force

Common failures

error: rustc 1.x is not supported — run rustup update stable.
error: failed to run custom build command — usually a missing system dependency (pkg-config, libssl-dev on Debian, etc.). Read the error and install the named library.
wta: command not found after install — the cargo bin directory is not on PATH. Re-read the cargo install output for the exact install location.
Permission denied (publickey) when cloning — use HTTPS instead of SSH for the clone, or run ssh-add to load the user's key.

After install

WTA is now available as wta. The next step depends on the user's goal:

To start operating an existing WTA project or set up a new one, load the wta-using-wta skill.
To create a new WTA project from scratch, run wta init --project NAME --ssh-host HOST inside an empty directory. Setup commands are dry-run/plan by default and apply only with --apply. Run wta next once a project is bound to see what to do.