microshift-dev:add-enhancement

A MicroShift enhancement proposal requires structuring your feature description into a compliant template fetched from the openshift/enhancements repository. It must include Summary, Motivation, User Stories, and workflow descriptions, while applying required conventions like feature-gate guidance to ensure alignment with OpenShift process standards.

To draft a MicroShift feature proposal with JIRA tracking, you provide your title, description, and JIRA link to generate a full enhancement draft. The generated file automatically inserts TODO placeholders for unconfirmed testing plans, graduation criteria, and feature gates, prompting you to fill in missing details before submission.

The required structure for a MicroShift enhancement proposal includes extracted what/why/who sections, Goals, Non-Goals, and MicroShift topology considerations. It generates an enhancements/microshift/<kebab-case-name>.md file that applies required conventions and provides reminders for test and graduation criteria.

Yes, you can generate an enhancement draft with unconfirmed API and feature gate details. The skill extracts confirmed information for the Summary and Motivation sections, and inserts explicit TODO placeholders for any unconfirmed API, feature gate, or testing details, prompting for later clarification.

The limitation of automating MicroShift enhancement template population is that it cannot finalize unconfirmed API, feature gate, or testing details. It handles structural compliance and initial drafting by inserting TODOs, but you must manually verify and complete these technical specifics before the proposal is ready.