- Home
- /
- Categories
- /
- Testing
Testing
Unit tests, integration tests, test automation
Documentation Updater
by anton-abyzov
Living documentation updater that syncs implementation progress to product docs. Use when updating docs after task completion, changing DRAFT status to published, or ensuring documentation reflects current implementation state.
Sync Living Docs
by anton-abyzov
Sync living docs for an increment. Generates or updates spec files in .specweave/docs/internal/specs/. Use when saying "sync docs", "update living docs", or "sync-docs".
TDD Cycle - Comprehensive Test-Driven Development
by anton-abyzov
Execute full TDD red-green-refactor cycle with validation gates. Use when saying "TDD cycle", "test-driven development", or "full TDD workflow".
Close Increment (PM Validated)
by anton-abyzov
Close increment with PM 3-gate validation (tasks, tests, docs). Use when all tasks complete and saying "close increment", "we're done", or "finish up".
Specweave Jira Mapper Skill
by anton-abyzov
Expert in mapping SpecWeave increments to JIRA structure (Increment → Epic + Stories + Subtasks) with bidirectional sync. Use when exporting increments to JIRA, importing JIRA epics as increments, or configuring field mapping. Maintains traceability across systems.
Spec-Driven Brainstorming Skill
by anton-abyzov
Spec-driven brainstorming and product discovery expert. Helps teams ideate features, break down epics, conduct story mapping sessions, prioritize using MoSCoW/RICE/Kano, and validate ideas with lean startup methods. Activates for brainstorming, product discovery, story mapping, feature ideation, prioritization, MoSCoW, RICE, Kano model, lean startup, MVP definition, product backlog, feature breakdown.
Do Increment
by anton-abyzov
Execute increment tasks following spec and plan with sync hooks. Use when saying "implement", "start working", "execute tasks", or "continue increment". IMPORTANT - Before starting, check task count and domain count. If 3+ domains or 15+ tasks, recommend /sw:team-lead instead (ask user for confirmation, or auto-invoke in auto mode).
TDD Green Phase - Make Tests Pass
by anton-abyzov
Write minimal code to make failing tests pass. Use when saying "TDD green", "make tests pass", or "implement for tests".
Frontend Architect Skill
by anton-abyzov
Frontend architect for React, Next.js, Vue, Angular. Use for component architecture, dashboards, Atomic Design, TanStack Query, Zustand/Redux, routing, performance.
Next Increment (Smart Workflow Transition)
by anton-abyzov
Close current increment if ready and suggest next work. Use when saying "what's next", "next increment", or "move on".
Azure DevOps Multi-Project Skill
by anton-abyzov
Organize specs and tasks across multiple Azure DevOps projects with intelligent content-based mapping. Use when working with project-per-team, area-path-based, or team-based ADO architectures. Handles cross-project coordination and folder structure organization.
deepeval
by sammcj
Use when discussing or working with DeepEval (the python AI evaluation framework)
ab-test-analysis
by nimrodfisher
Rigorous A/B test statistical analysis. Use when analyzing experiment results, calculating statistical significance, checking for sample ratio mismatch, or validating test design before launch.
playwright-skill
by lackeyjb
Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform any browser-based testing.
Skill: Spec Architect
by peterbamuhigire
Last Updated: 2026-02-20
plan-implementation
by peterbamuhigire
"Autonomous plan executor that implements feature plans from start to finish using TDD, 5-layer validation, and the 10 Commandments of Orchestration. Reads plans created by feature-planning skill and executes every task without stopping, producing production-ready, fully tested code. Use when the user says 'implement the plan', 'execute the plan', 'build this', or wants autonomous end-to-end implementation."
feature-planning
by peterbamuhigire
Complete feature planning from specification to implementation. Create structured specs with user stories and acceptance criteria, then generate detailed implementation plans with TDD workflow, exact file paths, and complete code examples.
Historical — Protocol Specification
by SimHacker
```
insforge
by InsForge
Build applications with InsForge Backend-as-a-Service. Use when developers need to: (1) Set up backend infrastructure (create tables, storage buckets, deploy functions, configure auth/AI) (2) Integrate InsForge SDK into frontend applications (database CRUD, auth flows, file uploads, AI operations, real-time messaging) (3) Deploy frontend applications to InsForge hosting IMPORTANT: Before any backend work, you MUST have the user's Project URL and API Key. If not provided, ask the user first. Key distinction: Backend configuration uses HTTP API calls to the InsForge project URL. Client integration uses the @insforge/sdk in application code.
testing-essentials
by j-morgan6
MANDATORY for ALL test files. Invoke before writing any _test.exs file.
qa-test-planner
by fugazi
Generate comprehensive test plans, manual test cases, automated Playwright tests, regression test suites, and bug reports for QA Automation engineers. Includes Playwright MCP integration for browser-based test execution and validation.
Practice Question Generator
by https-deeplearning-ai
webapp-playwright-testing
by fugazi
Browser automation toolkit using Playwright MCP for testing web applications. Use when asked to navigate pages, click elements, fill forms, take screenshots, verify UI components, check console logs, debug frontend issues, or validate responsive design. Supports live browser interaction and accessibility snapshots.
qa-manual-istqb
by fugazi
ISTQB Foundation Level (CTFL) aligned QA toolkit for manual and automated testing. Use when asked to create test plans, test strategies, test conditions, test cases, bug reports, defect logs, regression suites, traceability matrices, or exploratory charters. Supports risk-based testing, test design techniques (equivalence partitioning, boundary value analysis, decision tables, state transitions), test estimation, static testing reviews, and test process management. Includes Playwright automation guidance for test implementation.