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 / Cowork: use the extension and role ZIP path below. Desktop installation does not connect your CLI automatically.
- Local source workflow: authorized source, vendored dependencies and source-tool prerequisites; Jira is not required for that separate recipe.
Runtime/Jira Desktop workflow needs
- Claude Desktop with Cowork (local folder / computer use) on the computer that holds the product repository
- 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)
- The Praxis release artifacts listed on Installation
You do not need (ordinary Desktop install)
- Node.js, npm, Make, Docker, or SQLite
- Editing Praxis source
launchctl setenv- A repository
.envfile - 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.