mg-assess-tech

Coordinate multi-role evaluations to produce structured technical recommendations and implementation plans.

1|1|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/wonton-web-works/miniature-guacamole --skill mg-assess-tech
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: mg-assess-tech
Source: https://github.com/wonton-web-works/miniature-guacamole/tree/main/src/framework/skills/mg-assess-tech
Command: npx skills add https://github.com/wonton-web-works/miniature-guacamole --skill mg-assess-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Aligns architecture decisions with CTO, staff-engineer, api-designer, and data-engineer input to produce a cohesive technical approach and risk-aware recommendations.

Core Features & Use Cases

  • Multi-role coordination: orchestrates input from CTO, staff-engineer, API designer, and data engineer to form a unified technical plan.
  • Evidence-based recommendations: compares architectures, quantifies trade-offs, and surfaces risks with actionable context.
  • Artifacts and outputs: generates a technical design document, decision rationale, risk mitigations, and a clear implementation path.
  • Use Case: ideal for architecture steering decisions like choosing between service patterns, data architecture, and integration strategies.

Quick Start

Run a technical assessment for a feature by specifying constraints and goals to receive a structured recommendation.

Frequently Asked Questions about mg-assess-tech

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

FAQPage Schema
How do I conduct a structured tech review for architecture decisions?▼

A structured tech review for architecture decisions coordinates input from CTO, staff-engineer, api-designer, and data-engineer roles to produce a unified technical approach. It evaluates technology stack comparisons and risk trade-offs across workstreams, outputting a documented rationale and implementation plan.

What is the best way to compare technology stack trade-offs and quantify risks?▼

Comparing technology stack trade-offs requires evidence-based evaluation across multiple engineering disciplines to surface risks with actionable context. By orchestrating multi-role coordination, it quantifies architectural trade-offs and generates risk mitigations aligned with stakeholder constraints.

How do I align stakeholders on a technical design for a new feature?▼

Aligning stakeholders on a technical design involves synthesizing evaluations from CTO, staff-engineer, api-designer, and data-engineer perspectives into a cohesive recommendation. This approach ensures architecture steering decisions include documented decision rationale and a clear implementation path.

Can I use this approach for choosing between service patterns and data architecture strategies?▼

Yes, choosing between service patterns and data architecture strategies is an ideal use case for structured technical assessments. It evaluates integration strategies, compares architectures, and produces risk-aware recommendations with a concrete implementation plan tailored to your specified constraints.

What artifacts do I need to start evaluating architecture decisions and trade-offs?▼

Evaluating architecture decisions requires specifying feature constraints and goals as input to generate a structured recommendation. The process then outputs a technical design document, decision rationale, risk mitigations, and a clear implementation path based on those defined parameters.