skills.rest
salazarsebas
salazarsebasCOMMUNITY
Explore all skills by this author →
Website𝕏@salazarsebas_crGitHub

tyler-architect

Translate product requirements and UX into technical architecture decisions and roadmaps.

9|66|Updated Oct 13, 2025
Search Tags:#design#architecture#productivity#requirements#trade-offs#stakeholders
One-click install
npx skills add https://github.com/salazarsebas/Cougr --skill tyler-architect
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tyler-architect
Source: https://github.com/salazarsebas/Cougr/tree/main/.claude/skills/tyler-architect
Command: npx skills add https://github.com/salazarsebas/Cougr --skill tyler-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tyler translates product requirements and UX into robust technical architecture, aligning engineering efforts with business goals and ensuring architecture decisions support long-term maintainability.

Core Features & Use Cases

  • Translate product requirements and UX into concrete architectural designs and policies.
  • Provide trade-off analysis, roadmap guidance, and implementation plans across teams.
  • Align engineering, product, and design stakeholders to reduce rework and speed decision-making.

Quick Start

Ask Tyler to translate the latest product requirements into a concrete system architecture and implementation roadmap.

Frequently Asked Questions about tyler-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I translate product requirements into a robust system architecture?▼

Architecture trade-off analysis evaluates competing design decisions by measuring impacts on developer productivity, system scalability, and stakeholder alignment. It provides actionable steps with safety and compliance considerations to guide implementation and reduce rework.

What is the best way to align engineering, product, and design stakeholders on technical designs?▼

Aligning stakeholders on technical designs requires translating product requirements into concrete architectural policies and roadmaps. This reduces rework and speeds decision-making by ensuring architecture decisions explicitly reflect trade-offs and maintain developer productivity.

Does this approach support scalable systems using the BMad methodology?▼

To create an implementation roadmap from UX goals, you translate product requirements into concrete technical designs and actionable steps. This includes safety and compliance considerations to guide development teams across the implementation lifecycle.

When do I need architecture decisions that reflect trade-offs and maintain developer productivity?▼

You need architecture decisions that reflect trade-offs when translating product requirements into scalable systems. Ensuring decisions maintain developer productivity and provide actionable steps prevents bottlenecks and aligns engineering with business goals.

Related Skills

Explore More Software Engineering Skills→
wahabmalikwahabmalik

bmad-create-epics-and-stories

Decompose product requirements into detailed epics and user stories.

Community
Advanced
lexicalninjalexicalninja
2

implementation-planner

Break down requirements into phased implementation roadmaps with dependencies, effort, and risks.

Community
Advanced
jc180105jc180105

Technical Product Manager

Translate engineering and product goals into a technical roadmap and API strategy.

Community
Advanced
yfyang86yfyang86
1

dennis-ritchie-perspective

Apply Dennis Ritchie's mental models to system design and language architecture decisions.

Community
Basic