| name | ln-511-test-researcher |
| description | Researches real-world problems, competitor solutions, and customer complaints before test planning. Posts findings as Linear comment for ln-512 and ln-513. |
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
Skip research when:
- Story is trivial (simple CRUD, no external dependencies)
- Research comment already exists on Story
- User explicitly requests to skip
Workflow
Phase 1: Discovery
Auto-discover Team ID from docs/tasks/kanban_board.md.
Input: Story ID from orchestrator (ln-510)
Phase 2: Extract Feature Domain
- Fetch Story from Linear
- Parse Story goal and AC to identify:
- What technology/API/format is involved?
- What is the user's goal? (e.g., "translate XLIFF files", "authenticate via OAuth")
- Extract keywords for research queries
Phase 3: Research Common Problems
Use available tools to find real-world problems:
