change-request-generator

To generate a structured change request, provide a user prompt describing the desired change. The Skill automates turning feature requests into a standardized CR file with clear scope and acceptance criteria.

Standardizing backlog items is achieved by applying this Skill to feature requests or compliance requirements. It produces a standardized CR file in the issues directory with actionable details across workstreams.

The clarification process uses interactive prompts to resolve ambiguities in user descriptions. It presents A/B/C options during change request generation to ensure the resulting CR file contains clear and accurate details.

Yes, you can use this Skill to automate change request documents for compliance requirements. It transforms these inputs into structured backlog items with actionable details and clear acceptance criteria.

Generated change request files are stored in the issues directory. They are saved using a standardized naming convention as markdown files with a CR number and title.

No external dependencies are required to create structured change requests. The Skill operates independently using a built-in template to produce the final markdown output file.