mao-pm-apex

QA-as-a-Service discovery — quality maturity assessment (TMMi), test coverage analysis, tool landscape evaluation, PITT methodology alignment, team composition modeling, test factory design, and QA transformation roadmap. Use when the user asks to "assess QA maturity", "evaluate testing practices", "QA service discovery", "test factory design", "TMMi assessment", "QA transformation", "testing maturity evaluation", "PITT methodology", "QA team composition", "test automation assessment", "quality engineering assessment", or mentions "independent testing", "QA-as-a-Service", "test industrialization", "ISTQB".

Strategic quality engineering framework covering test strategy, automation architecture, quality gates, metrics, and shift-left practices. Use when the user asks to "design test strategy", "plan quality gates", "set up test automation", "assess quality maturity", "define quality metrics", or mentions "test pyramid", "shift-left", "CI/CD quality", "automation architecture", "quality engineering".

Release management approach design, deployment pattern selection (blue-green, canary, rolling), and rollback procedure definition. Use when the user asks to "design release strategy", "define deployment patterns", "plan rollback procedures", or mentions trunk-based development, GitFlow, feature flags, or CI/CD pipeline strategy.

Proactive risk controller and financial vigilance — operates as an anxious CPA/PM hybrid that anticipates worst-case scenarios at every discovery step, stress-tests assumptions, tracks risk exposure, and feeds better insights back into each phase. Use when the user asks to "assess risks", "stress-test the plan", "validate assumptions", "run worst-case analysis", "check what could go wrong", "audit the discovery", or mentions risk register, contingency planning, assumption validation, exposure analysis, risk appetite, worst-case scenarios, financial controls, or "what keeps you up at night". The paranoid voice that makes the discovery reliable and the proposal trustworthy.

Execution roadmap generator with sprint breakdown, prerequisites, gates, team/budget, and risk register. Use when the user asks to "create a roadmap", "plan a PoC", "build sprint plan", "execution timeline", or mentions "proof of concept", "MVP plan", "milestones", "sprint breakdown", "iteracion", "go/no-go".

RPA and process automation discovery — process landscape assessment, automation opportunity scoring, bot design architecture, platform evaluation, process mining, ROI projection, and automation roadmap. Use when the user asks to "evaluate RPA readiness", "assess automation opportunities", "process automation discovery", "bot architecture design", "RPA platform comparison", "automation roadmap", "process mining analysis", "identify automation candidates", "RPA ROI analysis", or mentions "robotic process automation", "attended/unattended bots", "automation CoE", "process digitization".

Evaluates 3+ modernization scenarios using Tree of Thought with 6-dimension weighted scoring. Use when the user asks to "compare scenarios", "evaluate options", "run scenario analysis", "Tree of Thought", "which approach should we take", "compare architectures", or mentions "Phase 3", "strategic analysis", "trade-off analysis", "SWOT comparison".

Industry/sector intelligence analysis — context-adaptive expert that provides sector-specific insights, regulatory context, benchmarks, and risk overlays. Replaces former dynamic-sme. Use when the user asks to "add industry context", "analyze sector", "give me the banking/retail/health perspective", or mentions "sector intelligence", "industry analysis", "industry lens", "sector analysis", "regulatory context".

Security architecture design — threat modeling, zero trust, identity, encryption, compliance. Use when the user asks to "design security architecture", "model threats", "implement zero trust", "design IAM", "plan encryption strategy", "map compliance requirements", or mentions STRIDE, OWASP, OAuth, RBAC, SOC2, ISO27001, PCI-DSS.

SLO/SLA/SLI definition — error budget policies, reliability targets, customer-facing commitments. Use when the user asks to "define SLAs", "design SLOs", "set reliability targets", "create error budget policy", or mentions SLI, service level, uptime, nines, error budgets.

Software architecture design — modules, layers, boundaries, design patterns, ADRs, quality attributes, and technical debt strategy. Use when the user asks to "design the internal structure", "define module boundaries", "select architecture patterns", "document architecture decisions", "evaluate code architecture", or mentions CQRS, Hexagonal, Event Sourcing, Clean Architecture, ADRs, or technical debt.

Software and technology viability validator — deep forensic analysis of whether proposed software solutions, AI/ML components, and technology choices are viable substance or speculative smoke. Covers service viability, platform viability, methodology viability, tool viability, and vendor assessment for any service type. Use when the user asks to "validate technology viability", "detect vaporware", "verify AI claims", "assess software maturity", "check if this tech actually works", or mentions technology due diligence, software validation, AI feasibility, vendor evaluation, or tech-stack viability. This is the devoted software-specific validator — separate and more critical than the multidimensional feasibility analysis.

Complete transformation roadmap with phased execution, investment horizon, team ramp-up, risk-adjusted timeline, and estimation pivot points. Use when the user asks to "create a roadmap", "plan the transformation", "build an investment case", "team sizing", "risk-adjusted timeline", or mentions "Phase 4", "solution roadmap", "transformation plan", "phased execution", "PoC validation criteria", "kill criteria", "go/no-go gates".

End-to-end solution design — system integration, channel orchestration, identity management, observability, and cross-cutting concerns. Use when the user asks to "design the full solution", "integrate multiple systems", "plan API gateway strategy", "define identity and security architecture", "set up observability", or mentions C4 containers, BFF, Zero Trust, SLI/SLO, circuit breaker, or migration planning.

Staff augmentation discovery — talent gap analysis, skills matrix profiling, team composition modeling, onboarding and ramp-up design, retention framework, and staffing roadmap. Use when the user asks to "assess staffing needs", "analyze talent gaps", "design team composition", "plan staff augmentation", "evaluate team skills", "create staffing roadmap", "onboarding plan", "ramp-up strategy", "retention framework", or mentions talent gap, skills matrix, team topology, augmentation, nearshore, offshore, or staffing plan.

Stakeholder analysis — influence/interest matrix, communication plan, RACI, change readiness. Use when the user asks to "map stakeholders", "build influence matrix", "create communication plan", "assign RACI", "assess change readiness", "identify champions", or mentions stakeholder analysis, power/interest grid, engagement strategy, or adoption curve.

Narrative arc design and transformation metodologia-storytelling for discovery deliverables. Use when structuring the overall narrative across deliverables, building scenario narratives, crafting transformation stories (current pain → decision → future state), or designing risk narratives and success reference stories.

Green IT evaluation, carbon footprint estimation, energy efficiency analysis, and sustainable architecture pattern recommendations. Use when the user asks to "assess sustainability", "estimate carbon footprint", "evaluate green IT", or mentions energy efficiency, sustainable architecture, or environmental impact of technology.

Conway's Law analysis, team interaction modes, cognitive load assessment, organizational design. Use when the user asks to "design team structure", "assess cognitive load", "map team interactions", "apply Conway's Law", or mentions stream-aligned teams, platform teams, enabling teams, team-first thinking.

Technical debt quantification, debt quadrant classification (reckless/prudent x deliberate/inadvertent), remediation prioritization, and paydown roadmap generation. Use when the user asks to "assess technical debt", "quantify debt", "classify tech debt", "prioritize remediation", or mentions debt inventory, impact scoring, or paydown planning.