WS Claude Marketplace

What it makes possible.

Developers and engineering teams using Claude Code or omp; particularly teams coordinating consistent project conventions across repositories.

Install shared engineering conventions for a single repository, then adopt an optional project hub when work spans multiple repositories.

/ws-setup configures repository policy, tracker selection, documentation and migrations.
/ws-matt links idea review, specifications, tickets, implementation, TDD and code review.
/ws-docs supports user docs, internal architecture records, changelogs, release notes and optional Outline publishing.
/ws-commit and /ws-status use project policy for commits, pull requests and optional Jira behavior.
/ws-hub registers related repositories and supports shared project context and documentation.
A generated TypeScript package supplies the shared suite plus runtime guards, dashboard context and structured tools.

Claude Code CLI and Git with GitHub SSH access for the documented Claude installation.
tea is needed for Gitea pull-request flows; jira-cli is needed when Jira behavior is selected.
Outline publishing requires Python 3 and an Outline token.
Add the marketplace, install its single ws plugin, then run /ws-setup inside the target repository.
Use /ws-help for orientation and /ws-matt grill to develop an idea.
omp users follow the separate native @wsagency/omp-ws package instructions.

Third-party integrations need their own CLI configuration and account credentials.
The omp instructions say not to install the native package together with ws@ws-marketplace in omp, because this loads the suite twice.
Legacy sibling-path hub repositories are not reachable in omp; the documented layout nests repositories inside the hub.
The native omp package license metadata differs from the repository root license.

Based on public project documentation and source, checked 7 September 2026. Refer to the repository for changes since then.