issue-qa-doc

Auto-generate QA documentation by feeding test results, issues, and remediation actions into the skill. It structurally organizes outcomes into a concise, shareable markdown document with consistent sections for summary, environment, and verification.

Structuring a QA report requires organizing test outcomes, issues, and actions into defined sections like summary, environment, test scope, scenarios, and verification. This approach ensures a comprehensive document ready for stakeholder review and archival.

Yes, consistent QA document generation requires a defined schema and frontmatter including issue severity, category, status, assignee, and due date to ensure structured storage and uniform formatting across diverse issue types.

Include evidence and verification steps in automated QA reporting by feeding them into the skill alongside test outcomes. It handles diverse issue types and remediation actions, structuring them into the verification section of the final document.

Automated QA reporting applies to QA projects across both software and systems testing. It handles diverse issue types, evidence, and verification steps, structuring them into a concise document for stakeholder review after sprint passes.