Requirements

Choose your environment

• Claude Code CLI: installed and authenticated Claude Code, Node.js 20+, authorized role distribution, and Runtime connection when using the Jira Skills.
• Claude Desktop Code / Cowork / Claude Code: install the praxis plugin from the marketplace; the Runtime comes with it. Node.js 20+ is needed on that computer.
• Claude Desktop Chat: a plugin's local server is not a Chat tool, so install the separate praxis-runtime.mcpb extension.
• Local source workflow: authorized source, vendored dependencies and source-tool prerequisites; Jira is not required for that separate recipe.

What you need

• Claude with plugin support: Claude Code (CLI 2.1.278 or later), Claude Desktop Code, or Cowork, on the computer that holds the project folder
• A project folder you can read and write

Optional (Jira workflow)

• A Jira Cloud site you can read (and, for apply workflows, write) in the target project
• A Jira API token for your Atlassian account (how to get one)
• A GitHub or GitLab token, only for pull/merge requests and CI status

Local workflows work without any of these.

You do not need (ordinary Desktop install)

• npm install, Make, Docker, or SQLite
• Administrator rights, a background service, an installer package or a hardware key
• Editing Praxis source
• launchctl setenv
• A repository .env file
• Installing all role plugins
• A separate Runtime per role

Supported Jira

Praxis Cloud authentication uses Atlassian account email + API token (jira_email + jira_token) against a site such as https://example.atlassian.net.

Do not put the password for your Atlassian account in jira_token. Do not put a Data Center personal access token into the Cloud token field.

Working folders

Role	Working folder and access
BA	Shared product documentation repository; approved requirements and initial package writes.
Architect	The same shared product repository; linked BA inputs and technical package writes.
Developer	Code checkout plus prepared package access; code/tests and execution evidence.
Quality Harness	Selected work result, its handoff and evidence; review and separately approved apply.

Runtime resolves local inputs in the selected repo; prepare required design and manifest artifacts there explicitly when product and code live in separate repositories. A Jira link alone is insufficient. The source-tool workflow supports separate design/code roots and writes reports under the selected design directory. See repository boundaries.

Choose one role's authorized package. Quality Harness and the private future Quality Platform have separate access and licensing; neither requires every teammate to install all roles.