start

Redirect deprecated /mst:start commands to /mst:request with all arguments.

24|5|Updated Feb 14, 2026
One-click install
npx skills add https://github.com/myrtlepn/gran-maestro --skill start-myrtlepn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start
Source: https://github.com/myrtlepn/gran-maestro/tree/main/skills/start
Command: npx skills add https://github.com/myrtlepn/gran-maestro --skill start-myrtlepn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill acts as a backward-compatible redirect, ensuring that users who previously used /mst:start are seamlessly guided to the current /mst:request command without disruption.

Core Features & Use Cases

  • Deprecated Command Handling: Automatically translates outdated /mst:start commands into the current /mst:request command.
  • User Guidance: Informs the user about the command change, promoting adoption of the new standard.
  • Use Case: A user familiar with an older version of the tool types /mst:start "build a login page". The skill intercepts this, informs the user that /mst:start is deprecated and that /mst:request should be used instead, and then executes /mst:request "build a login page".

Quick Start

Use the start skill to request a new feature for the dashboard.

Frequently Asked Questions about start

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

FAQPage Schema
How do I handle a deprecated command redirect for backward compatibility?

A deprecated command redirect automatically intercepts outdated user requests, informs the user of the command change, and forwards all original arguments to the current command structure to maintain backward compatibility.

What happens when I use a deprecated command instead of the new request structure?

When a deprecated command is used, the system intercepts it, notifies the user that the command is deprecated, and automatically executes the current request command with all original arguments passed through.

Can I pass arguments to the new command when a deprecated command is redirected?

Yes, when a deprecated command is redirected, all arguments provided by the user are automatically forwarded to the new request command, ensuring the command execution remains fully functional without disruption.

Why do I need a backward-compatible redirect for deprecated commands?

A backward-compatible redirect is needed to seamlessly guide users familiar with older versions to the current command structure, preventing disruption while promoting adoption of the new standard without breaking existing workflows.

Does the redirect skill execute the new command or just inform the user of the change?

The redirect skill both informs the user of the command deprecation and executes the new request command, ensuring the user's original request is fully processed while learning the updated command syntax.