Generate a Functional and Technical Specification document from TRS ticket context and approved quotes.
npx skills add https://github.com/leomleao/tct-cowork-plugin --skill fts
Please help me install this Agent Skill. Skill: fts Source: https://github.com/leomleao/tct-cowork-plugin/tree/main/plugins/assistant/skills/fts Command: npx skills add https://github.com/leomleao/tct-cowork-plugin --skill fts
Automates the creation of a complete Functional and Technical Specification (FTS) document from TRS tickets and the associated context, reducing manual drafting time and ensuring consistency with the approved quote.
Use Case: A change request with an approved quote can be transformed into an FTS draft for stakeholder review.
Provide the TICKET_ID to begin the guided FTS drafting process from the approved quote and ticket context.
High-intent search queries and answers about installing and using this skill.
To generate a functional and technical specification, you provide the TRS ticket ID to fetch ticket context and automatically draft an FTS document incorporating the approved quote and ticket notes.
You create an FTS document from a TRS ticket by supplying the ticket ID, which loads guiding documents and populates the standard TCT FTS template with the ticket data and referencing documents.
An FTS document in SAP change requests is a formal functional and technical specification that defines requirements, and is generated by consolidating approved quote details and TRS ticket context.
Yes, an approved quote is required to generate a functional and technical specification, as the quote details and ticket context are reviewed and incorporated into the cohesive FTS draft.
Yes, you can automate SAP FTS drafting by inputting the ticket ID, which fetches TRS ticket notes and existing documentation to populate the standard TCT FTS template sections automatically.
The automation relies on the TRS ticket having an approved quote and existing ticket context, meaning it cannot generate a functional and technical specification draft without these prerequisite inputs.
matteocervelliGenerate pytest and Jest unit tests with AAA structure and coverage benchmarks.
noelserdnaDocument and validate software requirements into a structured REQUIREMENTS.md using SWEBOK v4 and EARS-style statements.
orekyuuGuide code investigation, requirement elicitation, and specification document creation.
dimagiGenerate Markdown product and technical spec documents from Jira ticket IDs or URLs.
