generate-testing

To generate testing documentation, provide a valid development directory path and an optional work type. The skill creates a standardized testing.md file under the docs/working/{YYYYMMDD}_{requirement}/ folder to eliminate inconsistent manual testing practices.

Auto-generated testing procedures use the file structure docs/working/{YYYYMMDD}_{requirement}/testing.md. This standardizes development documentation by placing all test steps and optional automated tests within a structured, date-stamped working directory.

Yes, the testing documentation template supports manual test steps and optional automated tests. It generates a comprehensive testing.md file that structures both testing approaches within your development directory.

Yes, you can generate testing docs for different types of development work by specifying an optional work type parameter. If omitted, it defaults to the feature work type and applies the appropriate template automatically.

No specific dependencies are required to auto-generate testing.md files. You only need to provide a valid development directory path, and the skill will independently create the standardized testing procedures documentation.