Skill Claude CodeCodex
Standalone three-axis code review of the diff between HEAD and a fixed point — Spec (does it implement the intent), Standards (does it follow the repo's documented conventions), Risk (is it safe in production, judged with a Principal Engineer mindset). Axes run as parallel subagents; findings stay separated per axis…
Skill Claude CodeCodex
Orchestrate the full feature delivery pipeline — Planning (/plan-product-spec → /plan-technical-spec → /plan-contract-spec → /plan-verification → /plan-ready) → Implement (/plan-implement) → Review (/impl-review) → QA (/qa-test) — with approval gates, resume, per-feature memory, and optional multi-model delegation…
Skill Claude CodeCodex
Holistic post-implementation review of the whole feature diff against Product/Technical/Contract Specs — spec compliance, correctness, security, tests, maintainability; writes review-report.md. Stage 7 of /development-workflow, after /plan-implement. Use when the user asks to review an implemented feature or invokes…
Skill Claude CodeCodex
Create or update contract-spec.md (REST/gRPC/Event contracts) from a Technical Spec. Stage 3 of /development-workflow, after /plan-technical-spec. Use when the user asks to define API or event contracts, write a contract spec, or invokes /plan-contract-spec.
Skill Claude CodeCodex
Execute an approved tasks.md task-by-task with tests, per-task reviewer PASS, and checkpoint gates; writes implementation-report.md. Stage 6 of /development-workflow, after /plan-ready. Use when the user asks to implement approved tasks, execute tasks.md, or invokes /plan-implement.
Skill Claude CodeCodex
Write a UX-centric Product Spec (feature/UX spec) from a feature idea, user problem, or goal — or from an APPROVED prd.md handed off by /product-workflow (for a problem/outcome-level PRD, use /product-prd) — flows, stories, states, edge cases; no KPIs, rollout, or implementation. Stage 1 of the /development-workflow…
Skill Claude CodeCodex
Final planning gate — verify specs are consistent, then generate tasks.md organized by user story with checkpoints; fails without generating tasks while Blocking/High issues remain. Stage 5 of /development-workflow, before /plan-implement. Use when the user asks to generate implementation tasks or invokes /plan-ready.
Skill Claude CodeCodex
Create an implementation-ready Technical Spec from a Product Spec. Stage 2 of /development-workflow, after /plan-product-spec. Use when the user asks to design a feature's technical implementation, plan the architecture, or invokes /plan-technical-spec.
Skill Claude CodeCodex
Skeptical pre-implementation review of Product/Technical/Contract Specs — ambiguity, contradictions, over-engineering, risk — with severity-ranked findings and interactive Q&A. Stage 4 of /development-workflow, before /plan-ready. Use when the user asks to verify, review, or challenge a plan/spec set, or invokes…
Skill Claude CodeCodex
Generate QA test plans, Gherkin test cases, regression suites, and an optional HTML dashboard. Use for "create a test plan for X", "write test cases for X", or "build a regression suite".
Skill Claude CodeCodex
QA acceptance testing of an implemented feature against the Product Spec — run suites, execute each story's Independent Test, edge cases, contract conformance; writes qa-report.md. Final stage of /development-workflow, after /impl-review. Use when the user asks to QA or acceptance-test a feature, or invokes /qa-test.
Skill Claude CodeCodex
Feature retrospective after a feature ships (or after any finished piece of work) — collect retro points, review them one by one, quiz the user when useful, and with the user's permission write each lesson into the right place (spec, skill, repo constitution, or memory). Use when the user asks for a retro, a…
Skill Claude CodeCodex
Judge and analyze an existing product or technical spec. Deep-research the product spec against competitors and first-principles; review the technical spec against the codebase for robustness, quality, simplicity, scalability, and long-term maintainability. Surfaces labeled findings and quizzes the user to resolve…
Skill Claude CodeCodex
Trace a feature through the codebase and generate it as an product spec or technical spec.
Skill Claude CodeCodex
Break a plan, spec, or conversation into atomic, dependency-ordered tickets (tracer-bullet vertical slices), or review tasks against their specs. Use for "break down this plan/spec into tasks", "create tickets", "task breakdown", or "review task T00X against the spec".
Skill Claude CodeCodex
Explain any topic, decision, code, or process for a complete beginner. Use when the user says "ELI5", "explain like I am five", asks for a very simple explanation, or appears unfamiliar with the topic.
Skill Claude CodeCodex
Quiz the user on a topic to check and strengthen their understanding. Default source is the current session — quiz on topics that stayed unresolved or unanswered. Use when the user says "quiz me", "test me", "check my understanding", or invokes /quiz-me.
Skill Claude CodeCodex
Default output style for installed skills: write documents and user-facing responses in Simplified Technical English (ASD-STE100) with simple words, short sentences, active voice, and clear structure. Use when the user wants simple text or invokes /simplified-english.
Skill Claude CodeCodex
Research that answers one exact question — use the products of competitors, read their bad reviews, read why deals were won or lost, and find what competitors will ship next. The result is a ranked list of actions. Stage P2 (optional) of /product-workflow. Simple English, no product experience needed. Use when the…
Skill Claude CodeCodex
Find which problem is worth the work — talk to real users, write what they said, and map their problems to possible solutions. Stage P1 of /product-workflow. Simple English, no product experience needed. Use when the user wants to learn about the users, plan interviews, or invokes /product-discovery.
Skill Claude CodeCodex
Set the meaning of success before the team builds, in numbers that a person can show are false — one main number, a few weekly numbers, one early signal, and the things that must not become worse. Then record the real numbers after launch. Stages P6 and P7 of /product-workflow. Simple English, no product experience…
Skill Claude CodeCodex
Skeptical review of one PRD before it goes to publish or to build — find the gaps, the parts that do not belong, the words with more than one meaning, and the risks; then close each gap by asking the user one question at a time. Runs after /product-prd, and before /product-publish-prd or /development-workflow. Simple…
Skill Claude CodeCodex
Write a short PRD that starts with the problem — introduction with 5W1H, success metrics, user stories, and a requirements table with acceptance criteria. Then give it to the /development-workflow build pipeline. Stage P5 of /product-workflow. Simple English, no product experience needed. Use when the user asks for a…
Skill Claude CodeCodex
Select what to build next and show the reasons — score the problems by how much users need help, score the solutions with a simple formula, give a source for each number, and make a roadmap with no false dates. Stage P4 of /product-workflow. Simple English, no product experience needed. Use when the user asks to put a…