10x-test-plan

Orchestrates phased test rollouts by writing a stateful test-plan.md and driving research, plan, and implement phases.

Updated May 23, 2026
One-click install
npx skills add https://github.com/BMS-kmusial/bms-stream-monitor --skill 10x-test-plan-bms-kmusial
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: 10x-test-plan
Source: https://github.com/BMS-kmusial/bms-stream-monitor/tree/main/.claude/skills/10x-test-plan
Command: npx skills add https://github.com/BMS-kmusial/bms-stream-monitor --skill 10x-test-plan-bms-kmusial

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Teams investing in tests for an existing product often lack a prioritized, evidence-based strategy, leading to coverage that mirrors the PRD instead of addressing real risks. This Skill writes a durable phased test rollout document and orchestrates each phase through a research, plan, and implement chain. ## Core Features & Use Cases - Stateful rollout orchestration: Re-derives progress from which artifacts exist on disk and resumes from the next pending rollout phase on every invocation. - Evidence-based risk mapping: Combines PRD analysis, git hot-spot churn scans, test-base profiling, and a structured user interview to rank failure scenarios by impact and likelihood. - Downstream handoffs: Launches each rollout phase into /10x-new, /10x-research, /10x-plan, and /10x-implement, updating the status table in context/foundation/test-plan.md. - Use Case: A brownfield project with a PRD but no test strategy invokes the skill, answers five interview questions about feared failures, and receives a phased rollout plan covering critical-path tests, hot-spot integration tests, and quality gates. ## Quick Start Ask the assistant to create a phased test plan for this project using the 10x-test-plan skill after your PRD and roadmap exist.

Frequently Asked Questions about 10x-test-plan

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

FAQPage Schema
How do I create a phased test plan for an existing project?

Run the skill after your PRD and roadmap exist. It reads project documents, scans git hot-spots, profiles the existing test base, interviews you about feared failures, then writes context/foundation/test-plan.md with 3-5 ordered rollout phases.

How does the test rollout state machine resume progress?

Each invocation checks which artifacts exist on disk: the test-plan guide, change folders, research.md, and plan.md progress items. It then resumes from the first rollout phase whose status is not complete and hands off to the next command.

When should I not use a phased test rollout skill?

Skip it when there is no PRD, roadmap, or implemented code, since greenfield projects need product definition first. Also skip it for adding a single test to one file, which belongs to a TDD workflow rather than a rollout.

Does the test plan identify exact files where failures live?

No. The plan deliberately cites evidence such as PRD lines, interview answers, and hot-spot directories, never file or line anchors. Locating failure-owning code is delegated to the research phase of each rollout.

How do I update an existing test plan without editing it in place?

Invoke the skill with the --refresh flag. It opens a new change folder named test-plan-refresh-<date> so strategy sections are revised through the standard change process rather than edited directly.