name: test-plan description: Generate manual test plans with test cases, role-based scenarios, and edge cases. Use when preparing for QA, before releases, after completing features, or when asked to create test documentation.
Manual Test Plan Generator
Generate comprehensive manual test plans for features, changes, or releases.
Scope
Create test plans covering:
1. Functional Testing
- Happy path scenarios
- Edge cases and boundary conditions
- Error handling and validation
- State transitions
- Data persistence
2. User Flow Testing
- Complete user journeys
- Multi-step workflows
- Navigation and routing
- Form submissions
- File uploads (task-attachments, user-avatars)
3. Role-Based Testing
- ADMIN role scenarios
- CLIENT role scenarios
- Permission boundaries
- Access control verification
- Client membership scoping
4. Cross-Browser Testing
- Chrome (latest)
- Firefox (latest)
- Safari (latest)
- Edge (latest)
5. Responsive Testing
- Mobile (320px+)
- Tablet (768px+)
- Desktop (1024px+)
- Per AGENTS.md: no horizontal scroll
6. Accessibility Testing
- Keyboard-only navigation
- Screen reader compatibility
- Focus management
- Color contrast
7. Integration Points
- Supabase Auth flows
- Supabase Storage operations
- Email sending (Resend)
- External API integrations
Output Format
# Test Plan: [Feature Name]
## Overview
Brief description of what's being tested
## Prerequisites
- Required test data
- User accounts needed
- Environment setup
## Test Cases
### TC-001: [Test Case Name]
**Priority:** P0|P1|P2
**Type:** Functional|UI|Integration|Security
**Role:** ADMIN|CLIENT|Unauthenticated
**Preconditions:**
- List of required states
**Steps:**
1. Step-by-step instructions
2. Be specific about clicks/inputs
3. Include expected intermediate states
**Expected Result:**
- What should happen
**Actual Result:**
- [ ] Pass
- [ ] Fail (describe issue)
---
Actions
- Analyze the feature or change scope
- Identify all user-facing behaviors
- Map permission requirements
- Consider failure modes
- Include regression scenarios
Test Plan Principles
- Cover both positive and negative cases
- Include data boundary conditions
- Test with different user roles
- Verify soft delete behavior
- Check loading and empty states
Post-Generation
Provide:
- Prioritized test case list (P0 first)
- Estimated testing time
- Required test data setup scripts
- Automation candidates for future
chat Comments (0)
Sign in to join the discussion and leave a comment.
Skill Details
GitHub Stars
0
GitHub Forks
0
Created
Jan 2026
Last Updated
5 months ago
tools
tools productivity tools
Related Skills
Build your own?
Join 12,000+ developers contributing to the Claude ecosystem.
No comments yet. Be the first to share your thoughts!