dev-quick

Generate concise quick-specs for small engineering tasks and bug fixes.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/MaxGiu67/plugin-MUCC --skill dev-quick
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-quick
Source: https://github.com/MaxGiu67/plugin-MUCC/tree/main/dev-methodology/skills/dev-quick
Command: npx skills add https://github.com/MaxGiu67/plugin-MUCC --skill dev-quick

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a fast, lightweight alternative to the full 8-phase dev workflow for small, well-scoped engineering tasks so teams can produce actionable specs without the overhead of the complete process.

Core Features & Use Cases

  • Quick-spec generation: Produces a compact specs/quick-spec.md using a template that includes a mini vision, MoSCoW requirements, user stories with acceptance criteria, tech notes, and an implementation plan.
  • Scope validation and escalation: Automatically checks for scale limits (stories, epics, DB changes, story points) and suggests escalation to the full workflow when needed.
  • Automation & tracking: Supports an --auto mode to skip interactive prompts and updates specs/_status.md and specs/_changelog.md to record decisions and workflow state.
  • Use Cases: Fast bug fixes, small features (1–15 stories), or any task with a clearly limited scope that needs a concise developer-ready spec.

Quick Start

Generate a compact quick-spec from your task description by saying: Create a quick spec for fixing the password reset 500 error with acceptance criteria.

Frequently Asked Questions about dev-quick

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

FAQPage Schema
How do I generate a quick spec for a small bug fix or feature?

To generate a quick spec for a small bug fix, provide a task description and the system produces a concise quick-spec.md containing a mini vision, MoSCoW requirements, user stories with acceptance criteria, and an implementation plan.

What is the best lightweight alternative to a full engineering workflow for small tasks?

A quick-spec workflow provides a fast, lightweight alternative for small, well-scoped engineering tasks, enabling teams to produce actionable developer-ready specs without the overhead of a complete multi-phase development process.

Can I use quick-spec generation for larger features with many user stories?

Quick-spec generation is designed for small features of 1–15 user stories. It automatically validates scale limits and suggests escalating to a full workflow if your task exceeds the expected story or epic boundaries.

How do I automate quick-spec creation to skip interactive prompts?

You can automate quick-spec creation by using an --auto mode, which skips interactive prompts and automatically updates tracking files like _status.md and _changelog.md to record workflow state and decisions.

What components should a compact engineering spec include for small tasks?

A compact engineering spec should include a mini vision, MoSCoW prioritized requirements, user stories with acceptance criteria, technical notes, and a step-by-step implementation plan tailored for the specific task.

When should I avoid using a quick-spec and escalate to a full workflow?

You should avoid quick-specs and escalate to a full workflow when a task involves large scale database changes, exceeds 15 user stories, or lacks a clearly limited scope that fits the lightweight template.