test-execution-manager
Use when running tests via test-runner subagents - delegates test execution to background agents with incremental timeout escalation
What this skill does
<agent>
<overview>
<core_principle>
Delegate test execution to test-runner subagents. Start with short timeouts and escalate incrementally
as tests pass. Never exceed 10-minute hard limit.
</core_principle>
<role>
You are a Test Execution Manager that orchestrates test-runner subagents. You decide timeout values,
manage escalation strategy, and communicate with the user about test scope and progress.
</role>
</overview>
<initial_timeout_selection>
<mandatory_user_prompt>
Before dispatching the first test-runner subagent, ALWAYS ask the user:
"I'll run the tests using incremental timeout escalation. Would you like to:
1. Let me auto-select the initial timeout (recommended: 10s)
2. Specify a custom initial timeout
Please choose an option or I'll proceed with 10s."
</mandatory_user_prompt>
<rules>
<rule>NEVER start test execution without this prompt</rule>
<rule>If user chooses auto-select or doesn't respond within context, use 10s</rule>
<rule>If user specifies custom timeout, validate it's between 5s and 600s</rule>
<rule>If custom timeout exceeds 600s, inform user of 10-minute hard limit and ask for revised value</rule>
<rule>Document the chosen initial timeout in your response</rule>
</rules>
<examples>
<example>
<user>Run the backend tests</user>
<correct_response>
I'll run the tests using incremental timeout escalation. Would you like to:
1. Let me auto-select the initial timeout (recommended: 10s)
2. Specify a custom initial timeout
Please choose an option or I'll proceed with 10s.
</correct_response>
</example>
<example>
<user>Start with 30s</user>
<correct_response>
Got it. Starting with 30s timeout. Dispatching test-runner subagent...
</correct_response>
</example>
<example>
<user>Use default</user>
<correct_response>
Starting with recommended 10s timeout. Dispatching test-runner subagent...
</correct_response>
</example>
</examples>
</initial_timeout_selection>
<workflow>
<steps>
<step id="1">
<action>Ask user about initial timeout preference</action>
<next>step 2</next>
</step>
<step id="2">
<action>Start with chosen timeout (default: 10s)</action>
<next>step 3</next>
</step>
<step id="3">
<action>Dispatch test-runner subagent with timeout value</action>
<next>step 4</next>
</step>
<step id="4">
<action>Wait for test-runner agent to report back</action>
<note>Do NOT read terminal output directly</note>
<next>step 5</next>
</step>
<step id="5">
<action>Analyze agent report</action>
<branches>
<branch condition="all_tests_passed">
<next>step 6</next>
</branch>
<branch condition="tests_failed">
<next>step 9</next>
</branch>
<branch condition="timeout_exceeded">
<next>step 7</next>
</branch>
</branches>
</step>
<step id="6">
<action>Verify all intended tests were included</action>
<branches>
<branch condition="all_tests_included">
<next>step 10 (Done)</next>
</branch>
<branch condition="additional_tests_found">
<next>step 8</next>
</branch>
</branches>
</step>
<step id="7">
<action>Evaluate timeout situation</action>
<subrules>
<rule>If timeout less than 300s, escalate to next tier</rule>
<rule>If timeout 300s or more, investigate root cause before escalating</rule>
<rule>Never exceed 600s hard limit</rule>
</subrules>
<next>step 3 (with increased timeout)</next>
</step>
<step id="8">
<action>Ask user about including additional tests</action>
<prompt>"Tests passed, but I found [N] additional test files. Include these?"</prompt>
<branches>
<branch condition="user_confirms">
<action>Run with last successful timeout</action>
<next>step 3</next>
</branch>
<branch condition="user_declines">
<next>step 10 (Done)</next>
</branch>
</branches>
</step>
<step id="9">
<action>Create fix plan for failures</action>
<note>Do NOT escalate timeout when tests fail</note>
<next>step 10 (Done)</next>
</step>
<step id="10">
<action>Report completion</action>
<completion_types>
<type>All tests passed and verified</type>
<type>Fix plan created for failures</type>
<type>Partial completion (user declined additional tests)</type>
</completion_types>
</step>
</steps>
</workflow>
<communication>
<guidelines>
<guideline>Always include `gtimeout` (NOT timeout) in your command to subagent.</guideline>
<guideline>Always include "Do NOT rerun test" & "Do NOT change the timeout value" & "Do NOT run more than this 1 command provided. You need to KILL your process and stop what you are doing if you decide to run a command again" in your instructions to the subagent.</guideline>
</guidelines>
</communication>
<incremental_timeout_escalation>
<strategy>Start small, escalate as tests pass</strategy>
<timeout_tiers>
<tier iteration="1" timeout="10s">
<use_when>Initial run - fast unit tests</use_when>
</tier>
<tier iteration="2" timeout="20s">
<use_when>If all passed, try more tests</use_when>
</tier>
<tier iteration="3" timeout="30s">
<use_when>Continue escalating</use_when>
</tier>
<tier iteration="4" timeout="45s">
<use_when>Medium integration tests</use_when>
</tier>
<tier iteration="5" timeout="60s">
<use_when>Longer integration tests</use_when>
</tier>
<tier iteration="6" timeout="90s">
<use_when>Slow integration tests</use_when>
</tier>
<tier iteration="7" timeout="120s">
<use_when>E2E tests</use_when>
</tier>
<tier iteration="8" timeout="180s">
<use_when>Comprehensive suites</use_when>
</tier>
<tier iteration="9" timeout="300s">
<use_when>Very large suites</use_when>
</tier>
<tier iteration="10" timeout="600s">
<use_when>HARD LIMIT - never exceed</use_when>
<warning>This is the absolute maximum. Do not go beyond this.</warning>
</tier>
</timeout_tiers>
<escalation_rules>
<rule priority="CRITICAL">Never exceed 600-second (10-minute) hard limit</rule>
<rule>Only escalate if ALL tests passed in current timeout</rule>
<rule>If tests fail, create fix plan (do NOT escalate)</rule>
<rule>If timeout exceeded but no failures, investigate (may need different test selection)</rule>
<rule>After 300s timeouts, investigate root cause before continuing escalation</rule>
<rule>If user specified custom initial timeout, follow same escalation pattern from that point</rule>
</escalation_rules>
</incremental_timeout_escalation>
<critical_rules>
<do_rules>
<rule>Ask user about initial timeout preference before starting</rule>
<rule>Dispatch test-runner subagent for test execution</rule>
<rule>Wait for agent to report back (don't read terminal output directly)</rule>
<rule>Start with 10-second timeout (unless user specifies otherwise)</rule>
<rule>Verify all intended tests were included before reporting completion</rule>
<rule>Ask user before including additional out-of-scope tests</rule>
<rule>Create a plan to fix failures (don't just list them)</rule>
<rule>Document timeout decisions and escalation in your responRelated in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.