plan-test-modify

Update test case IDs and statuses in test plan documents.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/oogDZ/2 --skill plan-test-modify
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan-test-modify
Source: https://github.com/oogDZ/2/tree/main/.claude/skills/plan-test-modify
Command: npx skills add https://github.com/oogDZ/2 --skill plan-test-modify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a standardized way to modify an existing test plan document by updating test case IDs (TC-N), resolving status markers, transitioning DRAFT states to WAITING, and handling conflicts. It helps teams keep test plans synchronized with the SSOT and reduces manual, error-prone edits.

Core Features & Use Cases

  • Update TC-N and statuses in test plan documents to reflect latest changes.
  • Resolve markers and transitions between DRAFT and WAITING to align with release workflows.
  • Use Case: When a test plan needs a quick revision across specs, this skill standardizes the edit process and ensures consistency.

Quick Start

Выполните /plan-test-modify <путь> [--status WAITING] для указания пути к документу плана тестов.

Frequently Asked Questions about plan-test-modify

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

FAQPage Schema
How do I update test case statuses in a test plan document?▼

You can update test case statuses in a test plan document by executing a modification command with the file path and an optional --status flag set to WAITING to enforce state transitions.

What is the best way to transition a draft test plan to WAITING status?▼

The best way to transition a draft test plan to WAITING status is by applying a standardized document modification workflow that enforces an optional --status flag to control the state shift.

How do you synchronize test plan revisions with the SSOT?▼

You synchronize test plan revisions with the SSOT by applying standardized edits to update test case IDs and resolve markers, ensuring coordinated consistency across specifications.

Can I resolve status markers in test plans using a single command?▼

Yes, you can resolve status markers in test plans using a single command that targets the document path, standardizes the edit process, and handles conflicts to align with release workflows.

How do I modify existing TC-N identifiers across test plan specifications?▼

To modify existing TC-N identifiers across test plan specifications, run a document modification workflow that updates the test case IDs and ensures consistency without manual error-prone edits.