with one click
ln-521-test-researcher
// Researches real-world problems, competitor solutions, and customer complaints for a feature domain. Use before test planning to ground tests in actual user pain points.
// Researches real-world problems, competitor solutions, and customer complaints for a feature domain. Use before test planning to ground tests in actual user pain points.
[HINT] Download the complete skill directory including SKILL.md and all related files
| name | ln-521-test-researcher |
| description | Researches real-world problems, competitor solutions, and customer complaints for a feature domain. Use before test planning to ground tests in actual user pain points. |
| license | MIT |
Paths: File paths (
references/,../ln-*) are relative to this skill directory.
| Input | Required | Source | Description |
|---|---|---|---|
storyId | Yes | args, git branch, kanban, user | Story to process |
Resolution: Story Resolution Chain. Status filter: To Review
Type: L3 Worker
Researches real-world problems and edge cases before test planning to ensure tests cover actual user pain points, not just AC.
addComment) for later test-planning steps.This skill should be used when:
Skip research when:
MANDATORY READ: Load references/input_resolution_pattern.md
Resolve storyId: Run Story Resolution Chain per guide (status filter: [To Review]).
Auto-discover Team ID from docs/tasks/kanban_board.md
getStory)Use available tools to find real-world problems:
Web Search:
MCP Ref:
ref_search_documentation("[feature] error handling best practices")ref_search_documentation("[format] validation rules")Context7:
Web Search:
Analysis:
Web Search:
Analysis:
Compile findings into categories:
Post tracker comment (addComment) on Story with research summary:
## Test Research: {Feature}
### Sources Consulted
- [Source 1](url)
- [Source 2](url)
### Common Problems Found
1. **Problem 1:** Description + test case suggestion
2. **Problem 2:** Description + test case suggestion
### Competitor Analysis
- **Competitor A:** How they handle this + what we can learn
- **Competitor B:** Their approach + gaps we can exploit
### Customer Pain Points
- **Complaint 1:** What users struggle with + test to prevent
- **Complaint 2:** Common frustration + how to verify we solve it
### Recommended Test Coverage
- [ ] Test case for problem 1
- [ ] Test case for competitor parity
- [ ] Test case for customer pain point
---
_This research informs both manual tests (ln-522) and automated tests (ln-523)._
MANDATORY READ: Load references/test_planning_summary_contract.md, references/test_planning_worker_runtime_contract.md
Runtime profile:
test-planning-workerln-521test-planning-workerworker, status, warnings, research_comment_pathInvocation rules:
runId and summaryArtifactPathrunId and exact summaryArtifactPathOutput: Tracker comment with research findings for ln-522 and ln-523 to use.
references/research_tool_fallback.mdVersion: 1.0.0 Last Updated: 2026-01-15