[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71EF2FC3EQ2M6SCY2MPQ4TP":3,"skill-same:01M71EF2FC3EQ2M6SCY2MPQ4TP":115},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":34,"publishedAt":55,"linkOnly":56,"markdownContent":57,"markdownBody":58,"frontMatter":59,"refName":61,"commitSha":62,"skillDirectory":63,"forksCount":14,"repositoryHtmlUrl":64,"repositoryHomepageUrl":6,"ownerHtmlUrl":65,"ownerBlogUrl":66,"ownerDescription":67,"updatedAt":68,"install":69,"resources":82},"01M71EF2FC3EQ2M6SCY2MPQ4TP","qa-test-planner",null,"Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.","patinaproject\u002Fskills","patinaproject","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F229996889?v=4","01M71E58JKTDNY1138WYZK44TR","Patina Project","01M71E58K5GH4K16MV6A8BQ6NZ",1,"MIT","https:\u002F\u002Fgithub.com\u002Fpatinaproject\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fqa-test-planner\u002FSKILL.md",[18,23,26,29],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54],"test","qa","qa test planner","qa test","planner","test planner","regression test","figma mcp","manual test","test cases","for","manual","plans","reports","bug","design","regression","figma","generate","MCP","2026-11-10 10:12:30",false,"---\nname: qa-test-planner\ndescription: Generate comprehensive test plans, manual test cases, regression test suites, and bug reports for QA engineers. Includes Figma MCP integration for design validation.\ntrigger: explicit\n---\n\n# QA Test Planner\n\nA comprehensive skill for QA engineers to create test plans, generate manual test cases, build regression test suites, validate designs against Figma, and document bugs effectively.\n\n> **Activation:** This skill is triggered only when explicitly called by name (e.g., `\u002Fqa-test-planner`, `qa-test-planner`, or `use the skill qa-test-planner`).\n\n---\n\n## Quick Start\n\n**Create a test plan:**\n```\n\"Create a test plan for the user authentication feature\"\n```\n\n**Generate test cases:**\n```\n\"Generate manual test cases for the checkout flow\"\n```\n\n**Build regression suite:**\n```\n\"Build a regression test suite for the payment module\"\n```\n\n**Validate against Figma:**\n```\n\"Compare the login page against the Figma design at [URL]\"\n```\n\n**Create bug report:**\n```\n\"Create a bug report for the form validation issue\"\n```\n\n---\n\n## Quick Reference\n\n| Task | What You Get | Time |\n|------|--------------|------|\n| Test Plan | Strategy, scope, schedule, risks | 10-15 min |\n| Test Cases | Step-by-step instructions, expected results | 5-10 min each |\n| Regression Suite | Smoke tests, critical paths, execution order | 15-20 min |\n| Figma Validation | Design-implementation comparison, discrepancy list | 10-15 min |\n| Bug Report | Reproducible steps, environment, evidence | 5 min |\n\n---\n\n## How It Works\n\n```\nYour Request\n    │\n    ▼\n┌─────────────────────────────────────────────────────┐\n│ 1. ANALYZE                                          │\n│    • Parse feature\u002Frequirement                      │\n│    • Identify test types needed                     │\n│    • Determine scope and priorities                 │\n├─────────────────────────────────────────────────────┤\n│ 2. GENERATE                                         │\n│    • Create structured deliverables                 │\n│    • Apply templates and best practices             │\n│    • Include edge cases and variations              │\n├─────────────────────────────────────────────────────┤\n│ 3. VALIDATE                                         │\n│    • Check completeness                             │\n│    • Verify traceability                            │\n│    • Ensure actionable steps                        │\n└─────────────────────────────────────────────────────┘\n    │\n    ▼\nQA Deliverable Ready\n```\n\n---\n\n## Commands\n\n### Interactive Scripts\n\n| Script | Purpose | Usage |\n|--------|---------|-------|\n| `.\u002Fscripts\u002Fgenerate_test_cases.sh` | Create test cases interactively | Step-by-step prompts |\n| `.\u002Fscripts\u002Fcreate_bug_report.sh` | Generate bug reports | Guided input collection |\n\n### Natural Language\n\n| Request | Output |\n|---------|--------|\n| \"Create test plan for {feature}\" | Complete test plan document |\n| \"Generate {N} test cases for {feature}\" | Numbered test cases with steps |\n| \"Build smoke test suite\" | Critical path tests |\n| \"Compare with Figma at {URL}\" | Visual validation checklist |\n| \"Document bug: {description}\" | Structured bug report |\n\n---\n\n## Core Deliverables\n\n### 1. Test Plans\n- Test scope and objectives\n- Testing approach and strategy\n- Environment requirements\n- Entry\u002Fexit criteria\n- Risk assessment\n- Timeline and milestones\n\n### 2. Manual Test Cases\n- Step-by-step instructions\n- Expected vs actual results\n- Preconditions and setup\n- Test data requirements\n- Priority and severity\n\n### 3. Regression Suites\n- Smoke tests (15-30 min)\n- Full regression (2-4 hours)\n- Targeted regression (30-60 min)\n- Execution order and dependencies\n\n### 4. Figma Validation\n- Component-by-component comparison\n- Spacing and typography checks\n- Color and visual consistency\n- Interactive state validation\n\n### 5. Bug Reports\n- Clear reproduction steps\n- Environment details\n- Evidence (screenshots, logs)\n- Severity and priority\n\n---\n\n## Anti-Patterns\n\n| Avoid | Why | Instead |\n|-------|-----|---------|\n| Vague test steps | Can't reproduce | Specific actions + expected results |\n| Missing preconditions | Tests fail unexpectedly | Document all setup requirements |\n| No test data | Tester blocked | Provide sample data or generation |\n| Generic bug titles | Hard to track | Specific: \"[Feature] issue when [action]\" |\n| Skip edge cases | Miss critical bugs | Include boundary values, nulls |\n\n---\n\n## Verification Checklist\n\n**Test Plan:**\n- [ ] Scope clearly defined (in\u002Fout)\n- [ ] Entry\u002Fexit criteria specified\n- [ ] Risks identified with mitigations\n- [ ] Timeline realistic\n\n**Test Cases:**\n- [ ] Each step has expected result\n- [ ] Preconditions documented\n- [ ] Test data available\n- [ ] Priority assigned\n\n**Bug Reports:**\n- [ ] Reproducible steps\n- [ ] Environment documented\n- [ ] Screenshots\u002Fevidence attached\n- [ ] Severity\u002Fpriority set\n\n---\n\n## References\n\n- [Test Case Templates](references\u002Ftest_case_templates.md) - Standard formats for all test types\n- [Bug Report Templates](references\u002Fbug_report_templates.md) - Documentation templates\n- [Regression Testing Guide](references\u002Fregression_testing.md) - Suite building and execution\n- [Figma Validation Guide](references\u002Ffigma_validation.md) - Design-implementation validation\n\n---\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>Deep Dive: Test Case Structure\u003C\u002Fstrong>\u003C\u002Fsummary>\n\n### Standard Test Case Format\n\n```markdown\n## TC-001: [Test Case Title]\n\n**Priority:** High | Medium | Low\n**Type:** Functional | UI | Integration | Regression\n**Status:** Not Run | Pass | Fail | Blocked\n\n### Objective\n[What are we testing and why]\n\n### Preconditions\n- [Setup requirement 1]\n- [Setup requirement 2]\n- [Test data needed]\n\n### Test Steps\n1. [Action to perform]\n   **Expected:** [What should happen]\n\n2. [Action to perform]\n   **Expected:** [What should happen]\n\n3. [Action to perform]\n   **Expected:** [What should happen]\n\n### Test Data\n- Input: [Test data values]\n- User: [Test account details]\n- Configuration: [Environment settings]\n\n### Post-conditions\n- [System state after test]\n- [Cleanup required]\n\n### Notes\n- [Edge cases to consider]\n- [Related test cases]\n- [Known issues]\n```\n\n### Test Types\n\n| Type | Focus | Example |\n|------|-------|---------|\n| Functional | Business logic | Login with valid credentials |\n| UI\u002FVisual | Appearance, layout | Button matches Figma design |\n| Integration | Component interaction | API returns data to frontend |\n| Regression | Existing functionality | Previous features still work |\n| Performance | Speed, load handling | Page loads under 3 seconds |\n| Security | Vulnerabilities | SQL injection prevented |\n\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>Deep Dive: Test Plan Template\u003C\u002Fstrong>\u003C\u002Fsummary>\n\n### Test Plan Structure\n\n```markdown\n# Test Plan: [Feature\u002FRelease Name]\n\n## Executive Summary\n- Feature\u002Fproduct being tested\n- Testing objectives\n- Key risks\n- Timeline overview\n\n## Test Scope\n\n**In Scope:**\n- Features to be tested\n- Test types (functional, UI, performance)\n- Platforms and environments\n- User flows and scenarios\n\n**Out of Scope:**\n- Features not being tested\n- Known limitations\n- Third-party integrations (if applicable)\n\n## Test Strategy\n\n**Test Types:**\n- Manual testing\n- Exploratory testing\n- Regression testing\n- Integration testing\n- User acceptance testing\n\n**Test Approach:**\n- Black box testing\n- Positive and negative testing\n- Boundary value analysis\n- Equivalence partitioning\n\n## Test Environment\n- Operating systems\n- Browsers and versions\n- Devices (mobile, tablet, desktop)\n- Test data requirements\n- Backend\u002FAPI environments\n\n## Entry Criteria\n- [ ] Requirements documented\n- [ ] Designs finalized\n- [ ] Test environment ready\n- [ ] Test data prepared\n- [ ] Build deployed\n\n## Exit Criteria\n- [ ] All high-priority test cases executed\n- [ ] 90%+ test case pass rate\n- [ ] All critical bugs fixed\n- [ ] No open high-severity bugs\n- [ ] Regression suite passed\n\n## Risk Assessment\n\n| Risk | Probability | Impact | Mitigation |\n|------|-------------|--------|------------|\n| [Risk 1] | H\u002FM\u002FL | H\u002FM\u002FL | [Mitigation] |\n\n## Test Deliverables\n- Test plan document\n- Test cases\n- Test execution reports\n- Bug reports\n- Test summary report\n```\n\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>Deep Dive: Bug Reporting\u003C\u002Fstrong>\u003C\u002Fsummary>\n\n### Bug Report Template\n\n```markdown\n# BUG-[ID]: [Clear, specific title]\n\n**Severity:** Critical | High | Medium | Low\n**Priority:** P0 | P1 | P2 | P3\n**Type:** Functional | UI | Performance | Security\n**Status:** Open | In Progress | Fixed | Closed\n\n## Environment\n- **OS:** [Windows 11, macOS 14, etc.]\n- **Browser:** [Chrome 120, Firefox 121, etc.]\n- **Device:** [Desktop, iPhone 15, etc.]\n- **Build:** [Version\u002Fcommit]\n- **URL:** [Page where bug occurs]\n\n## Description\n[Clear, concise description of the issue]\n\n## Steps to Reproduce\n1. [Specific step]\n2. [Specific step]\n3. [Specific step]\n\n## Expected Behavior\n[What should happen]\n\n## Actual Behavior\n[What actually happens]\n\n## Visual Evidence\n- Screenshot: [attached]\n- Video: [link if applicable]\n- Console errors: [paste errors]\n\n## Impact\n- **User Impact:** [How many users affected]\n- **Frequency:** [Always, Sometimes, Rarely]\n- **Workaround:** [If one exists]\n\n## Additional Context\n- Related to: [Feature\u002Fticket]\n- Regression: [Yes\u002FNo]\n- Figma design: [Link if UI bug]\n```\n\n### Severity Definitions\n\n| Level | Criteria | Examples |\n|-------|----------|----------|\n| **Critical (P0)** | System crash, data loss, security | Payment fails, login broken |\n| **High (P1)** | Major feature broken, no workaround | Search not working |\n| **Medium (P2)** | Feature partial, workaround exists | Filter missing one option |\n| **Low (P3)** | Cosmetic, rare edge cases | Typo, minor alignment |\n\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>Deep Dive: Figma MCP Integration\u003C\u002Fstrong>\u003C\u002Fsummary>\n\n### Design Validation Workflow\n\n**Prerequisites:**\n- Figma MCP server configured\n- Access to Figma design files\n- Figma URLs for components\u002Fpages\n\n**Process:**\n\n1. **Get Design Specs from Figma**\n```\n\"Get the button specifications from Figma file [URL]\"\n\nResponse includes:\n- Dimensions (width, height)\n- Colors (background, text, border)\n- Typography (font, size, weight)\n- Spacing (padding, margin)\n- Border radius\n- States (default, hover, active, disabled)\n```\n\n2. **Compare Implementation**\n```\nTC: Primary Button Visual Validation\n1. Inspect primary button in browser dev tools\n2. Compare against Figma specs:\n   - Dimensions: 120x40px\n   - Border-radius: 8px\n   - Background color: #0066FF\n   - Font: 16px Medium #FFFFFF\n3. Document discrepancies\n```\n\n3. **Create Bug if Mismatch**\n```\nBUG: Primary button color doesn't match design\nSeverity: Medium\nExpected (Figma): #0066FF\nActual (Implementation): #0052CC\nScreenshot: [attached]\nFigma link: [specific component]\n```\n\n### What to Validate\n\n| Element | What to Check | Tool |\n|---------|---------------|------|\n| Colors | Hex values exact | Browser color picker |\n| Spacing | Padding\u002Fmargin px | DevTools computed styles |\n| Typography | Font, size, weight | DevTools font panel |\n| Layout | Width, height, position | DevTools box model |\n| States | Hover, active, focus | Manual interaction |\n| Responsive | Breakpoint behavior | DevTools device mode |\n\n### Example Queries\n```\n\"Get button specifications from Figma design [URL]\"\n\"Compare navigation menu implementation against Figma design\"\n\"Extract spacing values for dashboard layout from Figma\"\n\"List all color tokens used in Figma design system\"\n```\n\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>Deep Dive: Regression Testing\u003C\u002Fstrong>\u003C\u002Fsummary>\n\n### Suite Structure\n\n| Suite Type | Duration | Frequency | Coverage |\n|------------|----------|-----------|----------|\n| Smoke | 15-30 min | Daily | Critical paths only |\n| Targeted | 30-60 min | Per change | Affected areas |\n| Full | 2-4 hours | Weekly\u002FRelease | Comprehensive |\n| Sanity | 10-15 min | After hotfix | Quick validation |\n\n### Building a Regression Suite\n\n**Step 1: Identify Critical Paths**\n- What can users NOT live without?\n- What generates revenue?\n- What handles sensitive data?\n- What's used most frequently?\n\n**Step 2: Prioritize Test Cases**\n\n| Priority | Description | Must Run |\n|----------|-------------|----------|\n| P0 | Business-critical, security | Always |\n| P1 | Major features, common flows | Weekly+ |\n| P2 | Minor features, edge cases | Releases |\n\n**Step 3: Execution Order**\n1. Smoke first - if fails, stop and fix build\n2. P0 tests next - must pass before proceeding\n3. P1 then P2 - track all failures\n4. Exploratory - find unexpected issues\n\n### Pass\u002FFail Criteria\n\n**PASS:**\n- All P0 tests pass\n- 90%+ P1 tests pass\n- No critical bugs open\n\n**FAIL (Block Release):**\n- Any P0 test fails\n- Critical bug discovered\n- Security vulnerability\n- Data loss scenario\n\n**CONDITIONAL:**\n- P1 failures with workarounds\n- Known issues documented\n- Fix plan in place\n\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>Deep Dive: Test Execution Tracking\u003C\u002Fstrong>\u003C\u002Fsummary>\n\n### Test Run Report Template\n\n```markdown\n# Test Run: [Release Version]\n\n**Date:** 2024-01-15\n**Build:** v2.5.0-rc1\n**Tester:** [Name]\n**Environment:** Staging\n\n## Summary\n- Total Test Cases: 150\n- Executed: 145\n- Passed: 130\n- Failed: 10\n- Blocked: 5\n- Not Run: 5\n- Pass Rate: 90%\n\n## Test Cases by Priority\n\n| Priority | Total | Pass | Fail | Blocked |\n|----------|-------|------|------|---------|\n| P0 (Critical) | 25 | 23 | 2 | 0 |\n| P1 (High) | 50 | 45 | 3 | 2 |\n| P2 (Medium) | 50 | 45 | 3 | 2 |\n| P3 (Low) | 25 | 17 | 2 | 1 |\n\n## Critical Failures\n- TC-045: Payment processing fails\n  - Bug: BUG-234\n  - Status: Open\n\n## Blocked Tests\n- TC-112: Dashboard widget (API endpoint down)\n\n## Risks\n- 2 critical bugs blocking release\n- Payment integration needs attention\n\n## Next Steps\n- Retest after BUG-234 fix\n- Complete remaining 5 test cases\n- Run full regression before sign-off\n```\n\n### Coverage Tracking\n\n```markdown\n## Coverage Matrix\n\n| Feature | Requirements | Test Cases | Status | Gaps |\n|---------|--------------|------------|--------|------|\n| Login | 8 | 12 | Complete | None |\n| Checkout | 15 | 10 | Partial | Payment errors |\n| Dashboard | 12 | 15 | Complete | None |\n```\n\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>QA Process Workflow\u003C\u002Fstrong>\u003C\u002Fsummary>\n\n### Phase 1: Planning\n- [ ] Review requirements and designs\n- [ ] Create test plan\n- [ ] Identify test scenarios\n- [ ] Estimate effort and timeline\n- [ ] Set up test environment\n\n### Phase 2: Test Design\n- [ ] Write test cases\n- [ ] Review test cases with team\n- [ ] Prepare test data\n- [ ] Build regression suite\n- [ ] Get Figma design access\n\n### Phase 3: Execution\n- [ ] Execute test cases\n- [ ] Log bugs with clear steps\n- [ ] Validate against Figma (UI tests)\n- [ ] Track test progress\n- [ ] Communicate blockers\n\n### Phase 4: Reporting\n- [ ] Compile test results\n- [ ] Analyze coverage\n- [ ] Document risks\n- [ ] Provide go\u002Fno-go recommendation\n- [ ] Archive test artifacts\n\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>Best Practices\u003C\u002Fstrong>\u003C\u002Fsummary>\n\n### Test Case Writing\n\n**DO:**\n- Be specific and unambiguous\n- Include expected results for each step\n- Test one thing per test case\n- Use consistent naming conventions\n- Keep test cases maintainable\n\n**DON'T:**\n- Assume knowledge\n- Make test cases too long\n- Skip preconditions\n- Forget edge cases\n- Leave expected results vague\n\n### Bug Reporting\n\n**DO:**\n- Provide clear reproduction steps\n- Include screenshots\u002Fvideos\n- Specify exact environment details\n- Describe impact on users\n- Link to Figma for UI bugs\n\n**DON'T:**\n- Report without reproduction steps\n- Use vague descriptions\n- Skip environment details\n- Forget to assign priority\n- Duplicate existing bugs\n\n### Regression Testing\n\n**DO:**\n- Automate repetitive tests when possible\n- Maintain regression suite regularly\n- Prioritize critical paths\n- Run smoke tests frequently\n- Update suite after each release\n\n**DON'T:**\n- Skip regression before releases\n- Let suite become outdated\n- Test everything every time\n- Ignore failed regression tests\n\n\u003C\u002Fdetails>\n\n---\n\n## Examples\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>Example: Login Flow Test Case\u003C\u002Fstrong>\u003C\u002Fsummary>\n\n```markdown\n## TC-LOGIN-001: Valid User Login\n\n**Priority:** P0 (Critical)\n**Type:** Functional\n**Estimated Time:** 2 minutes\n\n### Objective\nVerify users can successfully login with valid credentials\n\n### Preconditions\n- User account exists (test@example.com \u002F Test123!)\n- User is not already logged in\n- Browser cookies cleared\n\n### Test Steps\n1. Navigate to https:\u002F\u002Fapp.example.com\u002Flogin\n   **Expected:** Login page displays with email and password fields\n\n2. Enter email: test@example.com\n   **Expected:** Email field accepts input\n\n3. Enter password: Test123!\n   **Expected:** Password field shows masked characters\n\n4. Click \"Login\" button\n   **Expected:**\n   - Loading indicator appears\n   - User redirected to \u002Fdashboard\n   - Welcome message shown: \"Welcome back, Test User\"\n   - Avatar\u002Fprofile image displayed in header\n\n### Post-conditions\n- User session created\n- Auth token stored\n- Analytics event logged\n\n### Edge Cases to Consider\n- TC-LOGIN-002: Invalid password\n- TC-LOGIN-003: Non-existent email\n- TC-LOGIN-004: SQL injection attempt\n- TC-LOGIN-005: Very long password\n```\n\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>Example: Responsive Design Test Case\u003C\u002Fstrong>\u003C\u002Fsummary>\n\n```markdown\n## TC-UI-045: Mobile Navigation Menu\n\n**Priority:** P1 (High)\n**Type:** UI\u002FResponsive\n**Devices:** Mobile (iPhone, Android)\n\n### Objective\nVerify navigation menu works correctly on mobile devices\n\n### Preconditions\n- Access from mobile device or responsive mode\n- Viewport width: 375px (iPhone SE) to 428px (iPhone Pro Max)\n\n### Test Steps\n1. Open homepage on mobile device\n   **Expected:** Hamburger menu icon visible (top-right)\n\n2. Tap hamburger icon\n   **Expected:**\n   - Menu slides in from right\n   - Overlay appears over content\n   - Close (X) button visible\n\n3. Tap menu item\n   **Expected:** Navigate to section, menu closes\n\n4. Compare against Figma mobile design [link]\n   **Expected:**\n   - Menu width: 280px\n   - Slide animation: 300ms ease-out\n   - Overlay opacity: 0.5, color #000000\n   - Font size: 16px, line-height 24px\n\n### Breakpoints to Test\n- 375px (iPhone SE)\n- 390px (iPhone 14)\n- 428px (iPhone 14 Pro Max)\n- 360px (Galaxy S21)\n```\n\n\u003C\u002Fdetails>\n\n---\n\n**\"Testing shows the presence, not the absence of bugs.\" - Edsger Dijkstra**\n\n**\"Quality is not an act, it is a habit.\" - Aristotle**\n","# QA Test Planner\n\nA comprehensive skill for QA engineers to create test plans, generate manual test cases, build regression test suites, validate designs against Figma, and document bugs effectively.\n\n> **Activation:** This skill is triggered only when explicitly called by name (e.g., `\u002Fqa-test-planner`, `qa-test-planner`, or `use the skill qa-test-planner`).\n\n---\n\n## Quick Start\n\n**Create a test plan:**\n```\n\"Create a test plan for the user authentication feature\"\n```\n\n**Generate test cases:**\n```\n\"Generate manual test cases for the checkout flow\"\n```\n\n**Build regression suite:**\n```\n\"Build a regression test suite for the payment module\"\n```\n\n**Validate against Figma:**\n```\n\"Compare the login page against the Figma design at [URL]\"\n```\n\n**Create bug report:**\n```\n\"Create a bug report for the form validation issue\"\n```\n\n---\n\n## Quick Reference\n\n| Task | What You Get | Time |\n|------|--------------|------|\n| Test Plan | Strategy, scope, schedule, risks | 10-15 min |\n| Test Cases | Step-by-step instructions, expected results | 5-10 min each |\n| Regression Suite | Smoke tests, critical paths, execution order | 15-20 min |\n| Figma Validation | Design-implementation comparison, discrepancy list | 10-15 min |\n| Bug Report | Reproducible steps, environment, evidence | 5 min |\n\n---\n\n## How It Works\n\n```\nYour Request\n    │\n    ▼\n┌─────────────────────────────────────────────────────┐\n│ 1. ANALYZE                                          │\n│    • Parse feature\u002Frequirement                      │\n│    • Identify test types needed                     │\n│    • Determine scope and priorities                 │\n├─────────────────────────────────────────────────────┤\n│ 2. GENERATE                                         │\n│    • Create structured deliverables                 │\n│    • Apply templates and best practices             │\n│    • Include edge cases and variations              │\n├─────────────────────────────────────────────────────┤\n│ 3. VALIDATE                                         │\n│    • Check completeness                             │\n│    • Verify traceability                            │\n│    • Ensure actionable steps                        │\n└─────────────────────────────────────────────────────┘\n    │\n    ▼\nQA Deliverable Ready\n```\n\n---\n\n## Commands\n\n### Interactive Scripts\n\n| Script | Purpose | Usage |\n|--------|---------|-------|\n| `.\u002Fscripts\u002Fgenerate_test_cases.sh` | Create test cases interactively | Step-by-step prompts |\n| `.\u002Fscripts\u002Fcreate_bug_report.sh` | Generate bug reports | Guided input collection |\n\n### Natural Language\n\n| Request | Output |\n|---------|--------|\n| \"Create test plan for {feature}\" | Complete test plan document |\n| \"Generate {N} test cases for {feature}\" | Numbered test cases with steps |\n| \"Build smoke test suite\" | Critical path tests |\n| \"Compare with Figma at {URL}\" | Visual validation checklist |\n| \"Document bug: {description}\" | Structured bug report |\n\n---\n\n## Core Deliverables\n\n### 1. Test Plans\n- Test scope and objectives\n- Testing approach and strategy\n- Environment requirements\n- Entry\u002Fexit criteria\n- Risk assessment\n- Timeline and milestones\n\n### 2. Manual Test Cases\n- Step-by-step instructions\n- Expected vs actual results\n- Preconditions and setup\n- Test data requirements\n- Priority and severity\n\n### 3. Regression Suites\n- Smoke tests (15-30 min)\n- Full regression (2-4 hours)\n- Targeted regression (30-60 min)\n- Execution order and dependencies\n\n### 4. Figma Validation\n- Component-by-component comparison\n- Spacing and typography checks\n- Color and visual consistency\n- Interactive state validation\n\n### 5. Bug Reports\n- Clear reproduction steps\n- Environment details\n- Evidence (screenshots, logs)\n- Severity and priority\n\n---\n\n## Anti-Patterns\n\n| Avoid | Why | Instead |\n|-------|-----|---------|\n| Vague test steps | Can't reproduce | Specific actions + expected results |\n| Missing preconditions | Tests fail unexpectedly | Document all setup requirements |\n| No test data | Tester blocked | Provide sample data or generation |\n| Generic bug titles | Hard to track | Specific: \"[Feature] issue when [action]\" |\n| Skip edge cases | Miss critical bugs | Include boundary values, nulls |\n\n---\n\n## Verification Checklist\n\n**Test Plan:**\n- [ ] Scope clearly defined (in\u002Fout)\n- [ ] Entry\u002Fexit criteria specified\n- [ ] Risks identified with mitigations\n- [ ] Timeline realistic\n\n**Test Cases:**\n- [ ] Each step has expected result\n- [ ] Preconditions documented\n- [ ] Test data available\n- [ ] Priority assigned\n\n**Bug Reports:**\n- [ ] Reproducible steps\n- [ ] Environment documented\n- [ ] Screenshots\u002Fevidence attached\n- [ ] Severity\u002Fpriority set\n\n---\n\n## References\n\n- [Test Case Templates](references\u002Ftest_case_templates.md) - Standard formats for all test types\n- [Bug Report Templates](references\u002Fbug_report_templates.md) - Documentation templates\n- [Regression Testing Guide](references\u002Fregression_testing.md) - Suite building and execution\n- [Figma Validation Guide](references\u002Ffigma_validation.md) - Design-implementation validation\n\n---\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>Deep Dive: Test Case Structure\u003C\u002Fstrong>\u003C\u002Fsummary>\n\n### Standard Test Case Format\n\n```markdown\n## TC-001: [Test Case Title]\n\n**Priority:** High | Medium | Low\n**Type:** Functional | UI | Integration | Regression\n**Status:** Not Run | Pass | Fail | Blocked\n\n### Objective\n[What are we testing and why]\n\n### Preconditions\n- [Setup requirement 1]\n- [Setup requirement 2]\n- [Test data needed]\n\n### Test Steps\n1. [Action to perform]\n   **Expected:** [What should happen]\n\n2. [Action to perform]\n   **Expected:** [What should happen]\n\n3. [Action to perform]\n   **Expected:** [What should happen]\n\n### Test Data\n- Input: [Test data values]\n- User: [Test account details]\n- Configuration: [Environment settings]\n\n### Post-conditions\n- [System state after test]\n- [Cleanup required]\n\n### Notes\n- [Edge cases to consider]\n- [Related test cases]\n- [Known issues]\n```\n\n### Test Types\n\n| Type | Focus | Example |\n|------|-------|---------|\n| Functional | Business logic | Login with valid credentials |\n| UI\u002FVisual | Appearance, layout | Button matches Figma design |\n| Integration | Component interaction | API returns data to frontend |\n| Regression | Existing functionality | Previous features still work |\n| Performance | Speed, load handling | Page loads under 3 seconds |\n| Security | Vulnerabilities | SQL injection prevented |\n\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>Deep Dive: Test Plan Template\u003C\u002Fstrong>\u003C\u002Fsummary>\n\n### Test Plan Structure\n\n```markdown\n# Test Plan: [Feature\u002FRelease Name]\n\n## Executive Summary\n- Feature\u002Fproduct being tested\n- Testing objectives\n- Key risks\n- Timeline overview\n\n## Test Scope\n\n**In Scope:**\n- Features to be tested\n- Test types (functional, UI, performance)\n- Platforms and environments\n- User flows and scenarios\n\n**Out of Scope:**\n- Features not being tested\n- Known limitations\n- Third-party integrations (if applicable)\n\n## Test Strategy\n\n**Test Types:**\n- Manual testing\n- Exploratory testing\n- Regression testing\n- Integration testing\n- User acceptance testing\n\n**Test Approach:**\n- Black box testing\n- Positive and negative testing\n- Boundary value analysis\n- Equivalence partitioning\n\n## Test Environment\n- Operating systems\n- Browsers and versions\n- Devices (mobile, tablet, desktop)\n- Test data requirements\n- Backend\u002FAPI environments\n\n## Entry Criteria\n- [ ] Requirements documented\n- [ ] Designs finalized\n- [ ] Test environment ready\n- [ ] Test data prepared\n- [ ] Build deployed\n\n## Exit Criteria\n- [ ] All high-priority test cases executed\n- [ ] 90%+ test case pass rate\n- [ ] All critical bugs fixed\n- [ ] No open high-severity bugs\n- [ ] Regression suite passed\n\n## Risk Assessment\n\n| Risk | Probability | Impact | Mitigation |\n|------|-------------|--------|------------|\n| [Risk 1] | H\u002FM\u002FL | H\u002FM\u002FL | [Mitigation] |\n\n## Test Deliverables\n- Test plan document\n- Test cases\n- Test execution reports\n- Bug reports\n- Test summary report\n```\n\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>Deep Dive: Bug Reporting\u003C\u002Fstrong>\u003C\u002Fsummary>\n\n### Bug Report Template\n\n```markdown\n# BUG-[ID]: [Clear, specific title]\n\n**Severity:** Critical | High | Medium | Low\n**Priority:** P0 | P1 | P2 | P3\n**Type:** Functional | UI | Performance | Security\n**Status:** Open | In Progress | Fixed | Closed\n\n## Environment\n- **OS:** [Windows 11, macOS 14, etc.]\n- **Browser:** [Chrome 120, Firefox 121, etc.]\n- **Device:** [Desktop, iPhone 15, etc.]\n- **Build:** [Version\u002Fcommit]\n- **URL:** [Page where bug occurs]\n\n## Description\n[Clear, concise description of the issue]\n\n## Steps to Reproduce\n1. [Specific step]\n2. [Specific step]\n3. [Specific step]\n\n## Expected Behavior\n[What should happen]\n\n## Actual Behavior\n[What actually happens]\n\n## Visual Evidence\n- Screenshot: [attached]\n- Video: [link if applicable]\n- Console errors: [paste errors]\n\n## Impact\n- **User Impact:** [How many users affected]\n- **Frequency:** [Always, Sometimes, Rarely]\n- **Workaround:** [If one exists]\n\n## Additional Context\n- Related to: [Feature\u002Fticket]\n- Regression: [Yes\u002FNo]\n- Figma design: [Link if UI bug]\n```\n\n### Severity Definitions\n\n| Level | Criteria | Examples |\n|-------|----------|----------|\n| **Critical (P0)** | System crash, data loss, security | Payment fails, login broken |\n| **High (P1)** | Major feature broken, no workaround | Search not working |\n| **Medium (P2)** | Feature partial, workaround exists | Filter missing one option |\n| **Low (P3)** | Cosmetic, rare edge cases | Typo, minor alignment |\n\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>Deep Dive: Figma MCP Integration\u003C\u002Fstrong>\u003C\u002Fsummary>\n\n### Design Validation Workflow\n\n**Prerequisites:**\n- Figma MCP server configured\n- Access to Figma design files\n- Figma URLs for components\u002Fpages\n\n**Process:**\n\n1. **Get Design Specs from Figma**\n```\n\"Get the button specifications from Figma file [URL]\"\n\nResponse includes:\n- Dimensions (width, height)\n- Colors (background, text, border)\n- Typography (font, size, weight)\n- Spacing (padding, margin)\n- Border radius\n- States (default, hover, active, disabled)\n```\n\n2. **Compare Implementation**\n```\nTC: Primary Button Visual Validation\n1. Inspect primary button in browser dev tools\n2. Compare against Figma specs:\n   - Dimensions: 120x40px\n   - Border-radius: 8px\n   - Background color: #0066FF\n   - Font: 16px Medium #FFFFFF\n3. Document discrepancies\n```\n\n3. **Create Bug if Mismatch**\n```\nBUG: Primary button color doesn't match design\nSeverity: Medium\nExpected (Figma): #0066FF\nActual (Implementation): #0052CC\nScreenshot: [attached]\nFigma link: [specific component]\n```\n\n### What to Validate\n\n| Element | What to Check | Tool |\n|---------|---------------|------|\n| Colors | Hex values exact | Browser color picker |\n| Spacing | Padding\u002Fmargin px | DevTools computed styles |\n| Typography | Font, size, weight | DevTools font panel |\n| Layout | Width, height, position | DevTools box model |\n| States | Hover, active, focus | Manual interaction |\n| Responsive | Breakpoint behavior | DevTools device mode |\n\n### Example Queries\n```\n\"Get button specifications from Figma design [URL]\"\n\"Compare navigation menu implementation against Figma design\"\n\"Extract spacing values for dashboard layout from Figma\"\n\"List all color tokens used in Figma design system\"\n```\n\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>Deep Dive: Regression Testing\u003C\u002Fstrong>\u003C\u002Fsummary>\n\n### Suite Structure\n\n| Suite Type | Duration | Frequency | Coverage |\n|------------|----------|-----------|----------|\n| Smoke | 15-30 min | Daily | Critical paths only |\n| Targeted | 30-60 min | Per change | Affected areas |\n| Full | 2-4 hours | Weekly\u002FRelease | Comprehensive |\n| Sanity | 10-15 min | After hotfix | Quick validation |\n\n### Building a Regression Suite\n\n**Step 1: Identify Critical Paths**\n- What can users NOT live without?\n- What generates revenue?\n- What handles sensitive data?\n- What's used most frequently?\n\n**Step 2: Prioritize Test Cases**\n\n| Priority | Description | Must Run |\n|----------|-------------|----------|\n| P0 | Business-critical, security | Always |\n| P1 | Major features, common flows | Weekly+ |\n| P2 | Minor features, edge cases | Releases |\n\n**Step 3: Execution Order**\n1. Smoke first - if fails, stop and fix build\n2. P0 tests next - must pass before proceeding\n3. P1 then P2 - track all failures\n4. Exploratory - find unexpected issues\n\n### Pass\u002FFail Criteria\n\n**PASS:**\n- All P0 tests pass\n- 90%+ P1 tests pass\n- No critical bugs open\n\n**FAIL (Block Release):**\n- Any P0 test fails\n- Critical bug discovered\n- Security vulnerability\n- Data loss scenario\n\n**CONDITIONAL:**\n- P1 failures with workarounds\n- Known issues documented\n- Fix plan in place\n\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>Deep Dive: Test Execution Tracking\u003C\u002Fstrong>\u003C\u002Fsummary>\n\n### Test Run Report Template\n\n```markdown\n# Test Run: [Release Version]\n\n**Date:** 2024-01-15\n**Build:** v2.5.0-rc1\n**Tester:** [Name]\n**Environment:** Staging\n\n## Summary\n- Total Test Cases: 150\n- Executed: 145\n- Passed: 130\n- Failed: 10\n- Blocked: 5\n- Not Run: 5\n- Pass Rate: 90%\n\n## Test Cases by Priority\n\n| Priority | Total | Pass | Fail | Blocked |\n|----------|-------|------|------|---------|\n| P0 (Critical) | 25 | 23 | 2 | 0 |\n| P1 (High) | 50 | 45 | 3 | 2 |\n| P2 (Medium) | 50 | 45 | 3 | 2 |\n| P3 (Low) | 25 | 17 | 2 | 1 |\n\n## Critical Failures\n- TC-045: Payment processing fails\n  - Bug: BUG-234\n  - Status: Open\n\n## Blocked Tests\n- TC-112: Dashboard widget (API endpoint down)\n\n## Risks\n- 2 critical bugs blocking release\n- Payment integration needs attention\n\n## Next Steps\n- Retest after BUG-234 fix\n- Complete remaining 5 test cases\n- Run full regression before sign-off\n```\n\n### Coverage Tracking\n\n```markdown\n## Coverage Matrix\n\n| Feature | Requirements | Test Cases | Status | Gaps |\n|---------|--------------|------------|--------|------|\n| Login | 8 | 12 | Complete | None |\n| Checkout | 15 | 10 | Partial | Payment errors |\n| Dashboard | 12 | 15 | Complete | None |\n```\n\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>QA Process Workflow\u003C\u002Fstrong>\u003C\u002Fsummary>\n\n### Phase 1: Planning\n- [ ] Review requirements and designs\n- [ ] Create test plan\n- [ ] Identify test scenarios\n- [ ] Estimate effort and timeline\n- [ ] Set up test environment\n\n### Phase 2: Test Design\n- [ ] Write test cases\n- [ ] Review test cases with team\n- [ ] Prepare test data\n- [ ] Build regression suite\n- [ ] Get Figma design access\n\n### Phase 3: Execution\n- [ ] Execute test cases\n- [ ] Log bugs with clear steps\n- [ ] Validate against Figma (UI tests)\n- [ ] Track test progress\n- [ ] Communicate blockers\n\n### Phase 4: Reporting\n- [ ] Compile test results\n- [ ] Analyze coverage\n- [ ] Document risks\n- [ ] Provide go\u002Fno-go recommendation\n- [ ] Archive test artifacts\n\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>Best Practices\u003C\u002Fstrong>\u003C\u002Fsummary>\n\n### Test Case Writing\n\n**DO:**\n- Be specific and unambiguous\n- Include expected results for each step\n- Test one thing per test case\n- Use consistent naming conventions\n- Keep test cases maintainable\n\n**DON'T:**\n- Assume knowledge\n- Make test cases too long\n- Skip preconditions\n- Forget edge cases\n- Leave expected results vague\n\n### Bug Reporting\n\n**DO:**\n- Provide clear reproduction steps\n- Include screenshots\u002Fvideos\n- Specify exact environment details\n- Describe impact on users\n- Link to Figma for UI bugs\n\n**DON'T:**\n- Report without reproduction steps\n- Use vague descriptions\n- Skip environment details\n- Forget to assign priority\n- Duplicate existing bugs\n\n### Regression Testing\n\n**DO:**\n- Automate repetitive tests when possible\n- Maintain regression suite regularly\n- Prioritize critical paths\n- Run smoke tests frequently\n- Update suite after each release\n\n**DON'T:**\n- Skip regression before releases\n- Let suite become outdated\n- Test everything every time\n- Ignore failed regression tests\n\n\u003C\u002Fdetails>\n\n---\n\n## Examples\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>Example: Login Flow Test Case\u003C\u002Fstrong>\u003C\u002Fsummary>\n\n```markdown\n## TC-LOGIN-001: Valid User Login\n\n**Priority:** P0 (Critical)\n**Type:** Functional\n**Estimated Time:** 2 minutes\n\n### Objective\nVerify users can successfully login with valid credentials\n\n### Preconditions\n- User account exists (test@example.com \u002F Test123!)\n- User is not already logged in\n- Browser cookies cleared\n\n### Test Steps\n1. Navigate to https:\u002F\u002Fapp.example.com\u002Flogin\n   **Expected:** Login page displays with email and password fields\n\n2. Enter email: test@example.com\n   **Expected:** Email field accepts input\n\n3. Enter password: Test123!\n   **Expected:** Password field shows masked characters\n\n4. Click \"Login\" button\n   **Expected:**\n   - Loading indicator appears\n   - User redirected to \u002Fdashboard\n   - Welcome message shown: \"Welcome back, Test User\"\n   - Avatar\u002Fprofile image displayed in header\n\n### Post-conditions\n- User session created\n- Auth token stored\n- Analytics event logged\n\n### Edge Cases to Consider\n- TC-LOGIN-002: Invalid password\n- TC-LOGIN-003: Non-existent email\n- TC-LOGIN-004: SQL injection attempt\n- TC-LOGIN-005: Very long password\n```\n\n\u003C\u002Fdetails>\n\n\u003Cdetails>\n\u003Csummary>\u003Cstrong>Example: Responsive Design Test Case\u003C\u002Fstrong>\u003C\u002Fsummary>\n\n```markdown\n## TC-UI-045: Mobile Navigation Menu\n\n**Priority:** P1 (High)\n**Type:** UI\u002FResponsive\n**Devices:** Mobile (iPhone, Android)\n\n### Objective\nVerify navigation menu works correctly on mobile devices\n\n### Preconditions\n- Access from mobile device or responsive mode\n- Viewport width: 375px (iPhone SE) to 428px (iPhone Pro Max)\n\n### Test Steps\n1. Open homepage on mobile device\n   **Expected:** Hamburger menu icon visible (top-right)\n\n2. Tap hamburger icon\n   **Expected:**\n   - Menu slides in from right\n   - Overlay appears over content\n   - Close (X) button visible\n\n3. Tap menu item\n   **Expected:** Navigate to section, menu closes\n\n4. Compare against Figma mobile design [link]\n   **Expected:**\n   - Menu width: 280px\n   - Slide animation: 300ms ease-out\n   - Overlay opacity: 0.5, color #000000\n   - Font size: 16px, line-height 24px\n\n### Breakpoints to Test\n- 375px (iPhone SE)\n- 390px (iPhone 14)\n- 428px (iPhone 14 Pro Max)\n- 360px (Galaxy S21)\n```\n\n\u003C\u002Fdetails>\n\n---\n\n**\"Testing shows the presence, not the absence of bugs.\" - Edsger Dijkstra**\n\n**\"Quality is not an act, it is a habit.\" - Aristotle**\n",{"name":5,"trigger":60,"description":7},"explicit","main","e6ee720f466a8344a52abd87679191fadde3b63f",".agents\u002Fskills\u002Fqa-test-planner","https:\u002F\u002Fgithub.com\u002Fpatinaproject\u002Fskills","https:\u002F\u002Fgithub.com\u002Fpatinaproject","https:\u002F\u002Fwww.patinaproject.com","The best way to pick your next pair of boots or shoes.","2026-11-11 10:34:42",{"source":8,"skillName":5,"commands":70,"prompt":80,"zipAvailable":81},[71,74,77],{"tool":72,"command":73},"npx","npx skills add patinaproject\u002Fskills --skill qa-test-planner",{"tool":75,"command":76},"bunx","bunx skills add patinaproject\u002Fskills --skill qa-test-planner",{"tool":78,"command":79},"pnpm","pnpm dlx skills add patinaproject\u002Fskills --skill qa-test-planner","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fpatinaproject\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fqa-test-planner\u002FSKILL.md",true,[83,89,93,97,101,105,111],{"path":84,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":87,"sourceHtmlUrl":88},"README.md","REFERENCE","参考文档",10887,"https:\u002F\u002Fgithub.com\u002Fpatinaproject\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fqa-test-planner\u002FREADME.md",{"path":90,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Fbug_report_templates.md",8607,"https:\u002F\u002Fgithub.com\u002Fpatinaproject\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fqa-test-planner\u002Freferences\u002Fbug_report_templates.md",{"path":94,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Ffigma_validation.md",7046,"https:\u002F\u002Fgithub.com\u002Fpatinaproject\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fqa-test-planner\u002Freferences\u002Ffigma_validation.md",{"path":98,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fregression_testing.md",7273,"https:\u002F\u002Fgithub.com\u002Fpatinaproject\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fqa-test-planner\u002Freferences\u002Fregression_testing.md",{"path":102,"resourceType":85,"resourceTypeDesc":86,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Ftest_case_templates.md",9220,"https:\u002F\u002Fgithub.com\u002Fpatinaproject\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fqa-test-planner\u002Freferences\u002Ftest_case_templates.md",{"path":106,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":109,"sourceHtmlUrl":110},"scripts\u002Fcreate_bug_report.sh","SCRIPT","脚本",5912,"https:\u002F\u002Fgithub.com\u002Fpatinaproject\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fqa-test-planner\u002Fscripts\u002Fcreate_bug_report.sh",{"path":112,"resourceType":107,"resourceTypeDesc":108,"sizeBytes":113,"sourceHtmlUrl":114},"scripts\u002Fgenerate_test_cases.sh",6624,"https:\u002F\u002Fgithub.com\u002Fpatinaproject\u002Fskills\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fqa-test-planner\u002Fscripts\u002Fgenerate_test_cases.sh",[116,142,154,176,200,216],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":128,"publishedAt":55},"01M71ESEDVHD9EXN6787XHP7HD","writing-for-pstack","Write or tighten an operator prompt for a patina-mode run. Use when the operator asks to write, revise, or review a prompt that will be passed to patina-mode.","https:\u002F\u002Fgithub.com\u002Fpatinaproject\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fwork\u002Fskills\u002Fwriting-for-pstack\u002FSKILL.md",[122,125],{"categoryNo":123,"categoryName":124,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":126,"categoryName":127,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000036","内容创作者",[129,130,45,131,132,133,134,135,136,137,138,139,140,141],"writing for pstack","writing","pstack","when","run","review","prompt","write","use","revise","tighten","mode","operator",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":150,"publishedAt":55},"01M71ESCJ0SSJFFENF8HYDKBTJ","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Fpatinaproject\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fwork\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[148,149],{"categoryNo":123,"categoryName":124,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":126,"categoryName":127,"taxonomyType":32,"taxonomyTypeDesc":33},[130,151,45,152,132,137,153],"writing for agents","editing","documents",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":55},"01M71ESA1NN9WVMD2HA5Z1RRDY","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002Fpatinaproject\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fwork\u002Fskills\u002Fwizard\u002FSKILL.md",[],[156,161,45,162,163,164,165,166,137,132,167,168,169,170,53,171,172,173,174,175],"interactive","can","human","provisioning infrastructure","up","only","Bash","secrets","credentials","ci","dashboard","invoke","one","setting","running",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":182,"publishedAt":55},"01M71ES8FAN567N3JEPG8W6AS1","wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002Fpatinaproject\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fwork\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[178,183,184,185,186,162,187,188,189,190,191,192,193,173,194,195,196,197,198,199],"at","tracker","destination","agent session","true","more","tickets","as","shared","time","map","session","one at a time","work","decision","plan","chunk",{"skillNo":201,"name":202,"nameZh":6,"description":203,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":204,"categories":205,"keywords":206,"publishedAt":55},"01M71ES6PWJPKBW8R24YFH4PY6","wait-what","Stop. That last message did not land: re-pitch it.","https:\u002F\u002Fgithub.com\u002Fpatinaproject\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fwork\u002Fskills\u002Fwait-what\u002FSKILL.md",[],[207,208,209,210,211,212,213,187,214,215],"wait","wait what","pitch","message","stop","land","it","last","re",{"skillNo":217,"name":218,"nameZh":6,"description":219,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":220,"categories":221,"keywords":222,"publishedAt":55},"01M71ES4ZXKEGMMYS0NFPEBQ80","using-github","Work with repository settings, pull requests, reviews, checks, and releases on GitHub. Use for GitHub operations other than issue tracking.","https:\u002F\u002Fgithub.com\u002Fpatinaproject\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fwork\u002Fskills\u002Fusing-github\u002FSKILL.md",[],[223,224,225,45,226,227,228,229,230,231,137,232,233,234,196,235,236,237],"github","using github","issue","issue tracking","github operations","requests","reviews","with","releases","operations","tracking","settings","repository","pull","pull requests"]