Extract unit test coverage from quotes and FTS to draft a UTD.
npx skills add https://github.com/leomleao/tct-cowork-plugin --skill unittest
Please help me install this Agent Skill. Skill: unittest Source: https://github.com/leomleao/tct-cowork-plugin/tree/main/plugins/assistant/skills/unittest Command: npx skills add https://github.com/leomleao/tct-cowork-plugin --skill unittest
This Skill automates the end-to-end creation of a complete Unit Test Document (UTD) by synthesising ticket context, the approved quote, the FTS (where available), and supporting materials into a production-ready template, reducing manual drafting time and ensuring comprehensive test coverage.
Provide the TICKET_ID and related ticket context to initiate a draft Unit Test Document.
High-intent search queries and answers about installing and using this skill.
To generate a unit test document from SAP change tickets, provide the TICKET_ID and related TRS ticket context. The Skill extracts coverage from approved quotes and FTS to draft a complete UTD with test data, edge cases, and validation steps.
A unit test document defines test scenarios, data requirements, interfaces, edge cases, and validation steps for SAP changes. It aligns with UTD templates to ensure comprehensive test coverage before final document generation and review.
Yes, you can automate UTD drafting by extracting existing test coverage from approved quotes and FTS. The Skill synthesizes this context to generate a production-ready template structured around the SAP change workflow.
The best way to define edge cases and validation steps is to load supporting references like utd-structure.md and utd-review-template.md. These materials steer content generation and ensure consistency across sessions for SAP change tickets.
Yes, you need a TICKET_ID and related ticket context to initiate a draft Unit Test Document. The Skill targets SAP change tickets and their TRS ticket context to shape tests, data requirements, and interfaces.
The unit test review step validates and refines tests using utd-review-template.md before final document generation. This ensures the UTD draft meets quality standards and handles exceptions properly across sessions.
ilandahanGenerate a technical specification from PRDs and requirements.
bacocoGenerate PRD.md and epics.md from validated discovery insights.
narcisolcfGenerate formal .docx documents from PCA data using templates and tracked changes.
dralgorhythmWrite unit, integration, and end-to-end tests using Arrange-Act-Assert patterns.
