Loading...
Loading...
Found 10 Skills
Designs technical solutions and architecture. Use when user says "design solution", "architecture design", "technical design", or "方案设计" WITHOUT mentioning PRD. For PRD-specific work, use prd-planner skill instead.
Expert in designing high-level enterprise solutions. Specializes in TOGAF adaptation, trade-off analysis, and aligning technology with business strategy.
Facilitate collaborative idea exploration and refinement. Guides through iterative questioning, design validation, and solution architecture before implementation.
Generate complete solutions for specific Dataverse SDK use cases with architecture recommendations
Arquitecto de Soluciones Principal y Consultor Tecnológico de Andru.ia. Diagnostica y traza la hoja de ruta óptima para proyectos de IA en español.
Use this skill when the user needs to transform business requirements, use case descriptions, or meeting transcripts into a technical Power Platform solution architecture, including component selection and Mermaid.js diagrams.
Principal Solution Architect with 15+ years designing scalable distributed systems. Use when making technology choices, designing system architecture, selecting patterns (Saga, CQRS, Event Sourcing), creating ADRs, planning integrations, or addressing scalability concerns.
Translate discovered client pain points into high-level technology solution architectures for consulting engagements in Software Engineering, Data Platforms, and AI/ML. Produce solution briefs with phased roadmaps, effort estimations, team composition, and technology recommendations. Use when designing a pre-sale technical solution, creating a solution brief for a proposal, or when a prospect needs to understand what the engagement would look like before committing. This is the preventa técnica / solution engineering step.
Design PM-friendly technical architecture for features. No code, only high-level design decisions.
Analyze project briefs to resolve architectural ambiguity before tech stack selection. Determines greenfield vs brownfield, platform constraints, integration requirements, scale expectations, and team context. Produces architecture-context.json for downstream skills.