The mobile specialist — implements user-facing slices as a native mobile app against the active mobile stack (stack-flutter). Consumes engineering-standards, stack-flutter, frontend-design (visual craft — the same anti-generic discipline as web), api-design (client-side contract consumption), accessibility…
The phase lead who owns the deployment plane AND the operational plane — CI/CD pipelines, infrastructure (IaC), containers, environments, deployments, secrets, capacity sizing, reliability + DR, observability operations, chaos engineering, cost-finops, and incident response. Stands up the pipeline, provisions infra…
The Phase A lead — owns product discovery and requirements through the requirementsfreeze gate. Runs product-discovery, user-research, requirements-elicitation, requirements-interrogation, and nfr-definition. Produces the opportunity brief, JTBD framing, success metrics, user stories with acceptance criteria…
The Phase B lead — owns technical design from requirementsfreeze through architecturesignoff. Runs architecture-pattern-selection, distributed-systems decisions, ADR authoring via adr-decision-records, project-phasing for the executable roadmap, and architecture-documentation. Produces the architecture decision, C4…
The 16th and final agent — the cross-cutting role that watches the Praxis itself and proposes evidence-based improvements. Activated cross-project (not per project); operates on quarterly cadence consuming factory-evaluation reports. Owns the skill lifecycle (experimental → active → deprecated → merged|removed)…
The documentation and maintenance specialist. Leads brownfield comprehension (running codebase-comprehension and impact-analysis), keeps documentation living (architecture-documentation, technical-documentation), and runs the maintenance disciplines (legacy-modernization, tech-debt-management). Use whenever brownfield…
The Phase B+ lead — owns user experience design from requirementsfreeze through the architecturesignoff gate (parallel with the Solution Architect). Runs ux-journey-mapping, wireframing-prototyping, user-research (when needed), and design-system extension. Produces journey maps, wireframes, interactive prototypes…
TOMBSTONE — This SKILL was consolidated into using-praxis in the Polish-1 pass. Its content (workflow execution model, step types, Decision Node evaluation, gate enforcement runtime, workflow lifecycle state machine) lives there under "LAYER 2 — Orchestration Runtime". Do not load this SKILL; do not depend on it; do…
Routes tasks to the right reasoning-effort tier (high / medium / low — the Codex resolution of Praxis capability tiers deep / standard / light per governance/model-routing.yaml) based on task complexity, novelty, stakes, and interdependency. Prevents wasteful high-reasoning consumption on tasks medium handles equally…
Use when starting or resuming an autonomous drive run in Codex — iterating the active task ledger unattended or in-session. Triggers on "praxis drive", "keep going autonomously", "run this without me", or resuming a paused drive session.
Use when the user wants to record a rich factory-metrics observation for steward review — "record what we learned", "capture an observation", "factory record", "log this for the steward". Codex analogue of Claude Code's /factory-record.
Use when a new requirement arrives in steady state (story, epic, ticket, stakeholder ask, or change request) after the initial discover/architect rounds are done. The single front door — triage, right-size, and route it via requirements-intake so the user never picks a workflow by hand. Triggers on "new story", "new…
Use when refining an ideation artifact (concept note, PRD draft, proposal, roadmap sketch) in Codex through the bounded creator/reviewer/enhancer/arbiter loop before it enters formal discovery.
Use when running one Praxis implementation slice in Codex. ALWAYS launches delivery-lead as the orchestrator session; never launches specialists directly. Follows implementation-slice.yaml with subagents, review gates, QA, and closeout.