joris887

uat-cycle

Execute a UAT test case — select, test, process findings, fix or log, and close the cycle.

architecture-check

Validate module boundaries, check for architectural drift, and suggest fitness function tests. Compares actual code structure against ARCHITECTURE.md.

backlog-review

Execute comprehensive backlog review. Analyzes story quality, Definition of Ready compliance, dependencies, zombie stories, and generates a backlog health report.

bootstrap

First-run framework setup. Detects existing project stack or guides new project creation from vision/braindump.

brainstorm

Use when the user has a complex idea that needs design exploration before story decomposition.

Web & Frontend Listed

build

Build a project from a plain-English description. Handles all technical decisions automatically. Designed for non-technical users but useful for anyone who wants fast results.

claude-sense-check

Incremental code logic verification of UAT test cases — pick batch, trace code, fix issues, update tracking.

Analyzes code quality, complexity, duplication, and architectural patterns. Use after implementing features, during code review, or when preparing for PR. Auto-invoke when user has completed significant code changes or asks to review code quality.

continue

Resume development with smart session continuation. Reads session handoff files, sprint spec, analyzes git state, and determines the best path forward.

custom-hooks

Create project-specific hook scripts and register them in settings.json. Extends the framework's enforcement layer.

dashboard

Sprint status overview with session insights, sprint trends, and actionable next steps.

debug-session

Use when the user reports a bug, error, or unexpected behavior that needs investigation.

deploy

Deploy the project to a hosting platform. Detects deployment configuration, runs pre-deploy checks, and guides first-time setup.

discover

Deep guided elicitation for new projects. Archetype-aware, research-backed, multi-phase discovery with assumption tracking and Phase Transition Stories.

doctor

Validate framework configuration, check runtime dependencies, and report issues. Use when something isn't working or after setup.

fix-issue

Fix a GitHub issue following project coding standards. Creates branch, implements fix with TDD, and prepares PR.

framework-upgrade

Upgrade Exosuit to a newer version while preserving project customizations.

handoff

Generate a structured handoff document for ending a development session. Saves to docs/sessions/ for the continue skill to read.

help-me

Natural language skill discovery — describe what you want to do and get matched to the right skill.

ideate

Use when the user has an idea or requirement to decompose into backlog stories.

manual-test

Prepare for manual testing session with test plan based on known issues, recent changes, and acceptance criteria.

merge-down

Use when the user is inside a parallel stream (worktree branch) and wants to bring that branch up to date with the LATEST of its parent branch — typically after one or more sibling streams have merged their work up into the parent (via /merge-up). Pulls the parent's accumulated commits down into the current branch with a true merge. Inverse of /merge-up; the parent is recorded by /parallel-work in git config (branch.<name>.exosuitParent). Read-only on the parent — safe to run while the parent worktree is busy.

merge-up

Use when the user is inside a parallel stream (worktree branch) and wants to merge that branch's committed work into the parent branch it was created from, then bring the stream back up to date with the parent. True merge (keeps individual commits); prompts before pushing the parent. Pairs with /parallel-work, which records the parent in git config (branch.<name>.exosuitParent), and with /merge-down (the inverse direction).

optimize

Use when the user wants to autonomously improve a measurable metric through iterative experimentation with git-based checkpointing and automatic rollback.

parallel-work

Work on multiple stories at the same time. Creates isolated parallel streams (git worktrees) from the current branch, wires up local settings, and opens each in its own Claude Code session. Also shows stream status and cleans up finished streams. Pairs with /merge-up (publish a stream's work to the parent branch) and /merge-down (pull the parent's accumulated work into a stream).

API & Backend Listed

performance-check

Analyze performance patterns — N+1 queries, unbounded operations, blocking I/O, memory leaks, and scaling behavior. Auto-invoke after performance-sensitive code changes.

phase-review

Phase transition review — walkthrough built features, validate assumptions, refresh research, decide direction, and plan next phase.

quickstart

Guided interactive tour of the framework. Walks through your first sprint from zero to shipped PR.

research

Deep online research on any topic. Produces structured reports with citations and confidence scores. Three depth modes — quick scan, standard investigation, or deep dive.

retrospective

Sprint retrospective — consumes progress.md Metrics table, adds leading-lagging analysis, anti-pattern detection, and 4Ls framework.

security-audit

Security review for code touching authentication, credentials, file access, or user data. Includes CWE checklist ranked by AI vulnerability frequency, phantom package detection, ASVS-aligned controls, and supply chain checks. MANDATORY for auth code, credential handling, file operations with user data, network comms, or database queries with user input.

skill-create

Analyze the repository's technology stack and generate appropriate skills, rules, and hook configurations.

skill-eval

Use when you want to test, measure, or compare skill effectiveness. Supports eval, compare, metrics, baseline capture, and regression detection.

sprint-end

Use when the user wants to ship a sprint's work to main via PR.

sprint-start

Pre-sprint checks, feature branch creation, and sprint planning. Ensures clean state, defines sprint goal and scope, creates sprint spec document.

story-cycle

Use when the user wants to implement a single story or deliver a backlog item.

test-validator

Validates test coverage, quality, and TDD compliance. Detects weakened assertions, deleted tests, and tautological patterns. Auto-invoke when user has written code and needs test validation.

testing-cycle

Process a single user testing feedback item — classify, fix or log, verify, and report.

undo-work

Safely discard or revert failed implementation attempts and restore a clean working state.

uninstall

Cleanly remove the Exosuit framework from a project while preserving project-specific content.

weekly-maintenance

Execute comprehensive weekly maintenance routine (1-2 hours, Friday recommended). Includes health checks, quality review, dependency governance, activity insights, and planning.