propose-feature-test-plan

To generate a test plan from EARS requirements, this skill extracts REQ-* and CC-* identifiers from feature documentation and maps each to concrete test types and descriptions, producing a structured test-plan.md file.

Mapping software requirements to test types is handled by linking each REQ-* and CC-* identifier to a specific category, such as unit, integration, not-testable, or out-of-scope, accompanied by a concise test description.

Yes, you need existing feature documentation containing EARS requirements and Critical Constraints. The skill extracts these prerequisite REQ-* and CC-* identifiers to generate the formal test plan.

Traceability between feature requirements and verification tests is established by directly linking each REQ-* and CC-* identifier to a specific test type and description within the generated test-plan.md document.

The generated test plan document is saved as a ready-to-commit file at ./docs/features/NNNN-feature-name/test-plan.md, aligning with standard project workflows and feature development directories.

Yes, you can mark requirements as out-of-scope or not-testable. The skill maps each requirement to a test type, explicitly including unit, integration, not-testable, and out-of-scope categories.