Praxis

Appearance

First run ​

First finish installation (marketplace first; CLI setup is the terminal alternative). Confirm both Runtime connection and your chosen role before starting work.

The Cowork steps below apply to Desktop. In Claude Code and Desktop Code, launch from the selected repository with the Praxis plugins installed, then use the same read-only checks. In Desktop Chat the Runtime comes from the MCPB.

1. Start Cowork ​

  1. Open Cowork in Claude Desktop.
  2. Turn Only on this computer / local computer access ON (wording varies by build). Developer and Quality cannot implement or re-test without local execution.
  3. New session (do this after installing or updating extensions).
  4. Choose the shared product documentation folder for BA/Architect or the code checkout for Developer. For a separate canon/code layout, make the required canon and design files available explicitly; see repository boundaries.

2. Infer .project if missing ​

If the folder has no .project, the Skill runs praxis_project_init_preview, shows inferred YAML, and waits. Applying it is a protected action: it runs only after your client's own approval dialog approves it, and nothing is written if it is rejected or if your client has no dialog Praxis can use (APPROVAL_CLIENT_UI_REQUIRED). In Claude Desktop (Cowork, Chat and the Code tab) it is not written: Claude shows the preview and says it was not applied. Apply it from the Claude Code CLI in a terminal, in the same folder. See Approvals.

Do not hand-write .project unless you are an advanced user. Secrets do not belong there. See Configuration.

3. Confirm Runtime ​

Ask the role Skill to run doctor/status, or paste a read-only prompt.

Success looks like:

  • Runtime tools available (praxis_doctor)
  • Jira flags configured (base URL / email / project / token present, values not printed)
  • Repository path is the folder you selected

Failure codes: Troubleshooting.

4. Start a role workflow ​

Pick one Skill:

  • BA: Jira Epic Analysis
  • Architect: Plan Jira Epic / Materialize Work Package
  • Developer: Implement Work Package / Developer Status
  • Quality Harness, with its authorized role package: Review Work Package / Quality Status

Example (read-only):

Inspect Epic PRX-1 and show BA status.
Study the requirements and existing Stories first.
Do not create anything in Jira automatically.

Then follow Approvals. Neither the agent's confirmation=YES nor a “yes” in chat approves anything: protected actions run only after the client's own approval dialog, which Claude Desktop does not provide.

Quality Harness review is separate from approved application and delivery. The private future Quality Platform is not installed by this first-run flow.