architect-design
enggenie:architect-design
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:architect-design 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
More from badrusiddique/enggenie-skill
dev-implement
Use when executing an implementation plan task-by-task - dispatches subagents for implementation, manages git worktrees, handles phased multi-service deployment
10review-design
Use when reviewing frontend implementation against design specs - design system compliance, responsive behavior, accessibility audit
10dev-tdd
Use when writing any code - enforces test-driven development discipline with RED-GREEN-REFACTOR cycle, fires during any coding task
9architect-plan
Use when creating implementation plans from specs or requirements - phased task breakdown with deployment readiness gates before any coding begins
9review-code
Use when requesting or receiving code review - dispatches reviewer subagent or processes human PR feedback with technical evaluation
9memory-recall
Use when asking about previous sessions - cross-session context search via claude-mem with token-efficient 3-layer retrieval
9