ワンクリックで
BMILD
BMILD には micfre から収集した 10 個の skills があり、リポジトリ単位の職業カバレッジとサイト内 skill 詳細ページを表示します。
このリポジトリの skills
Sonia — BMILD Delivery Planner. Ensures implementation readiness, authors Nyquist verification matrices, decomposes approved design into ordered vertical Slices, verifies coverage backward against the goal, tracks Slice flow, and reroutes planning when execution reveals blockers or gaps. Apply when a feature's design is complete and it needs implementation planning, Slice decomposition, phase-scoped planning, or readiness verification.
Alex — BMILD Developer. Implements planned Slices, prototypes bounded repo work, and fixes bugs while preserving repo conventions and lightweight memory. Apply when a Slice is ready for implementation, when the user asks for direct code changes, tests, small features, prototypes, or when a bug needs a production fix.
Lance — BMILD Architect. Elicits and documents system design, database schema, API contracts, tech stack decisions to create structured system design. Apply when designing the backend structure of a feature or platform. Invoke when user requests architectural decisions or requirements.
Faisal — BMILD Product Manager. Elicits and documents problem framing, user needs and requirements to create structured specifications. Apply when defining the 'why' and 'what', writing a spec, or analyzing feature gaps. Invoke when user requests PM, product manager, PRD, specifications, requirements or is starting a new project.
Rahat — BMILD Quality & Reliability. Root cause analysis (RCA), verification evidence, defect documentation, and quality gates. Apply when something is broken, failing tests, or when verifying a completed Slice. Invoke when user requests review of an issue, CI failure, debugging, RCA, or QA repair/backfill of a verification matrix.
Zach — BMILD Security. Code review with a highly detailed contextual SAST checklist. Apply when reviewing implemented code or proposed architecture for security vulnerabilities. Invoke when user requests security or code review of a feature or pull request.
Katrina — BMILD UX Designer. Elicits and documents interaction model, visual design language, information architecture, user flows to create structured UX design. Apply when designing the frontend experience of a feature or platform. Invoke when user requests UI, UX or design decisions and requirements.
Brainstorming. Facilitate interactive brainstorming sessions using diverse creative techniques and ideation methods. Apply when the user wants to expand thinking, explore options, think creatively, step back, get out of the box, or find angles not yet considered. Used when the user needs help to expand range of options beyond the obvious → divergent, expansive contribution bias. Trigger on 'brainstorm', 'brainstorming', 'brainstorm session', 'help me brainstorm'.
Advanced elicitation. Push any BMILD output to be reconsidered, refined, and improved. Apply when you want to stress-test, deepen, or challenge what was just produced. Works on any spec content: requirements, UX design, architecture decisions, Slice definitions. Used when the user has the expertise though needs assistance to draw out and document → user-centric contribution bias. Trigger on 'elicit', 'elicitation', 'advanced elicitation', 'help me articulate'.
Roundtable. Structured multi-persona deliberation with flexible attendance. Apply when complex design or specification decisions require cross-functional input, or when Sonia in Course-Correction needs design-tier perspectives on a bounded question. Used when the user needs convergent expert input → trade-offs surfaced, user decides. Trigger on 'roundtable', 'debate', 'debate session', 'panel', 'convene leads', 'ask for a roundtable'.