GeorgeQLe
- 1k skills
- 0 followers
- 1 repo stars
- 3 weeks ago last updated
- ▌ Customer Discovery 8 · georgeqleOrchestrator — detect pre-product vs product-exists mode, bootstrap ICP candidates, recommend customer-discovery frameworks, synthesize outputs into unified ICP research
- ▌ Customer Discovery 9 · georgeqleOrchestrator — detect pre-product vs product-exists mode, bootstrap ICP candidates, recommend customer-discovery frameworks, synthesize outputs into unified ICP research
- ▌ Customer Discovery 10 · georgeqleOrchestrator — detect pre-product vs product-exists mode, bootstrap ICP candidates, recommend customer-discovery frameworks, synthesize outputs into unified ICP research
- ▌ Customer Discovery 11 · georgeqleOrchestrator — detect pre-product vs product-exists mode, bootstrap ICP candidates, recommend customer-discovery frameworks, synthesize outputs into unified ICP research
- ▌ UX Variations 39 · georgeqleInterview and plan multiple UX and UI variations for a product, page, or flow, including onboarding, typical workflows, sharing, collaboration, return use, and interface alternatives users can compare before locking a direction — and concrete visual/layout UI variations (component choices, spatial arrangements, information density)
- ▌ UX Variations 40 · georgeqleInterview and plan multiple UX and UI variations for a product, page, or flow, including onboarding, typical workflows, sharing, collaboration, return use, and interface alternatives users can compare before locking a direction — and concrete visual/layout UI variations (component choices, spatial arrangements, information density)
- ▌ Youtube Portfolio 6 · georgeqleMap a YouTube channel's video portfolio by archetype, strategic role, performance concentration, and cleanup or refresh opportunities
- ▌
- ▌
- ▌ Pmf Assessment 3 · georgeqleSean Ellis PMF survey design + qualitative signal analysis for post-launch fit measurement
- ▌ Platform Strategy 7 · georgeqleExpand from a single product into a multi-product platform — map vertical and horizontal growth vectors, score candidates, design validation experiments, and sequence the portfolio
- ▌ Platform Strategy 8 · georgeqleExpand from a single product into a multi-product platform — map vertical and horizontal growth vectors, score candidates, design validation experiments, and sequence the portfolio
- ▌ Platform Strategy 9 · georgeqleExpand from a single product into a multi-product platform — map vertical and horizontal growth vectors, score candidates, design validation experiments, and sequence the portfolio
- ▌ Platform Strategy 10 · georgeqleExpand from a single product into a multi-product platform — map vertical and horizontal growth vectors, score candidates, design validation experiments, and sequence the portfolio
- ▌ Platform Strategy 11 · georgeqleExpand from a single product into a multi-product platform — map vertical and horizontal growth vectors, score candidates, design validation experiments, and sequence the portfolio
- ▌ Platform Strategy 12 · georgeqleExpand from a single product into a multi-product platform — map vertical and horizontal growth vectors, score candidates, design validation experiments, and sequence the portfolio
- ▌ Platform Strategy 13 · georgeqleExpand from a single product into a multi-product platform — map vertical and horizontal growth vectors, score candidates, design validation experiments, and sequence the portfolio
- ▌ Platform Strategy 14 · georgeqleExpand from a single product into a multi-product platform — map vertical and horizontal growth vectors, score candidates, design validation experiments, and sequence the portfolio
- ▌ Platform Strategy 15 · georgeqleExpand from a single product into a multi-product platform — map vertical and horizontal growth vectors, score candidates, design validation experiments, and sequence the portfolio
- ▌ Platform Strategy 16 · georgeqleExpand from a single product into a multi-product platform — map vertical and horizontal growth vectors, score candidates, design validation experiments, and sequence the portfolio
- ▌ Assumption Tracker 2 · georgeqleExtract and risk-rank assumptions from research docs — living register of what to validate first
- ▌ Reconcile Research 2 · georgeqleCross-document consistency audit across research outputs — find contradictions, stale assumptions, and gaps
- ▌ Positioning 29 · georgeqleOrchestrator — detect market vs product mode, recommend positioning frameworks, synthesize outputs into unified positioning
- ▌ Positioning 30 · georgeqleOrchestrator — detect market vs product mode, recommend positioning frameworks, synthesize outputs into unified positioning
- ▌ Positioning 31 · georgeqleOrchestrator — detect market vs product mode, recommend positioning frameworks, synthesize outputs into unified positioning
- ▌ Positioning 32 · georgeqleOrchestrator — detect market vs product mode, recommend positioning frameworks, synthesize outputs into unified positioning
- ▌ Positioning 33 · georgeqleOrchestrator — detect market vs product mode, recommend positioning frameworks, synthesize outputs into unified positioning
- ▌ Positioning 34 · georgeqleOrchestrator — detect market vs product mode, recommend positioning frameworks, synthesize outputs into unified positioning
- ▌ Positioning 35 · georgeqleOrchestrator — detect market vs product mode, recommend positioning frameworks, synthesize outputs into unified positioning
- ▌ Positioning 36 · georgeqleOrchestrator — detect market vs product mode, recommend positioning frameworks, synthesize outputs into unified positioning
- ▌ Positioning 37 · georgeqleOrchestrator — detect market vs product mode, recommend positioning frameworks, synthesize outputs into unified positioning
- ▌ Journey Map 12 · georgeqleMap the full user and customer lifecycle from trigger and discovery through onboarding, aha, conversion, retention, expansion, and advocacy
- ▌ Journey Map 13 · georgeqleMap the full user and customer lifecycle from trigger and discovery through onboarding, aha, conversion, retention, expansion, and advocacy
- ▌ Journey Map 14 · georgeqleMap the full user and customer lifecycle from trigger and discovery through onboarding, aha, conversion, retention, expansion, and advocacy
- ▌ Journey Map 15 · georgeqleMap the full user and customer lifecycle from trigger and discovery through onboarding, aha, conversion, retention, expansion, and advocacy
- ▌ Journey Map 16 · georgeqleMap the full user and customer lifecycle from trigger and discovery through onboarding, aha, conversion, retention, expansion, and advocacy
- ▌ Journey Map 17 · georgeqleMap the full user and customer lifecycle from trigger and discovery through onboarding, aha, conversion, retention, expansion, and advocacy
- ▌ Journey Map 18 · georgeqleMap the full user and customer lifecycle from trigger and discovery through onboarding, aha, conversion, retention, expansion, and advocacy
- ▌ Journey Map 19 · georgeqleMap the full user and customer lifecycle from trigger and discovery through onboarding, aha, conversion, retention, expansion, and advocacy
- ▌ Journey Map 20 · georgeqleOrchestrator — detect pre-product vs product-exists mode, recommend journey-mapping frameworks, synthesize outputs into unified lifecycle overview
- ▌ Journey Map 21 · georgeqleOrchestrator — detect pre-product vs product-exists mode, recommend journey-mapping frameworks, synthesize outputs into unified lifecycle overview
- ▌ Journey Map 22 · georgeqleOrchestrator — detect pre-product vs product-exists mode, recommend journey-mapping frameworks, synthesize outputs into unified lifecycle overview
- ▌ Journey Map 23 · georgeqleOrchestrator — detect pre-product vs product-exists mode, recommend journey-mapping frameworks, synthesize outputs into unified lifecycle overview
- ▌ Journey Map 24 · georgeqleOrchestrator — detect pre-product vs product-exists mode, recommend journey-mapping frameworks, synthesize outputs into unified lifecycle overview
- ▌ Journey Map 25 · georgeqleOrchestrator — detect pre-product vs product-exists mode, recommend journey-mapping frameworks, synthesize outputs into unified lifecycle overview
- ▌ Design System 2 · georgeqleExtract or scan design tokens from a consolidated UI spec or existing codebase and produce a DESIGN.md file following the Google Labs Stitch format — machine-readable YAML frontmatter with prose rationale sections
- ▌ Prototype 22 · georgeqleBuild tangible, runnable prototypes from design-phase UX variation and UI branch packets — static HTML/CSS for UI projects, runnable scripts for CLI, endpoint stubs for API, or minimal configs for infra
- ▌ UI Interview 25 · georgeqleInterview page by page to define a complete UI specification, including layout, hierarchy, controls, links, spacing, sizing, responsive behavior, visual states, and implementation-ready interface details — supports a requirements-only mode that establishes data, actions, and states without locking layout or component decisions
- ▌ UI Interview 26 · georgeqleInterview page by page to define a complete UI specification, including layout, hierarchy, controls, links, spacing, sizing, responsive behavior, visual states, and implementation-ready interface details — supports a requirements-only mode that establishes data, actions, and states without locking layout or component decisions
- ▌ UI Interview 27 · georgeqleInterview page by page to define a complete UI specification, including layout, hierarchy, controls, links, spacing, sizing, responsive behavior, visual states, and implementation-ready interface details — supports a requirements-only mode that establishes data, actions, and states without locking layout or component decisions
- ▌ UI Interview 28 · georgeqleInterview page by page to define a complete UI specification, including layout, hierarchy, controls, links, spacing, sizing, responsive behavior, visual states, and implementation-ready interface details — supports a requirements-only mode that establishes data, actions, and states without locking layout or component decisions
- ▌ UI Interview 29 · georgeqleInterview page by page to define a complete UI specification, including layout, hierarchy, controls, links, spacing, sizing, responsive behavior, visual states, and implementation-ready interface details — supports a requirements-only mode that establishes data, actions, and states without locking layout or component decisions
- ▌ UI Interview 30 · georgeqleInterview page by page to define a complete UI specification, including layout, hierarchy, controls, links, spacing, sizing, responsive behavior, visual states, and implementation-ready interface details — supports a requirements-only mode that establishes data, actions, and states without locking layout or component decisions
- ▌ User Flow Map 2 · georgeqleTurn a high-level product concept, positioned goal, or goal sequence into screen flow structure with entry points, decisions/actions/states, branches, failure paths, and low-fidelity wireframe guidance before UI/spec/prototype work
- ▌ User Flow Map 3 · georgeqleTurn a high-level product concept, positioned goal, or goal sequence into screen flow structure with entry points, decisions/actions/states, branches, failure paths, and low-fidelity wireframe guidance before UI/spec/prototype work
- ▌ User Flow Map 4 · georgeqleTurn a high-level product concept, positioned goal, or goal sequence into screen flow structure with entry points, decisions/actions/states, branches, failure paths, and low-fidelity wireframe guidance before UI/spec/prototype work
- ▌ User Flow Map 5 · georgeqleTurn a high-level product concept, positioned goal, or goal sequence into screen flow structure with entry points, decisions/actions/states, branches, failure paths, and low-fidelity wireframe guidance before UI/spec/prototype work
- ▌ User Flow Map 6 · georgeqleTurn a high-level product concept, positioned goal, or goal sequence into screen flow structure with entry points, decisions/actions/states, branches, failure paths, and low-fidelity wireframe guidance before UI/spec/prototype work
- ▌ User Flow Map 7 · georgeqleTurn a high-level product concept, positioned goal, or goal sequence into screen flow structure with entry points, decisions/actions/states, branches, failure paths, and low-fidelity wireframe guidance before UI/spec/prototype work
- ▌ User Flow Map 8 · georgeqleTurn a high-level product concept, positioned goal, or goal sequence into screen flow structure with entry points, decisions/actions/states, branches, failure paths, and low-fidelity wireframe guidance before UI/spec/prototype work
- ▌ User Flow Map 9 · georgeqleTurn a high-level product concept, positioned goal, or goal sequence into screen flow structure with entry points, decisions/actions/states, branches, failure paths, and low-fidelity wireframe guidance before UI/spec/prototype work
- ▌ User Flow Map 10 · georgeqleTurn a high-level product concept, positioned goal, or goal sequence into screen flow structure with entry points, decisions/actions/states, branches, failure paths, and low-fidelity wireframe guidance before UI/spec/prototype work
- ▌ User Flow Map 11 · georgeqleTurn a high-level product concept, positioned goal, or goal sequence into screen flow structure with entry points, decisions/actions/states, branches, failure paths, and low-fidelity wireframe guidance before UI/spec/prototype work
- ▌ UX Variations 2 · georgeqleInterview and plan multiple UX and UI variations for a product, page, or flow, including onboarding, typical workflows, sharing, collaboration, return use, and interface alternatives users can compare before locking a direction — and concrete visual/layout UI variations with UAT before consolidation
- ▌ Branch Lifecycle 2 · georgeqleEvaluate feature branches and decide whether to merge, salvage, keep open, or delete based on branch health, PR status, and stale-branch heuristics
- ▌
- ▌
- ▌ Growth Model 3 · georgeqleReforge-style growth loop design — acquisition, retention, and monetization loops
- ▌ Growth Model 4 · georgeqleReforge-style growth loop design — acquisition, retention, and monetization loops
- ▌ Growth Model 5 · georgeqleReforge-style growth loop design — acquisition, retention, and monetization loops
- ▌ Landing Copy 3 · georgeqleGenerate or audit landing page copy grounded in upstream research — hero, benefits, social proof, pricing, FAQ, and CTAs
- ▌ Monetization 3 · georgeqleResearch-driven monetization strategy — revenue models, pricing architecture, unit economics, and packaging grounded in ICP and competitive data
- ▌ Monetization 4 · georgeqleResearch-driven monetization strategy — revenue models, pricing architecture, unit economics, and packaging grounded in ICP and competitive data
- ▌ Monetization 5 · georgeqleResearch-driven monetization strategy — revenue models, pricing architecture, unit economics, and packaging grounded in ICP and competitive data
- ▌ Monetization 6 · georgeqleResearch-driven monetization strategy — revenue models, pricing architecture, unit economics, and packaging grounded in ICP and competitive data
- ▌ Monetization 7 · georgeqleResearch-driven monetization strategy — revenue models, pricing architecture, unit economics, and packaging grounded in ICP and competitive data
- ▌ Investor Update 3 · georgeqleGenerate structured monthly stakeholder update from current research state, metrics, roadmap, and feedback
- ▌
- ▌
- ▌ Positioning 2 · georgeqleStrategic positioning (April Dunford style) — competitive alternatives, unique attributes, value, target segment, market category
- ▌ Positioning 3 · georgeqleStrategic positioning (April Dunford style) — competitive alternatives, unique attributes, value, target segment, market category
- ▌ Positioning 4 · georgeqleStrategic positioning (April Dunford style) — competitive alternatives, unique attributes, value, target segment, market category
- ▌ Positioning 5 · georgeqleStrategic positioning (April Dunford style) — competitive alternatives, unique attributes, value, target segment, market category
- ▌ Positioning 6 · georgeqleStrategic positioning (April Dunford style) — competitive alternatives, unique attributes, value, target segment, market category
- ▌ Positioning 7 · georgeqleStrategic positioning (April Dunford style) — competitive alternatives, unique attributes, value, target segment, market category
- ▌ Positioning 8 · georgeqleParent router — detect market vs product mode, recommend positioning frameworks, synthesize outputs into unified positioning
- ▌ Positioning 9 · georgeqleOrchestrator — detect market vs product mode, recommend positioning frameworks, synthesize outputs into unified positioning
- ▌ Positioning 10 · georgeqleOrchestrator — detect market vs product mode, recommend positioning frameworks, synthesize outputs into unified positioning
- ▌ Regression Check 4 · georgeqleRun a comprehensive health check across the monorepo after completing a phase or major change
- ▌ Uat Guide 2 · georgeqleExpand a UAT journey into click-by-click tester instructions, then update the result log on completion
- ▌ Design System 3 · georgeqleExtract or scan design tokens from a consolidated UI spec or existing codebase and produce a DESIGN.md file following the Google Labs Stitch format — machine-readable YAML frontmatter with prose rationale sections
- ▌ Prototype 31 · georgeqleBuild tangible, runnable prototypes from design-phase UX variation and UI branch packets — static HTML/CSS for UI projects, runnable scripts for CLI, endpoint stubs for API, or minimal configs for infra
- ▌ UI Interview 35 · georgeqleInterview page by page to define a complete UI specification, including layout, hierarchy, controls, links, spacing, sizing, responsive behavior, visual states, and implementation-ready interface details — supports a requirements-only mode that establishes data, actions, and states without locking layout or component decisions
- ▌ UI Interview 36 · georgeqleInterview page by page to define a complete UI specification, including layout, hierarchy, controls, links, spacing, sizing, responsive behavior, visual states, and implementation-ready interface details — supports a requirements-only mode that establishes data, actions, and states without locking layout or component decisions
- ▌ UI Interview 37 · georgeqleInterview page by page to define a complete UI specification, including layout, hierarchy, controls, links, spacing, sizing, responsive behavior, visual states, and implementation-ready interface details — supports a requirements-only mode that establishes data, actions, and states without locking layout or component decisions
- ▌ UI Interview 38 · georgeqleInterview page by page to define a complete UI specification, including layout, hierarchy, controls, links, spacing, sizing, responsive behavior, visual states, and implementation-ready interface details — supports a requirements-only mode that establishes data, actions, and states without locking layout or component decisions
- ▌ UI Interview 39 · georgeqleInterview page by page to define a complete UI specification, including layout, hierarchy, controls, links, spacing, sizing, responsive behavior, visual states, and implementation-ready interface details — supports a requirements-only mode that establishes data, actions, and states without locking layout or component decisions
- ▌ UI Interview 40 · georgeqleInterview page by page to define a complete UI specification, including layout, hierarchy, controls, links, spacing, sizing, responsive behavior, visual states, and implementation-ready interface details — supports a requirements-only mode that establishes data, actions, and states without locking layout or component decisions
- ▌ User Flow Map 12 · georgeqleTurn a high-level product concept, positioned goal, or goal sequence into screen flow structure with entry points, decisions/actions/states, branches, failure paths, and low-fidelity wireframe guidance before UI/spec/prototype work
- ▌ User Flow Map 13 · georgeqleTurn a high-level product concept, positioned goal, or goal sequence into screen flow structure with entry points, decisions/actions/states, branches, failure paths, and low-fidelity wireframe guidance before UI/spec/prototype work