mao-discovery-framework

Technical fact-checking and multidimensional feasibility analysis — validates claims, assumptions, and technical decisions from scenario analysis against evidence. Use when the user asks to "validate feasibility", "fact-check the scenario", "verify technical claims", "run feasibility analysis", "stress-test the approach", or mentions technical due diligence, feasibility study, risk validation, or "Phase 3b" verification work.

Technical documentation precision — progressive disclosure, terminology consistency, evidence attribution, and reproducible analysis. Use when writing AS-IS analyses, functional specs, architecture documents, handover guides, or any deliverable requiring technical rigor and documentation standards.

Structured technology monitoring across analyst firms (Gartner, Forrester, IDC), academic sources (Stanford HAI, IEEE, ACM), editorial platforms (O'Reilly Radar, ThoughtWorks Tech Radar), and individual thought leaders (Martin Fowler, Paulo Caroli, Gregor Hohpe, Jez Humble). Produces vigilance reports with signals classified by urgency and impact. Use when evaluating technology trends, preparing sector-specific tech intelligence, validating technology choices against current landscape, or when "vigilancia tecnológica", "tech watch", "Gartner", "Forrester", "tech radar", "Stanford HAI", "IEEE", or "tendencias tecnológicas" is mentioned.

Test strategy design — pyramid, automation, E2E, contract testing, shift-left, test data management, QA-as-a-service strategy, test factory design, PITT methodology, QA CoE design. Use when the user asks to "design test strategy", "build test automation", "implement contract testing", "manage test data", "define quality gates", or mentions test pyramid, Pact, Playwright, Cypress, coverage targets, flaky tests, chaos engineering.

End-user advocate that evaluates deliverable clarity, cognitive load, accessibility, adoption risks, and biases. Use when the user asks to "review for clarity", "check readability", "evaluate from user perspective", "assess adoption risk", or mentions "user representative", "voice of the user", "representante del usuario", "clarity review", "cognitive load check".

UX/UI design discovery — design maturity assessment, design system inventory, user research capability evaluation, usability baseline, information architecture assessment, design process governance, and design transformation roadmap. Use when the user asks to "evaluate design maturity", "assess UX capability", "audit design system", "usability assessment", "information architecture review", "design ops evaluation", "UX transformation plan", or mentions "design discovery", "UX readiness", "design governance".

UX writing and document accessibility standards for technical deliverables. Use when the user asks to "improve readability", "fix information hierarchy", "reduce cognitive load", "write microcopy", "check readability score", or mentions "UX writing", "scanability", "Flesch-Kincaid", "escritura UX", "legibilidad", "cognitive load".

Vendor evaluation and selection framework — RFP/RFI design, scoring matrices, TCO analysis, contract risk. Use when the user asks to "evaluate vendors", "design RFP", "compare platforms", "assess TCO", or mentions vendor selection, build-vs-buy, technology evaluation, procurement strategy.

Workshop design methodology — event storming, impact mapping, user story mapping, design sprints. Replaces former workshop-facilitator (facilitation is the agent's job, design is the skill). Use when the user asks to "design a workshop", "plan event storming", "design impact mapping session", "design a sprint", "create user story map", "design discovery session", or mentions workshop design, design sprint, event storming, story mapping, or collaborative design.

Workshop design — event storming, impact mapping, user story mapping, design sprints. Use when the user asks to "plan a workshop", "run event storming", "facilitate impact mapping", "design a sprint", "create user story map", "facilitate discovery session", or mentions workshop facilitation, design sprint, event storming, story mapping, or collaborative design.

BPMN 2.0 process modeling and analysis skill for AS-IS/TO-BE business process documentation, bottleneck identification, automation opportunity assessment, process maturity scoring, and process improvement design. Use whenever the user mentions process mapping, BPMN, business process, process flow, swimlane, AS-IS process, TO-BE process, process improvement, operational workflow, delivery monitoring, process maturity, or needs to model how work flows through an organization. Especially relevant for SAP fit-to-standard workshops, IT services company operations, and service variant analysis. Also trigger for RACI assignment, automation ROI, or compliance audit trail. Trigger: BPMN, process mapping, AS-IS TO-BE, process flow, swimlane, process maturity, automation ROI, RACI, fit-to-standard, process improvement, operational workflow.

This skill should be used when the user asks to "create a Sofka HTML document", "generate a branded report", "build an executive deliverable", "upgrade HTML to brand standards", "fix broken Sofka styles", "convert markdown to HTML", "batch convert deliverables to HTML", or mentions Sofka HTML, entregable, brand deliverable, Design System v5, Dark Authority, or any combination of Sofka + document/report/summary/analysis/roadmap. Also use when batch-upgrading existing HTML files to Sofka brand compliance, even if the user does not explicitly say "brand". Triggers on: convert to HTML, branded HTML, DS v5, markdown to HTML pipeline, Mermaid diagrams in HTML.

Regional finance and accounting standards skill covering Colombia (NIIF/DIAN/CTC), Ecuador (SRI/USD dollarization), Mexico (SAT/CFDI), United States (GAAP/ASC 606), Spain (AEAT/SII), and pan-Americas considerations. Use whenever the user mentions financial regulations, tax compliance, electronic invoicing, transfer pricing, CTC calculation, intercompany billing, multi-currency management, localization requirements, withholding taxes, or labor cost structures for IT services companies operating across these regions. Essential for SAP localization configuration and fit-to-standard financial workshops. Also trigger when discussing cost-vs-sale segregation, Activity Type cost rates, margin visibility, arm's length pricing, or any cross-border billing. Trigger: CTC calculation, transfer pricing, intercompany billing, tax compliance, e-invoicing, SAP localization, withholding taxes, Activity Type rates, margin visibility.

SAP S/4HANA implementation skill covering module selection (CO, SD, PS, FI, HCM), SAP Activate methodology, fit-to-standard workshops, multi-country localization, intercompany configuration, and professional services industry patterns. Use whenever the user mentions SAP, S/4HANA, SAP implementation, fit-to-standard, SAP modules, SAP localization, SAP migration, ERP implementation, or needs guidance on SAP configuration for IT services companies. Also trigger for SAP-specific gap analysis, SAP scope definition, SAP best practices, CATS integration, Strangler Fig migration, Activity Type configuration, or revenue recognition patterns for T&M, fixed price, retainer, or managed services contracts. Trigger: SAP implementation, S/4HANA configuration, fit-to-standard, SAP modules, SAP localization, CATS integration, Strangler Fig, Activity Types, revenue recognition.