Menü
Use at session start to learn how Praxis skills are invoked and why triage runs before every task.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Use at ship time to merge the spec into the living documentation, delete the staging spec and plan, and ask how to finish.
Use when taking over an existing codebase that has no living document. Produces a factual record of what already exists.
Use when all plan tasks are done and green to review, archive planning artifacts, and ask how to finish.
Use for standard or complex new work before coding or planning. Also handles vague goals — clarifies before designing.
Use when the goal is vague or vision-level and can't be defined well enough for design questions.
Use after design approval for milestone plans with executable acceptance.
Basierend auf der SOC-Berufsklassifikation
| name | using-praxis |
| description | Use at session start to learn how Praxis skills are invoked and why triage runs before every task. |
You have Praxis.
<EXTREMELY_IMPORTANT> Before any response or action on every user message, classify scope using the triage table below, announce it, then load required skills in parallel. </EXTREMELY_IMPORTANT>
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.
docs/tech-spec.md first.praxis: scope=<x>, loading=<skills>praxis:<name>, or in file-read harnesses from skills/<name>/SKILL.md.<gate> markers.