메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| 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 |
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.
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.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.
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.
To upgrade to the latest commit:
cd /path/to/wta-workflow
git pull --ff-only
cargo install --path . --locked --force
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.WTA is now available as wta. The next step depends on the user's
goal:
wta-using-wta skill.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.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.
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.
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.
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.
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.
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).