Skip to content
Development
Skill

/quick-dev

Implement a task directly with Maister standards enforcement (no planning mode)

BOOST
From plugin
maister
25217 skills25 agents6 commands1 MCP
Install
$ npx -y skills add SkillPanel/maister --skill quick-dev --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/quick-dev

Context preview

The summary Claude sees to decide when to auto-load this skill.

Implement a task directly with Maister standards enforcement (no planning mode)

SKILL.md

quick-dev.SKILL.md
name: quick-dev
description: Implement a task directly with Maister standards enforcement (no planning mode)
argument-hint: "[task description]"

Quick Dev — Direct Development with Standards Enforcement

This works exactly as if you asked the main agent to implement the task directly — no plan mode. The one addition: discover and enforce the project's coding standards from `.maister/docs/`.

Workflow

1. **Get the task** — Use the argument if provided. If none, ask with `ask_user`: "What would you like to implement?"

2. **Implement it** — Explore the relevant code and make the changes exactly as you normally would for a direct development request.

3. **Discover and enforce standards (the addition)** — As you work:

  • Read `.maister/docs/INDEX.md` to find which standards exist.
  • **Then read the specific standard files it points to that are relevant to what you touch.** Reading INDEX.md alone is NOT sufficient — this is mandatory. When you reach a new area mid-task (e.g. auth, database, forms), read its standards before coding it.
  • Apply the matched standards while implementing.

4. **Verify compliance (mandatory)** — After implementing, go through each applicable standard and verify it was followed — report a **Standards Compliance Checklist** (pass/fail per guideline, each annotated with its source file) in your summary, alongside what changed and any tests run. Address any failure before marking the task complete.

If `.maister/docs/INDEX.md` does not exist, implement normally and note: "No Maister standards found. Consider running `/maister-init`."

Read more
Ships withmaister

Structured, standards-aware development workflows for Claude Code Describe what you want to build, and the plugin handles the rest - from specification through implementation to verification - while enforcing your project's coding standards at every step.

Get the whole plugin

Other skills on maister.