tommymorgan

Create a new feature plan via brainstorming with Gherkin requirements

Execute plan autonomously with TDD, code review, and exploratory testing gates until complete

Check scenario completion status in a plan and report progress

Review a plan file with the expert panel

Review Gherkin scenarios with context-aware domain experts

Smart testing with plan-awareness - automatically selects appropriate testing strategy based on context

Perform systematic root cause analysis using five whys methodology

One-time migration to create living .feature files from historical plans

Generate user or developer documentation from living .feature files

Analyze test coverage of living specification scenarios

Audit and configure jj safety checks for the current repository

Diff-scoped code review with optional fix loop that re-reviews until clean

Copy the last assistant output to the clipboard

General code review for project guidelines, style, and bug detection

Analyze code comments and documentation for accuracy and completeness

Analyze test coverage quality, gaps, and resilience

Hunt for silent failures, inadequate error handling, and missing logging

Analyze type design quality including encapsulation, invariants, and usefulness

Find unnecessary complexity, redundant code, and opportunities for simplification

You are an autonomous API testing agent specializing in comprehensive REST and GraphQL API exploratory testing. Your role is to systematically discover, validate, and test API endpoints to identify bugs, security issues, and integration problems.

You are an autonomous web application testing agent specializing in comprehensive browser-based exploratory testing. Your role is to systematically explore web applications to identify functional bugs, visual issues, accessibility problems, and performance bottlenecks.

You are an autonomous command-line tool testing agent specializing in comprehensive CLI exploratory testing. Your role is to systematically test command-line tools and scripts to identify bugs, validate error handling, and ensure robust behavior.

Autonomous exploratory testing agent that validates implementation against plan scenarios

You are a systematic root cause analyst specializing in the five whys methodology. Your purpose is to identify actual root causes before any solution attempts, preventing speculation-driven debugging.

Reviews findings through a panel of 14 domain experts, auto-selected by content. Debates conflicts and reaches consensus. Used by code review fix loops and plan review commands.

Applies consensus-approved code fixes from the expert panel. Edits files sequentially and resolves any lint issues introduced by each fix.

Turn ideas into fully formed designs through collaborative dialogue

This skill should be used when creating plan files, writing Gherkin requirements, or parsing plan file structure. Provides the plan file template and format specifications.

This skill should be used when executing plan tasks autonomously, implementing features using TDD, running the red-green-refactor cycle, handling code review loops, or dealing with blocked tasks. Provides the autonomous TDD execution workflow.

This skill should be used when checking plan status, running verification commands, updating task statuses, or determining what work remains. Provides the verification sweep algorithm and status update procedures.

This skill should be used when performing exploratory testing of REST or GraphQL APIs, including endpoint discovery, request/response validation, authentication testing, and error handling checks. Triggers when testing APIs, validating OpenAPI specs, checking endpoint security, or verifying API responses.

This skill should be used when performing browser-based exploratory testing of web applications, including functional testing, visual inspection, accessibility checks, and performance analysis. Triggers when testing web UIs, checking for browser bugs, validating WCAG compliance, or measuring Core Web Vitals.

This skill should be used when performing exploratory testing of command-line tools and scripts, including help text validation, option testing, error handling verification, and output validation. Triggers when testing CLI commands, scripts, build tools, or command-line interfaces.

This skill should be used when the user reports "error", "bug", "problem", needs to "fix" something, mentions "debug", "failing", "broken", "issue", "not working", "crash", or any problem-solving scenario. Enforces systematic root cause identification using five whys methodology before attempting solutions.

Opinionated REST API design guidance for resource naming, HTTP semantics, error formats, pagination, versioning, and more. Use when designing REST APIs during brainstorming or plan creation.

Use when working with Jujutsu (jj) version control system, creating changes, managing bookmarks, or pushing code. Triggers on jj commands and .jj/ directory presence.

4 hooks across 4 events