Role harnesses
Install one shared Runtime for the current Desktop workflow, then only the role ZIP each person needs. Install and understand plugin isolation.
Give each teammate the harness for the responsibility they own. The files below connect the roles; no teammate needs the previous role's plugin or chat history.
| Teammate | Installs | Works in |
|---|---|---|
| Business Analyst | BA harness | product canon repository |
| Architect | Architect harness | product canon repository |
| Developer | Developer harness | code repository plus explicit design-package path |
| Quality | Quality Harness | configured local review root and evidence |
Each role page is now both a skill reference and an operator playbook with copy-ready prompts for the work that role performs.
Praxis packages role-specific skills; the source repositories also contain broader tools. Installed ZIP contents vary by role and do not by themselves install every source executable. Each harness can be used for its supported workflow. Connected use preserves intent from request to quality evidence.
| Harness | Opens | Produces | Access |
|---|---|---|---|
| Business Analyst | customer request, existing product, Jira epic | canon, requirements, approved WP, Architect handoff | Apache-2.0 |
| Architect | BA handoff | decisions, contracts, NFR budgets, design package, Developer handoff | Apache-2.0 |
| Developer | Architect handoff or claimed Jira WP | approved plan, implementation, verification, Quality handoff | Apache-2.0 |
| Quality Harness | Prepared local WP, Developer evidence and design | Persisted review and findings; separately approved Apply | Quality Releases |
Use one harness
A BA can build a versioned requirements canon without the other roles. An Architect can audit and package a handoff. A Developer can enforce planning and verification. The output remains durable, so another person or a later session can continue.
Use the full lifecycle
The chain removes repeated interpretation:
request → requirement → decision → bounded plan → verified change → quality signalEach handoff has a contract; approval depends on the operation. The team shares artifacts rather than a single chat window.
Start with installation and bootstrap, then use the session recipes.
Source repositories
- GitHub · praxis-ba
- GitHub · praxis-architect
- GitHub · praxis-developer
- GitHub · praxis-quality
- GitHub · praxis-core
- GitHub · praxis-runtime
Quality Harness is public source. The separate Quality Platform is private and is not included in these repositories.