22db413a5d
- Add OpenSpec to docs.json navigation after speckit-commands - Add OpenSpec Commands section to slash-commands.md - Update features.md to mention bundled Spec-Kit and OpenSpec - Add Spec-Kit and OpenSpec rows to CLAUDE.md Key Files table - Update CONTRIBUTING.md with bundled AI command set guide - Update refresh prompts section to include both spec-kit and openspec - Fix ESLint warning (prefer-const) in openspec-manager.ts Tasks 3-9 of Phase 3 complete. Task 2 (screenshot) requires manual UI capture. Task 10 (manual testing) remains for human verification.
3.5 KiB
title, description, icon
| title | description | icon |
|---|---|---|
| Slash Commands | Create custom slash commands with template variables for your AI workflows. | terminal |
Maestro includes an extensible slash command system with autocomplete. Type / in the input area to open the autocomplete menu, use arrow keys to navigate, and press Tab or Enter to select.
Custom AI Commands
Create your own slash commands in Settings > Custom AI Commands. Each command has a trigger (e.g., /deploy) and a prompt that gets sent to the AI agent.
Commands support template variables that are automatically substituted at runtime:
Agent Variables
| Variable | Description |
|---|---|
{{AGENT_NAME}} |
Agent name |
{{AGENT_PATH}} |
Agent home directory path (full path to project) |
{{AGENT_GROUP}} |
Agent's group name (if grouped) |
{{AGENT_SESSION_ID}} |
Agent session ID (for conversation continuity) |
{{TAB_NAME}} |
Custom tab name (alias: SESSION_NAME) |
{{TOOL_TYPE}} |
Agent type (claude-code, codex, opencode) |
Path Variables
| Variable | Description |
|---|---|
{{CWD}} |
Current working directory |
{{AUTORUN_FOLDER}} |
Auto Run documents folder path |
Auto Run Variables
| Variable | Description |
|---|---|
{{DOCUMENT_NAME}} |
Current Auto Run document name (without .md) |
{{DOCUMENT_PATH}} |
Full path to current Auto Run document |
{{LOOP_NUMBER}} |
Current loop iteration (starts at 1) |
Date/Time Variables
| Variable | Description |
|---|---|
{{DATE}} |
Current date (YYYY-MM-DD) |
{{TIME}} |
Current time (HH:MM:SS) |
{{DATETIME}} |
Full datetime (YYYY-MM-DD HH:MM:SS) |
{{TIMESTAMP}} |
Unix timestamp in milliseconds |
{{DATE_SHORT}} |
Short date (MM/DD/YY) |
{{TIME_SHORT}} |
Short time (HH:MM) |
{{YEAR}} |
Current year (YYYY) |
{{MONTH}} |
Current month (01-12) |
{{DAY}} |
Current day (01-31) |
{{WEEKDAY}} |
Day of week (Monday, Tuesday, etc.) |
Git & Context Variables
| Variable | Description |
|---|---|
{{GIT_BRANCH}} |
Current git branch name (requires git repo) |
{{IS_GIT_REPO}} |
"true" or "false" |
{{CONTEXT_USAGE}} |
Current context window usage percentage |
Example: A custom /standup command with prompt:
It's {{WEEKDAY}}, {{DATE}}. I'm on branch {{GIT_BRANCH}} at {{AGENT_PATH}}.
Summarize what I worked on yesterday and suggest priorities for today.
Spec-Kit Commands
Maestro bundles GitHub's spec-kit methodology for structured feature development. Commands include /speckit.constitution, /speckit.specify, /speckit.clarify, /speckit.plan, /speckit.tasks, and /speckit.implement.
See Spec-Kit Commands for the complete workflow guide.
OpenSpec Commands
Maestro bundles OpenSpec for spec-driven change management. These commands help you propose, implement, and archive changes systematically:
| Command | Description |
|---|---|
/openspec.proposal |
Create a change proposal with spec deltas before writing code |
/openspec.apply |
Implement an approved proposal by following the tasks |
/openspec.archive |
Archive completed changes after deployment |
/openspec.implement |
Generate Auto Run documents from a proposal (Maestro-specific) |
/openspec.help |
Get help with OpenSpec workflow and concepts |
See OpenSpec Commands for the complete workflow guide and directory structure.