Get the FREE Ultimate OpenClaw Setup Guide →

settings

Scanned
npx machina-cli add skill Sh3rd3n/megazord/settings --openclaw
Files (1)
SKILL.md
7.5 KB

/mz:settings

View current Megazord configuration and modify individual settings. Changes take effect on the next skill invocation.

Reference @skills/init/design-system.md for all visual output formatting.

Step 1: Load and Display

Display the stage banner:

╔═══════════════════════════════════════════════╗
║  ⚡ MEGAZORD ► SETTINGS                       ║
╚═══════════════════════════════════════════════╝

Read .planning/megazord.config.json. If the file does not exist, display:

╔═══════════════════════════════════════════════╗
║  ✗ No Megazord config found                   ║
╠═══════════════════════════════════════════════╣
║  Run /mz:init to set up your project first.   ║
╚═══════════════════════════════════════════════╝

Then exit. Do not proceed further.

If the config file exists, parse it and display the current settings:

╔═══════════════════════════════════════════════════════╗
║  Current Settings                                     ║
╠═══════════════════════════════════════════════════════╣
║  ▸ Project                                            ║
║    Name:            {project_name}                    ║
║    Mode:            {yolo|interactive}                 ║
║    Depth:           {comprehensive|standard|quick}     ║
║    Parallelization: {✓/✗}                             ║
║    Commit docs:     {✓/✗}                             ║
║                                                       ║
║  ▸ Model                                              ║
║    Profile:         {quality|balanced|budget}          ║
║                                                       ║
║  ▸ Quality                                            ║
║    TDD:             {✓/✗}                             ║
║    Review:          {auto|manual|off}                  ║
║    Brainstorming:   {✓/✗}                             ║
║    CORTEX:          {✓/✗}                             ║
║    Debug:           {systematic|quick}                 ║
║                                                       ║
║  ▸ Workflow                                           ║
║    Research:        {✓/✗}                             ║
║    Plan check:      {✓/✗}                             ║
║    Verifier:        {✓/✗}                             ║
╚═══════════════════════════════════════════════════════╝

Use ✓ for true values and ✗ for false values. Display enum values as-is (e.g., "auto", "systematic").

Step 2: Modification

Ask the user what they would like to change.

Use AskUserQuestion:

  • header: "Setting" (7 chars)
  • question: "What would you like to change?"
  • options:
    • "Quality" -- description: "TDD, review, brainstorming, CORTEX, debug mode"
    • "Workflow" -- description: "Research, plan check, verifier agents"
    • "Model" -- description: "AI model profile (quality/balanced/budget)"
    • "Execution" -- description: "Mode, depth, parallelization, commit docs"
    • "Done" -- description: "No changes -- exit"

If "Done": Display "Settings unchanged." and exit.

Quality Settings

If the user selects "Quality", present each toggle:

  • header: "TDD" (3 chars), question: "Test-driven development (currently: {current value})", options: "On" / "Off"
  • header: "Review" (6 chars), question: "Code review mode (currently: {current value})", options: "Auto" / "Manual" / "Off"
  • header: "Brainstorm" (10 chars), question: "Socratic brainstorming (currently: {current value})", options: "On" / "Off"
  • header: "CORTEX" (6 chars), question: "CORTEX adaptive thinking (currently: {current value})", options: "On" / "Off"
  • header: "Debug" (5 chars), question: "Debugging approach (currently: {current value})", options: "Systematic" / "Quick"

Workflow Settings

If the user selects "Workflow", present each toggle:

  • header: "Research" (8 chars), question: "Research agent before planning (currently: {current value})", options: "On" / "Off"
  • header: "Plan Check" (10 chars), question: "Plan verification agent (currently: {current value})", options: "On" / "Off"
  • header: "Verifier" (8 chars), question: "Post-phase verifier agent (currently: {current value})", options: "On" / "Off"

Model Profile

