ln-510-test-planner

Plan risk-based E2E, Integration, and Unit tests from manual testing results.

534|73|Updated Oct 24, 2025
One-click install
npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-510-test-planner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-510-test-planner
Source: https://github.com/levnikolaevich/claude-code-skills/tree/main/ln-510-test-planner
Command: npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-510-test-planner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Plans final Story tests (E2E/Integration/Unit) after manual testing results, then delegates to ln-301-task-creator.

Core Features & Use Cases

  • Auto-discovers Team ID from kanban_board.md
  • Loads Story + Tasks metadata, analyzes manual test results
  • Applies risk-based testing to select E2E/Integration/Unit tests
  • Delegates test creation to ln-301-task-creator

Quick Start

Command: Skill(command: "ln-510-test-planner")

Frequently Asked Questions about ln-510-test-planner

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

FAQPage Schema
How do I plan E2E and integration tests based on manual testing results?

Risk-based test planning analyzes your manual testing outcomes to select appropriate E2E, integration, and unit tests. After manual testing completes and all implementation tasks are done, this approach evaluates test coverage and identified risks to recommend the right test types, then generates a finalized Story task with tests, fixes, infrastructure, and documentation.

Can I automate test planning for Linear stories with risk-based prioritization?

Yes. Risk-based test planning auto-discovers your Team ID from kanban_board.md, extracts manual test results directly from Linear, analyzes coverage gaps, and automatically selects E2E, integration, and unit tests by risk priority. The result is a finalized task ready for delegation to task creation automation.

What happens after manual testing is complete—how do I decide which automation tests to run?

Risk-based testing applies structured analysis to manual results: it examines what was tested, identifies coverage gaps, and prioritizes E2E, integration, and unit tests by risk level. This ensures automation effort focuses on the highest-impact test types, reducing redundancy and accelerating story completion.

Does this work with Linear integration and existing project documentation?

Yes. The Skill integrates directly with Linear to extract manual test results and auto-discovers Team ID from your kanban_board.md project documentation. It requires manual testing results already logged in Linear and implementation tasks marked Done before planning downstream automation.

What's the difference between risk-based testing and standard test planning?

Risk-based testing prioritizes test selection by analyzing actual manual results and identifying coverage gaps—focusing automation effort on high-risk areas. Standard approaches often apply uniform test types; risk-based planning adapts the test mix (E2E, integration, unit) to your specific story's tested and untested surfaces.