Skill Codex
Resolve material open questions in a QStack plan through one-at-a-time, plain-language decision dialogs, then write each answer and its consequences back into the plan immediately. Accepts a bootstrap Markdown plan or an authoritative QStack plan.html; once HTML exists, edits only HTML and never maintains a Markdown…
Skill Codex
Rewrite the immediately previous assistant answer in plain, non-technical language as a short bulleted list, or a numbered list when the content is ordered or counted. Use when the user invokes /qstack-be-concise, optionally with a target such as /qstack-be-concise 4, or asks to make the last answer shorter and…
Skill Codex
Assess what a proposed or recent change could break beyond its direct diff, identify the critical safety fact, and prove it with real code or mark it unproven. Use for blast-radius analysis, "what could this break?", or a small change whose downstream effects are uncertain.
Skill Claude CodeCodex
Build the smallest rerunnable tool that makes non-trivial work repeatable, reviewable, and safe to verify.
Skill Codex
Turn a recurring correction or repeated instruction into the strongest practical structural guardrail. Use when the same mistake returns, prose is being repeated, or a rule could become a type, schema, lint, check, or script.
Skill Codex
Reproduce and diagnose a failure until its root cause is supported by direct evidence, or trace a constraint presented as fixed down to what actually fixes it. Use for debugging, recurring symptoms, restart-only failures, a proposed guard that may only hide the real defect, or a claim that something is impossible, too…
Skill Claude CodeCodex
Settle data shape, access, ownership, concurrency, and useful shared setup before writing feature logic.
Skill Codex
Explain how a subsystem works by tracing its real runtime flow, ownership, boundaries, and files. Use for code walkthroughs, onboarding explanations, placement or layering questions, and explicitly requested architecture critique.
Skill Claude CodeCodex
Execute an approved implementation plan exactly, maintaining QStack execution evidence and asking how much independent adversarial review to run.
Skill Claude CodeCodex
Execute an approved implementation plan with documented adaptations, QStack execution evidence, and a user-selected adversarial review depth.
Skill Codex
Design or review commands, lifecycle steps, and processing loops so retries, partial failure, restart, and stale state converge to the same correct result. Use when an operation may run twice or resume after a crash.
Skill Codex
Replace scattered domain assumptions with the smallest structure that removes invalid states and branching. Use when booleans have to be kept in sync, the same rule is validated at several call sites, a branch grows with every new case, or an invalid state can be represented at all.
Skill Codex
Recommend the one installed skill to run next, from what the conversation has done so far and the state of the plan folder on disk. Use when invoked as /qstack-next, when asked "what now?" or which skill to use next, or as the last step of /qstack.
Skill Codex
Review whether an approved QStack HTML plan was faithfully executed by comparing plan.html with execution.md, executor.md, or legacy implementation notes and the actual committed and uncommitted code changes. Build a requirement-to-evidence matrix, identify missing or unapproved deviations, check whether the execution…
Skill Claude CodeCodex
Close an executed plan by recording its outcome against the plan and the execution board.
Skill Codex
Read the project's existing plan folder as content and brief the planner on what was already decided, deferred, and learned. Runs standalone before anything is written, or from /qstack-plan-to-html once that skill has settled its source and before the HTML document is. Ranks earlier plans by overlap with the subject…
Skill Claude CodeCodex
Render a plan as a reviewable QStack HLD/LLD HTML document, resolve its material open questions, and break it into the cards of its execution board. Takes a Markdown draft or the working agreement reached in the conversation. Also adds a board to a plan that already has HTML and no board.
Skill Codex
Verify completed work against the real artifact and its full input-to-output path instead of relying on compilation, timestamps, cached output, or agent summaries. Use before claiming a task or feature works.
Skill Codex
Produce an evidence-only report on how a project is actually being worked: checkout and branch topology, momentum over time, rework, instruction-file churn, and plan-record completeness. Every finding cites a count the reader can reproduce, and any category without enough evidence is refused rather than padded. Reads…
Skill Codex
Redesign concurrent work that shares a mutable file, branch, key, or state object by separating ownership before adding serialization. Use when actors may race, a lock is proposed, or coordination relies on taking turns.
Skill Claude CodeCodex
Serve the current repository's QStack HTML plan collection on a chosen local address and port.
Skill Claude CodeCodex
Rewrite the previous answer to remove AI writing patterns and add a natural human voice without losing meaning or useful detail.
Skill Claude CodeCodex
List every skill installed from QStack and from the optional collections QStack's installer offers as a table with a one-line description each, then recommend the next skill to run from the conversation so far and the plan folder on disk. Use when invoked as /qstack or when asked which QStack commands exist.
Skill Claude CodeCodex
Review a pull request, a branch against its base, or the working tree against a generic correctness baseline plus the repository's own CODEREVIEWRULES.md, then report findings and a score computed from their severities. Next to /review and /code-review, this one adds repository rules files, a score no reviewer is…
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: