mg-build

Classify incoming work requests and route them to MECHANICAL or ARCHITECTURAL tracks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Classifies incoming work requests and routes them to the correct development track (MECHANICAL or ARCHITECTURAL) to streamline delivery.

Core Features & Use Cases

  • Automated intake classification: evaluate a ticket or request and assign the appropriate track.
  • Deterministic spawning flow: orchestrates Dev, QA, Staff Engineer, and leadership steps with gating.
  • Handoff and memory integration: records decisions and triggers memory-backed handoffs to downstream agents.

Quick Start

Invoke mg-build with a workstream ID to classify and execute the appropriate track.

Frequently Asked Questions about mg-build

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

FAQPage Schema
How do I orchestrate end-to-end build workflows with deterministic spawning?

You orchestrate end-to-end build workflows by classifying incoming work requests and routing them to MECHANICAL or ARCHITECTURAL tracks with deterministic spawning of Dev, QA, and leadership review.

What is automated intake classification for build workflows?

Automated intake classification evaluates a ticket or work request to assign the appropriate development track, streamlining delivery by applying memory-backed classification to route features correctly.

How do I set up strict gates and acceptance criteria for QA and leadership review?

You establish strict gates and acceptance criteria by applying a build workflow that deterministically spawns Dev, QA, Staff Engineer, and leadership steps with structured handoffs across teams.

When do I need memory-backed classification for development tracks?

You need memory-backed classification when feature work requires structured handoffs to downstream agents, ensuring decisions are recorded and strict gates are maintained across MECHANICAL or ARCHITECTURAL tracks.

Can I use build workflow orchestration for deterministic spawning without manual routing?

Yes, build workflow orchestration automatically classifies incoming work requests and routes them to the correct track, enabling deterministic spawning of Dev and QA steps without manual intervention.

Does mg-build require specific dependencies to classify work requests?

No, mg-build does not require external dependencies to classify work requests, as it handles memory-backed classification and routing internally without additional components.