create-strategy

Included with Lifetime

$97 forever

Create a comprehensive test strategy document following IEEE 829 structure. Use for establishing testing approach on new projects or standardizing existing practices.

Code Review

What this skill does


# Create Test Strategy Command

Generate a comprehensive test strategy document tailored to the project.

## Process

### Step 1: Gather Context

If project context is provided in arguments, use it. Otherwise:

1. Look for existing documentation:
   - Requirements documents
   - Architecture documents
   - Existing test plans
   - Risk assessments

2. Identify project characteristics:
   - Technology stack (.NET, React, etc.)
   - Architecture style (monolith, microservices)
   - Deployment model (cloud, on-prem)
   - Team size and structure

### Step 2: Load Skills

Invoke the `test-strategy:test-strategy-planning` skill for IEEE 829 templates and guidance.

### Step 3: Spawn Strategy Agent

Delegate to the `test-strategist` agent:

```text
Analyze the project context and create a comprehensive test strategy document.

Project Context:
[Gathered context]

Requirements:
1. Follow IEEE 829 structure
2. Include specific test level recommendations
3. Define measurable entry/exit criteria
4. Address identified risks
5. Recommend appropriate tools for the tech stack
```

### Step 4: Review and Validate

Ensure the strategy includes:

- [ ] Clear scope definition (in/out)
- [ ] Test objectives tied to business goals
- [ ] Test levels with responsibilities
- [ ] Test types appropriate for the project
- [ ] Risk-based prioritization
- [ ] Environment requirements
- [ ] Entry/exit criteria
- [ ] Defect management process
- [ ] Deliverables and schedule
- [ ] Roles and responsibilities

### Step 5: Output

Save the strategy document and report location:

```markdown
## Test Strategy Created

**File**: [path to strategy document]

**Summary**:
- Scope: [brief scope]
- Test Levels: [unit, integration, E2E]
- Key Risks: [top 3 risks addressed]
- Tools: [recommended stack]

**Next Steps**:
1. Review strategy with stakeholders
2. Set up test environments
3. Begin test case design
```

## Examples

**Simple invocation:**

```bash
/test-strategy:create-strategy
```

**With context:**

```bash
/test-strategy:create-strategy e-commerce platform with payments, .NET 10, microservices
```

Files: 1

Size: 2.3 KB

Complexity: 11/100

Category: Code Review

Source: https://github.com/melodic-software/claude-code-plugins/tree/main/plugins/test-strategy/skills/create-strategy

Related in Code Review

gstack

Included

Fast 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)

Code Reviewscriptsfeatured

startup-due-diligence

Included

Legal 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.

Code Reviewscripts

interview-master

Included

This 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.

Code Reviewscripts

fix-issue

Included

Fixes 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.

Code Reviewscripts

sf-apex

Included

Generates 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.

Code Reviewscripts

swift-development

Included

Comprehensive 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.

Code Reviewscripts