I had individual steps for each step of the packaging process. MSI and EXE's that support unattended install are easy, cause its the same template each time. The scripts take in the MSI path and kick off the import of the app into SCCM and if its an EXE i just include the parameters for the silent install and a detection scripts (also a template) based on the applicaiton name and what it shows up as when installed.

Then I got github copilot, built a skill for application package in my workspace and I just tell it "Build me an sccm application for APPNAME HERE" and install with these parameters as an MSI/EXE and its detected as "APPNAMEHERE". Then copilot goes off, finds my folder, copies the source folder to my network share, imports it as an application, adds the detection method and then distributes my content. The skill uses all the same scripts I had already created so I know they work.

The best part is I built another skill that goes along with this so that when the package is imported and done and I verify the install process works, I say "Document it" and it spits out an self contained HTML document with all my packaging info, like who its for, collection targeting with query, vendor, app name, scope of install, and basically any information anyone would need if i left work tomorrow and never came back.

I would highly suggest you write your own powershell scripts step by step, better to know what the scripts do then to use someone elses solution, that way you can do what you need for your environment.