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.
WCAG/ARIA conformance as a cross-cutting practice spanning design and code. Semantic structure, focus management, color contrast, keyboard navigation, screen-reader expectations, automated checks (axe), manual testing protocol, CI gate on regressions. Applied at design time (UX Designer), at code time (FE Developer)…
Standardize how every significant architectural and engineering decision is recorded as an Architecture Decision Record (ADR) — context, options considered, decision taken, consequences, rejected alternatives. Use whenever a non-trivial decision is being made that future readers will need to understand (architecture…
Macro-design for LLM-powered features and agent systems. Choose between single-agent / multi-agent / planner-executor / supervisor topologies; design tool-use surfaces and tool schemas; choose memory systems (short-term / episodic / semantic / shared); place LLM calls relative to deterministic logic; decide when to…
Design and run swappable agentic-harness workflows where roles such as creator, reviewer, enhancer, and arbiter are bound at runtime to Claude, Codex, Gemini, Cursor, OpenCode, or custom harnesses. Use for iterative artifact refinement, cross-harness critique loops, convergence checks, and harness adapter contracts.
Contract-first API design. Produces the API specification (OpenAPI 3.1 for REST, .proto for gRPC, AsyncAPI for events) BEFORE implementation begins, with explicit versioning, pagination, idempotency, error model, and deprecation policy. The Solution Architect runs this for any slice that introduces or changes an API…
Keep architecture documentation alive — not a snapshot that ages into archaeology. C4 model at four levels (context / container / component / code) at the right level of fidelity per level; ADR archive maintained as the immutable decision trail; system-context maps; trust boundaries; data flows; "you-are-here"…
Choose the macro-architecture for a project from the requirements + NFR register + team composition + scale targets. Modular monolith, microservices, event-driven, serverless, layered/hexagonal — each has trade-offs and a sweet spot. Defaults to the simplest pattern that meets the NFRs — KISS/YAGNI applied to…
The drive protocol the Delivery Lead executes inside each drive iteration — read the task ledger, complete exactly one drive-eligible task against its named context, run its verify, and honor the non-negotiable stops. Use when a drive session (via /drive or scripts/praxis-drive.sh) starts or resumes, when deciding…
★not rated 7 todayA158 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: