ln-521-test-researcher

Researches problems, competitor solutions and customer complaints for test planning, posting findings as Linear comments.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/0xtaoist/taogate --skill ln-521-test-researcher-0xtaoist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-521-test-researcher
Source: https://github.com/0xtaoist/taogate/tree/main/ln-521-test-researcher
Command: npx skills add https://github.com/0xtaoist/taogate --skill ln-521-test-researcher-0xtaoist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Researches real-world problems, competitor solutions, and customer complaints before test planning to ensure tests cover actual user pain points, not just AC.

Core Features & Use Cases

  • Discovery-driven planning: gathers insights from real users, competitors, and forums to shape test scope.
  • Downstream alignment: informs ln-522 (Test Researcher) and ln-523 (Auto Test Planner) with structured findings.
  • Documentation-driven QA: posts findings to Linear as comments, preserving audit trails for QA reviews.

Quick Start

Run ln-521-test-researcher at the start of a test planning session to gather evidence-backed pain points for the story ln-520.

Frequently Asked Questions about ln-521-test-researcher

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I research customer complaints and competitor solutions before test planning?

Gather real-world problems, competitor solutions, and customer complaints before test planning to ensure tests cover actual user pain points. This discovery-driven approach uses real user insights to shape test scope beyond standard acceptance criteria.

Why should I research real user pain points instead of just testing acceptance criteria?

Researching real user pain points ensures tests cover actual problems customers face, not just theoretical acceptance criteria. Gathering competitor solutions and customer complaints reveals edge cases that standard test planning frequently misses.

How do I document quality assurance findings as comments in Linear?

Document quality assurance findings as comments in Linear to preserve audit trails for QA reviews. Posting research results directly as story comments keeps real-world problem evidence visible without altering the current story status.

Can I use discovery-driven test planning to inform downstream test generation skills?

Use discovery-driven test planning to inform downstream test generation skills with structured findings. Researching real-world problems and competitor solutions at the start of the pipeline provides evidence-backed pain points that align subsequent test planning and automation tasks.

Does posting research findings to Linear change the story status?

Posting research findings to Linear does not change the story status. The skill operates by adding comments only, preserving the current workflow state while maintaining a documentation-driven QA audit trail for review.

What is the best way to align test scope with actual user pain points?

Align test scope with actual user pain points by researching real-world problems, competitor solutions, and customer complaints before planning. Gathering evidence-backed insights from real users and forums ensures tests target genuine issues rather than assumed requirements.