mg-assess

Automate feature idea intake and evaluation into go/no-go recommendations.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Intake and evaluation of feature ideas is time-consuming and inconsistent; mg-assess streamlines this by guiding rough ideas through structured discovery, multi-lens evaluation, and a clear go/no-go decision.

Core Features & Use Cases

  • Guided intake to classify ideas as rough, semi-structured, or structured
  • Multi-lens evaluations from product-owner, product-manager, and CTO perspectives
  • Synthesis into scope, criteria, risks, and recommended next steps to align stakeholders

Quick Start

Describe a feature idea or problem to mg-assess to start intake and evaluation.

Frequently Asked Questions about mg-assess

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

FAQPage Schema
How do I evaluate feature ideas and decide whether to build them?

Evaluating feature ideas requires guiding raw requests through discovery, multi-lens assessments from product and technical perspectives, and synthesis into a structured go/no-go recommendation with defined next steps.

What is the best way to automate product management intake for feature requests?

Automating product management intake involves classifying rough or semi-structured feature requests upon entry, applying multi-lens evaluations, and capturing memory to align stakeholders on scope and risks.

Can I assess a feature request if it is only a rough idea with no structure?

Yes, assessing rough ideas works by guiding them through structured discovery and evaluation, ensuring even unstructured requests receive a formal go/no-go recommendation and defined next steps.

How do I align stakeholders on feature scope and risks during intake?

Aligning stakeholders on feature scope requires synthesizing evaluations from product-owner, product-manager, and CTO perspectives into a unified recommendation that highlights criteria, risks, and recommended next steps.

When do I need a go/no-go decision process for feature intake?

A go/no-go decision process is needed when early-stage product decisions require accelerating feature evaluation, ensuring consistent intake, and escalating specialized requests to align stakeholders.

Does mg-assess handle escalation to specialists during feature evaluation?

Yes, during feature evaluation, mg-assess handles escalation to specialists as needed, ensuring structured outputs and memory capture while guiding discovery toward a clear go/no-go recommendation.