Praxis documentation

Praxis gives each software-delivery role a focused AI harness. Choose your responsibility first. The documentation will show what you receive, what decisions you own, what to say in a session, and what artifact proves the work is ready for the next person.

Install and configure with Claude

Copy this into Claude. It will check your setup, help install your role, and verify the next step.

Claude Code · CLIClaude Desktop · Cowork

Documentation: https://praxis.dfuture.co/docs/

Claude Code · CLI

Follow the installation guide

Set up Praxis for me in Claude Code CLI.

Read the CLI installation, role setup and repository-workflow guides at
https://praxis.dfuture.co/docs/. I work in a terminal: use the documented Claude Code
plugin and MCP setup, not Claude Desktop extension-import instructions.

Ask which role I need. Inspect my Claude Code version, installed plugins,
available MCP servers and working repositories. Reuse compatible components.
Install only my role and its required dependencies from verified release or
marketplace sources. Check the manifest names, installation scope and
compatibility; do not invent a public npm package or marketplace URL.

For Developer, identify the code checkout and the prepared Work Package in
our shared BA/Architect product repository. Explain the supported access or
preparation step and the evidence output directory. Do not assume Runtime
will import another repository automatically.

If this workflow uses Runtime, configure its documented CLI/MCP launch and
required integrations, then check the actual connection and available tools.
Keep secrets out of chat, committed files and command history. If I need a
local workflow without Jira, use the separately documented supported setup;
do not silently substitute source scripts for missing installed Skills.

Perform the supported setup steps, preserving unrelated configuration.
Tell me if a new session or plugin reload is needed. Run documented health
and role-status checks when available. Preview project initialization and
obtain its required approval before applying it. Do not begin product work,
create Jira items, commit, push or open a PR during setup.

Finish with installed versions, selected role, code/product paths, checks
that passed, any blockers, and the exact first-session prompt for my role.

Claude Desktop · Cowork

Follow the installation guide

Help me install and configure the right Praxis harness for my work.

First read the installation guide, requirements, first-run guide and role
setup instructions at https://praxis.dfuture.co/docs/. Use their current supported
installation method and release links. If you cannot access them, tell me
what is missing instead of guessing commands or package locations.

Ask which role I am working in: Business Analyst, Architect, Developer,
Quality, or a founder handling several roles. Check my operating system,
Claude environment and existing installation before changing anything.
Distinguish Claude Desktop/Cowork from Claude Code; do not apply instructions
for one environment to the other.

Identify my working folders. BA and Architect share the product documentation
repository. Developer works in the code repository and needs access to the
prepared Work Package. State which folder each tool will read and write.

Install only the components needed for my chosen role, using documented
releases and compatibility requirements. Reuse a compatible installation.
Perform supported steps you can execute; for Desktop imports or settings you
cannot control, guide me through the exact manual step and then verify it.
Do not claim installation succeeded until it has been checked.

Configure the required integrations. Have me enter tokens only in the
supported secure settings, never in this chat or a repository file.
Do not assume Quality Harness access includes the private Quality Platform.

Run the documented doctor/status checks if available. If project configuration
is missing, show the initialization preview and obtain the required approval
before applying it. Report missing access, dependencies or input artifacts.
Do not start implementation, create Jira work or publish Git changes as part
of setup.

Finish with a short checklist: installed components and versions, selected
role and repository, checks that passed, remaining blockers, and one prompt
I can use to begin my first session.

Install and operate your role

Start with Claude Code CLI setup if you work in a terminal. The Desktop path is one Runtime MCPB plus your role's skills-only ZIP. Start with installation, credentials, and first run. Quality Harness is a delivered role package, distinct from private Quality Platform access.

Already working? Use the prompt library, full tutorial, Git Delivery, or troubleshooting. For maintenance, see update and uninstall.

Bring an existing team

Use the existing-project adoption guide to migrate Confluence knowledge, establish what the code already implements, audit deviations with Quality, and take the first correction through your team. It includes role prompts, repository boundaries, and a baseline audit checklist.

Start with your role

I am…	My first question	Start here
A Business Analyst or Product Owner	How do I turn vision, feedback, bugs, and feature requests into versioned requirements?	Business Analyst playbook
An Architect or Engineering Director	Which ready requirements still need decisions and design, and how do I package them for development?	Architect playbook
A Developer	How do I accept one bounded package, plan it, implement it, and prove it works?	Developer playbook
A Quality or Engineering leader	How do I review one work result, inspect findings, and apply an approved outcome?	Quality Harness
A Founder doing several roles	How do I keep the responsibilities separate while I do all of them?	Connected team sessions

The lifecycle

flowchart TD
  C[Customer intent] --> BA[Business Analyst<br/>vision, CR, requirements]
  BA -->|approved WP + handoff| A[Architect<br/>decisions and design]
  A -->|context slice + change spec| D[Developer<br/>plan, code, evidence]
  D -->|completion evidence + handoff| Q[Quality Harness<br/>review and findings]
  Q -->|findings or accepted evidence| BA

Compatible artifacts connect separate role sessions. Inspect and prepare each handoff explicitly; local Runtime journals are not automatically committed. Review, approved application, and Git delivery are separate steps.

Understand the language first

• Method and core vocabulary explains canon, CR, FR, NFR, BR, WP, handoff, gate, ADR, context slice, evidence, baseline, and drift.
• Roles and ownership shows who may change which artifact.
• The RBPIV cycle explains Research, Brainstorm, Plan, Implement, and Verify.

Operate Praxis

• Install one harness per role
• Use role-specific sessions
• Understand repositories and handoffs
• Configure project context
• Use CLI, Runtime, and recovery tools

BA, Architect, and Developer harnesses are Apache-2.0. Quality Harness has its own distribution and license terms. The separate private Quality Platform is planned to track multiple projects and each project’s quality history. The local source workflow does not require Jira; current Runtime/Jira Skills have different prerequisites.