ln-511-test-researcher
Test Researcher
Researches real-world problems and edge cases before test planning to ensure tests cover actual user pain points, not just AC.
Purpose & Scope
- Research common problems for the feature domain using Web Search, MCP Ref, Context7.
- Analyze how competitors solve the same problem.
- Find customer complaints and pain points from forums, StackOverflow, Reddit.
- Post structured findings as Linear comment for downstream skills (ln-512, ln-513).
- No test creation or status changes.
When to Use
This skill should be used when:
- Invoked by ln-510-test-planner at start of test planning pipeline
- Story has non-trivial functionality (external APIs, file formats, authentication)
- Need to discover edge cases beyond AC
More from levnikolaevich/claude-code-skills
ln-624-code-quality-auditor
Checks cyclomatic complexity, nesting, long methods, god classes, O(n2), N+1 queries, constants management. Use when auditing code quality.
413ln-620-codebase-auditor
Use when auditing the codebase through the evaluation platform with mandatory research, coordinated domain audit workers, and structured summaries.
376ln-100-documents-pipeline
Creates complete project documentation system (project docs, reference, tasks, tests). Use when bootstrapping docs from scratch or regenerating all.
371ln-626-dead-code-auditor
Checks unreachable code, unused imports/variables/functions, commented-out code, unsupported patterns. Use when auditing dead code.
354ln-782-test-runner
Executes all test suites and reports results with coverage. Use when verifying that test infrastructure works after bootstrap.
343ln-775-api-docs-generator
Configures Swagger/OpenAPI documentation for backend APIs. Use when adding interactive API docs to a project.
339