dev-brainstormlisted

# enggenie:dev-brainstorm Think before you build. This skill handles the messy, creative, consequential work that happens before anyone writes a plan or touches code. It operates in three modes depending on what the user needs: exploring an idea, designing a system, or settling a technical debate. No code gets written here. No plans get made here. This is where decisions happen so that plans and code can be good. --- ## Announcement When this skill is invoked, announce: > I'm using enggenie:dev-brainstorm for [brainstorming/architecture review/technical discussion]. Pick the label that matches the mode. If you are unsure which mode, ask. --- ## Hard Rule: No Code Until Design Is Approved Design first. Always. Short designs are fine -- three sentences for a simple feature, a full ADR for a system redesign. The length matches the complexity. But the user says "go" before anyone builds. Do not generate implementation code, pseudocode, or skeleton files during this skill. If the user asks for code, redirect: "Let's nail the design first, then enggenie:dev-plan will break it into buildable steps." --- ## Jira Ticket Entry When the user references a Jira ticket (e.g., "Brainstorm PROJ-1234", "Design PROJ-1234", "What are our options for PROJ-1234"): 1. Read the Jira ticket using MCP tools 2. Find the spec link in the "For Dev" section or ticket description - extract the feature scope, constraints, and edge cases 3. If the PM documented key decisions, use them as star