Skill Claude CodeCodex
Scan the wiki vault for unlinked mentions of page titles and topics. Insert [[wikilinks]] automatically. Run after /wiki ingest or standalone. Triggers on /cross-linker, "cross-link the wiki", "add wikilinks", "link wiki pages".
Skill Claude CodeCodex
Import a DesignOS export as structured context for Phase 1 planning. Reads the export and creates a design-context.md that enriches /discuss and /spec with design constraints, data shapes, milestone structure, and test scaffolding. Optional — the normal /discuss + /spec flow still runs. Triggers on /design-import…
Skill Claude CodeCodex
Create a git branch or worktree for isolated spec execution. One branch per spec. Triggers on /branch, "create branch", "set up worktree". Run after /pick-spec.
Skill Claude CodeCodex
Choose and validate the next spec for execution. Verifies the spec is complete, dependencies are met, and it fits a clean 200k context window. Triggers on /pick-spec, "what should we build next", "start execution".
Skill Claude CodeCodex
Review implementation against the spec between tasks. Two passes: spec compliance, then code quality. Critical findings BLOCK progress. Triggers on /code-review, between tasks, or when requested. Runs after each task in /subagent.
Skill Claude CodeCodex
Dispatch fresh subagents per task for parallel execution. Each subagent runs RED-GREEN-REFACTOR TDD on their task. Two-stage review per task. Human checkpoints between waves. Triggers on /subagent, "start executing", "run the tasks", "dispatch agents". Run after /branch.
Skill Claude CodeCodex
Enforce RED-GREEN-REFACTOR for every implementation task. This cycle runs inside each subagent task — not as a separate sequential step. Triggers on /tdd, when a task starts, or when code is being written without a failing test. Also used standalone when implementing outside of subagent mode.
Skill Claude CodeCodex
Capture implementation decisions BEFORE any spec is written. Triggers on /discuss, "what are we building", "let's plan", "I want to build X", "new feature". Always runs before /spec.
Skill Claude CodeCodex
Relentless interview to stress-test a spec before execution. Validates every decision against the wiki and techstack. Triggers on /grill, "grill me", "stress-test the spec", "challenge the plan". Always runs after /spec, before /pick-spec.
Skill Claude CodeCodex
Write an OpenSpec-style spec from the discussion document. Triggers on /spec, "write the spec", "create spec". Requires DISCUSS.md to exist. The spec must fit a fresh 200k context window.
Skill Claude CodeCodex
Create the PR, write the changelog entry, archive the phase directory, mark the spec complete, and trigger the next cycle. Triggers on /ship, "create PR", "ship it", "merge". Final step in the SuperSpecs lifecycle.
Skill Claude CodeCodex
Create a new SuperSpecs skill. Use when the user wants to extend the framework with a new workflow step or tool.
Skill Claude CodeCodex
Storybook workbench for visual frontend component development. No TDD/BDD — purely visual. Creates components, stories, and a component catalogue referenceable in /discuss and /spec. Triggers on /storybook, "new component", "build component in storybook", "add story".
Skill Claude CodeCodex
Maintain a controlled vocabulary of canonical tags for the wiki vault. Creates and updates meta/taxonomy.md. Audits all wiki pages for non-canonical tags and normalizes them. Triggers on /tag-taxonomy, "fix tags", "normalize wiki tags", "audit tags".
Skill Claude CodeCodex
TechLead questionnaire — elicits the project tech stack via guided questions and recommends installable skills, libraries, and production-readiness checklists for Frontend, Backend, Deployment, and CI/CD. Saves results to the wiki brain. Triggers on /techstack, "what skills do I need", "set up tech stack", "choose my…
Skill Claude CodeCodex
Full test suite run. Every spec scenario must have a passing test. No skipped tests. No pending tests. Invoked as Stage 1 of /superspecs:verify. Can also be triggered standalone on /check-tests, "run tests". Runs after all execution waves are complete.
Skill Claude CodeCodex
Distill a completed, verified feature into the project wiki. Architecture decisions, patterns, trade-offs, gotchas. The knowledge that should outlive this session. Invoked as Stage 2 of /superspecs:verify. Can also be triggered standalone on /wiki, "import to wiki", "document the feature". Runs after tests pass.
Skill Claude CodeCodex
Phase 3 combined verify. Stage 1 — run the full test suite, check spec scenario coverage, confirm no regressions. Stage 2 — distill the completed feature into the project wiki (architecture decisions, patterns, trade-offs, gotchas). Gate between stages: if tests fail, stop — do not proceed to wiki. Triggers on…
Skill Claude CodeCodex
Save findings from the current session directly to the wiki. Bugs fixed, decisions made, patterns discovered, gotchas hit. Quick mode stages a draft to raw/ for later ingest. Full mode distills directly to wiki pages. Triggers on /wiki-capture, "save to wiki", "capture this session", "note this for the wiki".
Skill Claude CodeCodex
Health check the compiled wiki vault. Finds orphaned pages, missing cross-links, contradictions between pages, and stale file references. Triggers on /wiki-lint, "lint the wiki", "check wiki health". Run periodically or before starting a new cycle.
Skill Claude CodeCodex
Query the compiled project wiki to answer a question. Uses tiered retrieval — summaries first, full pages only when needed. Synthesizes answers from existing wiki pages only, never from raw specs or the internet. Optionally files the answer back as a new wiki page. Triggers on /wiki-query, "search the wiki for..."…
Skill Claude CodeCodex
Archive the current wiki vault and rebuild it from scratch from raw source material and specs. Use when the wiki has drifted too far from its sources or accumulated too much drift. Also restores from a previous archive. Triggers on /wiki-rebuild, "rebuild the wiki", "archive and rebuild", "reset the wiki".
Skill Claude CodeCodex
Show a health and activity dashboard for the compiled wiki vault. Ingested pages, pending sources, hub pages with most backlinks, tag distribution, recent activity. Triggers on /wiki-status, "wiki dashboard", "wiki stats", "what's in the wiki".
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: