Generate observable test criteria for requirements with versioned storage.
npx skills add https://github.com/x85446/claudecodetricks --skill pm-test
Please help me install this Agent Skill. Skill: pm-test Source: https://github.com/x85446/claudecodetricks/tree/main/skills/pm-test Command: npx skills add https://github.com/x85446/claudecodetricks --skill pm-test
Write human-readable test criteria for requirements. No code, no pseudocode — only observable outcomes. Iterator-native, succinct, imperative mood.
Provide a requirement UUID and choose a mode to generate iterator-driven, observable tests.
High-intent search queries and answers about installing and using this skill.
To write observable test criteria for product requirements without code, generate human-readable, verifiable outcomes using imperative mood. This approach focuses on pass/fail metrics and traces rather than pseudocode, ensuring verifiable quality through succinct, iterator-native test definitions.
Observable test criteria in product management are verifiable outcomes like pass/fail results or metrics that validate requirement quality. You need them during requirement crawling or feature addition to ensure every iterator-driven item has clear, code-free verification standards before development.
To generate test criteria from existing feature requirements, use Add From Feature mode by providing a requirement UUID. This extracts iterator-driven, observable test cases and stores them with versioning in product_feature_tests for continuous interactive refinement.
Yes, you can reference iterators by name when writing requirement test cases. This iterator-native voice ensures complete coverage across related items within product_feature_tests, maintaining verifiable quality standards throughout the crawling and interactive refinement workflows.
The best way to refine test criteria after initial generation is using Interact Mode and Edit mode workflows. These allow iterative adjustments to the observable outcomes while enforcing the iterator-native voice and maintaining versioning within the product_feature_tests store.
Requirement tests fail verification during crawling when they lack observable outcomes or proper iterator references. Ensure tests are written in imperative mood with clear pass/fail metrics, stored via versioning in product_feature_tests, and reference iterators by name for complete coverage.
mahg-esGenerate traceable test cases from requirements and user stories.
semicolon-devteamRun Gradle tests for Spring Boot Kotlin projects and generate JaCoCo coverage reports.
xingranyaGather, analyze, and document product requirements into PRD files.
DavidsonGomesGenerate end-to-end QA test suites from feature specs and acceptance criteria.