If the user selects "Model", present:

  • header: "Model" (5 chars), question: "AI model profile (currently: {current value})", options:
    • "Quality" -- description: "Opus everywhere -- highest quality, higher cost"
    • "Balanced" -- description: "Opus for planning, Sonnet for execution"
    • "Budget" -- description: "Sonnet/Haiku -- fastest, lowest cost"

Execution Settings

If the user selects "Execution", present each setting:

  • header: "Mode" (4 chars), question: "Execution mode (currently: {current value})", options: "YOLO" / "Interactive"
  • header: "Depth" (5 chars), question: "Planning depth (currently: {current value})", options: "Comprehensive" / "Standard" / "Quick"
  • header: "Parallel" (8 chars), question: "Parallel plan execution (currently: {current value})", options: "On" / "Off"
  • header: "Git" (3 chars), question: "Commit planning docs (currently: {current value})", options: "Yes" / "No"

Write Updated Config

After collecting changes, write the updated config back to .planning/megazord.config.json with 2-space indentation.

Step 3: Confirmation

Show what changed:

╔═══════════════════════════════════════════════╗
║  Settings Updated                             ║
╠═══════════════════════════════════════════════╣
║  {setting}: {old value} → {new value}         ║
║  {setting}: {old value} → {new value}         ║
╚═══════════════════════════════════════════════╝

If no values actually changed (user selected same values), display: "No changes detected. Settings remain the same."

Note: "Changes take effect on the next skill invocation."

Ask if the user wants to change anything else. If yes, return to Step 2. If no, exit with the next-up block:

═══════════════════════════════════════════════════
▸ Next Up
**Check Project Status** -- see current progress and next actions
`/mz:status`
═══════════════════════════════════════════════════

Source

git clone https://github.com/Sh3rd3n/megazord/blob/master/skills/settings/SKILL.mdView on GitHub

Overview

Settings lets you view the current Megazord configuration and modify individual options. It reads .planning/megazord.config.json and displays sections like Project, Model, Quality, and Workflow, with changes applying on the next skill invocation.

How This Skill Works

On load, the skill shows a stage banner, then tries to read .planning/megazord.config.json. If the file is missing, it displays a notice and exits. If present, it renders the current settings and prompts you to choose what to change (Quality, Workflow, Model, Execution, or Done) using interactive questions. Each change updates the config for the next run.

When to Use It

  • You want to inspect the current Megazord configuration before making changes.
  • The config file is missing and you need to initialize a project with /mz:init.
  • You need to adjust Quality settings (TDD, Review, Brainstorming, CORTEX, Debug) for a sprint.
  • You want to tweak Workflow settings (Research, Plan check, Verifier) to match team processes.
  • You aim to confirm or reset settings before handing the project to another team member.

Quick Start

  1. Step 1: Run /mz:settings to load and display the current Megazord configuration.
  2. Step 2: When prompted, choose what you would like to change (Quality, Workflow, Model, Execution, or Done).
  3. Step 3: If you choose a category, adjust the toggles and values; changes apply on the next skill invocation.

Best Practices

  • Check for the existence of .planning/megazord.config.json before attempting changes.
  • Review each section (Project, Model, Quality, Workflow) to understand current values.
  • Use the provided toggles and enum values exactly (✓/✗, auto/manual/off, On/Off).
  • Document changes so teammates understand why a setting was altered.
  • Run /mz:settings again after changes to verify the updated configuration is saved for the next run.

Example Use Cases

  • A team opens /mz:settings to view the current Project mode and Depth, then changes Depth from comprehensive to quick for a faster iteration.
  • Quality is updated to enable Brainstorming and CORTEX, aligning planning with creative problem solving for a new feature.
  • Workflow toggles are adjusted: Research enabled and Verifier enabled to improve pre-commit checks.
  • Model profile is shifted from balanced to quality to prioritize higher model performance in a data-heavy project.
  • If the config is missing, the user follows the prompt and runs /mz:init to create Megazord config before proceeding.

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers ↗