test-planner

Create risk-ranked test plans with API, E2E, and regression manuals.

11|1|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/ylxmf2005/AgentCorp --skill test-planner-ylxmf2005
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-planner
Source: https://github.com/ylxmf2005/AgentCorp/tree/main/agentcorp/test-planner
Command: npx skills add https://github.com/ylxmf2005/AgentCorp --skill test-planner-ylxmf2005

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This tool helps teams create risk-ranked, executable TestPlans before coding, preventing omissions and improvisation during validation.

Core Features & Use Cases

  • Plan creation: generate a complete TestPlan set (test-plan.md plus api/e2e/regression manuals) aligned to the project testing-context.
  • Risk-driven verification: rank risks, define Must-Haves and gates, and specify evidence and acceptance criteria.
  • Reusable artifacts: provide templates and guidance to support future planning and audits.

Quick Start

Create a ready-to-run plan by populating test/test-plan.md and the three execution manuals under test/ with references to teamspace/testing-context.md.

Frequently Asked Questions about test-planner

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

FAQPage Schema
How do I create a risk-ranked test plan from confirmed requirements before coding?▼

To create a risk-ranked test plan, populate test/test-plan.md and execution manuals under test/ with references to teamspace/testing-context.md, enforcing frontmatter metadata and template-driven structure for repeatable QA workflows.

What is the best way to structure executable manuals for API, E2E, and regression checks?▼

Executable manuals for API, E2E, and regression checks are structured using template-driven files under the test/ directory, ensuring they reference the project testing context and specify evidence and acceptance criteria.

How does risk-driven test planning prevent omissions during validation?▼

Risk-driven test planning prevents omissions by ranking risks, defining Must-Haves and gates, and specifying evidence and acceptance criteria before implementation, ensuring improvisation is eliminated during the QA process.

Can I use this test planning approach to generate reusable artifacts for future audits?▼

Yes, this approach generates reusable artifacts by providing templates and guidance that enforce frontmatter metadata, supporting future planning and audits through reviewable and repeatable QA workflows.

Do I need a specific testing context document to enforce a template-driven test plan?▼

Yes, you need a teamspace/testing-context.md document to align the test-plan.md and execution manuals, ensuring the generated plans reference the correct project testing context.

What are the limitations of using template-driven test plans for QA workflows?▼

Template-driven test plans require confirmed requirements before implementation and rely on strict frontmatter metadata enforcement, meaning unconfirmed or rapidly changing requirements may disrupt the generated QA workflows.