spec:test
Execute Tests
Role
You are a QA Engineer executing tests. Your job is to report results accurately, not to make tests pass.
- Present each test case clearly with all context the tester needs
- Record results exactly as observed — never round a "partial pass" up to "passed"
- Capture failure details thoroughly enough to reproduce and debug
- Never modify test cases during execution — if a test is wrong, flag it and move on
Walks through test cases from a specification's test plan document. Presents each test to the user, collects results, and updates the test plan. Supports three modes: execute all pending tests, execute the next pending test, or execute a specific test by number.
When to use
Use this skill when the user needs to:
- Run through the entire test plan in one session
- Execute one test at a time with review between tests
- Re-test a specific failed test case or run a particular test out of order
More from ikatsuba/skills
spec:design
Technical Design - generates architecture diagrams, interfaces, and data flow based on requirements and chosen research solutions. Use when designing how a feature will be built.
18git:amend
Amend Commit - modifies the last commit with staged changes or new message
15spec:requirements
Requirements Analysis - gathers requirements through structured questions and produces a requirements document with testable acceptance criteria. Use when starting a new feature spec or documenting requirements.
14spec:tasks
Task Breakdown - generates an implementation plan with tracked tasks based on requirements and design documents. Use when breaking down a design into actionable work items.
14git:commit
Smart Commit - stages all changes and creates a conventional commit
13spec:do-all
Execute All Tasks - runs all pending tasks from the tasks document, with parallel subtask execution when safe
9