q2mm-analysis-design

Transform vague benchmark questions into structured design documents.

27|29|Updated Aug 26, 2014
One-click install
npx skills add https://github.com/ericchansen/q2mm --skill q2mm-analysis-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: q2mm-analysis-design
Source: https://github.com/ericchansen/q2mm/tree/main/.copilot/skills/q2mm-analysis-design
Command: npx skills add https://github.com/ericchansen/q2mm --skill q2mm-analysis-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide a rigorous, repeatable plan to transform vague benchmark questions into structured design documents.

Core Features & Use Cases

  • Restates user questions verbatim to preserve intent and prevent scope drift.
  • Enumerates deliverables and maps artifacts back to questions for traceability.
  • Guides the writer through a pre-write design checklist to align with user intent.

Quick Start

Write a design checklist following the steps to prepare a benchmark analysis document before drafting.

Frequently Asked Questions about q2mm-analysis-design

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

FAQPage Schema
What is a benchmark analysis design document?

It is a structured plan that restates benchmark questions verbatim, maps deliverable artifacts to specific question parts, and enforces a pre-write design checklist to prevent scope drift and preserve user intent.

How do I structure a benchmark analysis before writing?

Structure your benchmark analysis by following a four-step gating logic: restate the question verbatim, enumerate artifact inventories, map artifacts to question parts, and compile a design checklist before drafting.

How do I prevent scope drift when analyzing vague benchmark questions?

Prevent scope drift by restating the user's benchmark questions verbatim to preserve intent, then mapping explicit deliverable artifacts directly back to each question part for traceability before drafting begins.

Does this benchmark design process require specific input formats?

No specific input formats are required, but the process enforces a strict frontmatter schema and requires a vague benchmark question as input to generate a structured design document with mapped artifacts.

What are the limitations of using a pre-write design checklist for benchmark analysis?

The process requires completing a strict Step 1–4 gating logic and a safety review before writing, which may add overhead for simple benchmark questions that do not need detailed artifact mapping or traceability.