Using Praxis
You have Praxis.
Triage
One line before every response:
praxis: scope=<x>, loading=<skills>
| scope |
signal |
load |
| vague |
problem space undefined — can't yet say what to build, for whom, or whether it's worth building |
design |
| trivial |
typo, rename, docs-only, <=1-line, pure Q |
none |
| small |
one function, single file, <=50 LOC, or test-only change |
tdd (intent unclear? clarify first) |
| standard |
feature or source-code change |
design, plan, tdd, review |
| complex |
new system, >=5 tasks, or parallel edits |
design, plan, worktree, subagents, review, ship |
| debug |
broken, regression, failing test |
debug |
| onboard |
existing project, no docs/tech-spec.md |
onboard |
If multiple scopes fit, choose the smaller one. vague is a last resort — if you can name a rough deliverable, use a lower scope instead. feature change = user-visible/public-contract change. source code = code/schema/config that changes shipped behavior; docs, tests, examples, CI, and tooling excluded.
Rule
- Unfamiliar with this project? Read
docs/tech-spec.md first.
- Classify inline using the table above — no Skill call needed for triage.
- Announce:
praxis: scope=<x>, loading=<skills>
- Load all required skills in parallel (single response, multiple Skill tool calls):
praxis:<name>, or in file-read harnesses from skills/<name>/SKILL.md.
- Follow loaded skills literally; respect
<gate> markers.
Source: hashgraph-online/awesome-codex-plugins → plugins/ouonet/praxis/skills/using-praxis/SKILL.md
1---2name: using-praxis3description: Use at session start to learn how Praxis skills are invoked and why triage runs before every task.4---5
6# Using Praxis
7
8You have Praxis.
9
10<EXTREMELY_IMPORTANT>
11Before any response or action on every user message, classify scope using the triage table below, announce it, then load required skills in parallel.
12</EXTREMELY_IMPORTANT>
13
14## Triage
15
16One line before every response:
17```
18praxis: scope=<x>, loading=<skills>
19```
20
21| scope | signal | load |
22|---|---|---|
23| vague | problem space undefined — can't yet say what to build, for whom, or whether it's worth building | `design` |
24| trivial | typo, rename, docs-only, <=1-line, pure Q | none |
25| small | one function, single file, <=50 LOC, or test-only change | `tdd` (intent unclear? clarify first) |
26| standard | feature or source-code change | `design`, `plan`, `tdd`, `review` |
27| complex | new system, >=5 tasks, or parallel edits | `design`, `plan`, `worktree`, `subagents`, `review`, `ship` |
28| debug | broken, regression, failing test | `debug` |
29| onboard | existing project, no docs/tech-spec.md | `onboard` |
30
31If multiple scopes fit, choose the smaller one. `vague` is a last resort — if you can name a rough deliverable, use a lower scope instead. `feature change` = user-visible/public-contract change. `source code` = code/schema/config that changes shipped behavior; docs, tests, examples, CI, and tooling excluded.
32
33## Rule
34
350. Unfamiliar with this project? Read `docs/tech-spec.md` first.
361. Classify inline using the table above — no Skill call needed for triage.
372. Announce: `praxis: scope=<x>, loading=<skills>`
383. Load all required skills **in parallel** (single response, multiple Skill tool calls): `praxis:<name>`, or in file-read harnesses from `skills/<name>/SKILL.md`.
394. Follow loaded skills literally; respect `<gate>` markers.
40
41---
42
43**Source:** [`hashgraph-online/awesome-codex-plugins`](https://github.com/hashgraph-online/awesome-codex-plugins) → `plugins/ouonet/praxis/skills/using-praxis/SKILL.md`
thedixitjain