### Install OpenSpec CLI using npm

Source: https://github.com/gudastudio/commands/blob/main/gudaspec/init.md

Installs the latest version of the OpenSpec CLI globally using npm. This command is applicable to both Linux/macOS and Windows environments. Ensure Node.js and npm are installed and configured correctly.

```bash
npm install -g @fission-ai/openspec@latest
```

--------------------------------

### Install GudaStudio Commands (Linux/macOS)

Source: https://context7.com/gudastudio/commands/llms.txt

Installs GudaStudio commands for Claude Code on Linux and macOS systems. It supports user-level, project-level, and custom path installations by cloning the repository and running an installer script.

```bash
# Clone the repository
git clone https://github.com/GuDaStudio/commands
cd commands

# User-level installation (applies to all projects)
./install.sh --user

# Project-level installation (applies to current project only)
./install.sh --project

# Custom path installation
./install.sh --target /your/custom/path
```

--------------------------------

### GudaStudio Commands Parameter Reference

Source: https://github.com/gudastudio/commands/blob/main/docs/README_EN.md

Provides a reference for the parameters used in the 'install.sh' (Bash) and 'install.ps1' (PowerShell) scripts for GudaStudio Commands installation.

```markdown
| Bash | PowerShell | Short | Description |
|------|------------|-------|-------------|
| `--user` | `-User` | `-u` | Install to user-level directory (`~/.claude/commands/`) |
| `--project` | `-Project` | `-p` | Install to project-level directory (`./.claude/commands/`) |
| `--target <path>` | `-Target <path>` | `-t` | Install to custom path |
| `--help` | `-Help` | `-h` | Show help information |
```

--------------------------------

### Initialize OpenSpec Environment (/gudaspec:init)

Source: https://context7.com/gudastudio/commands/llms.txt

Initializes the OpenSpec environment for a project within Claude Code. This command installs the OpenSpec CLI, sets up the project structure, and verifies the availability of Codex and Gemini MCP tools.

```bash
# In Claude Code, type:
/gudaspec:init

# The command performs:
# 1. Detects operating system (Linux, macOS, Windows)
# 2. Installs OpenSpec CLI globally if not present:
npm install -g @fission-ai/openspec@latest

# 3. Initializes OpenSpec for current project:
openspec init --tools claude

# 4. Validates MCP tools and displays summary:
# OpenSpec installation: ✓
# Project initialization: ✓
# mcp__codex__codex availability: ✓/✗
# mcp__gemini__gemini availability: ✓/✗

# After completion, clear context for next phase:
/clear
```

--------------------------------

### Install GudaStudio Commands on Linux/macOS

Source: https://github.com/gudastudio/commands/blob/main/docs/README_EN.md

Installs GudaStudio Commands using a bash script. Supports user-level, project-level, or custom path installations. Requires the 'install.sh' script from the repository.

```bash
# User-level installation (applies to all projects)
./install.sh --user

# Project-level installation (applies to current project only)
./install.sh --project

# Custom path
./install.sh --target /your/custom/path
```

--------------------------------

### Install GudaStudio Commands on Windows (PowerShell)

Source: https://github.com/gudastudio/commands/blob/main/docs/README_EN.md

Installs GudaStudio Commands using a PowerShell script. Supports user-level, project-level, or custom path installations. Requires the 'install.ps1' script from the repository.

```powershell
# User-level installation (applies to all projects)
.\install.ps1 -User

# Project-level installation (applies to current project only)
.\install.ps1 -Project

# Custom path
.\install.ps1 -Target C:\your\custom\path
```

--------------------------------

### Install GudaStudio Commands (Windows PowerShell)

Source: https://context7.com/gudastudio/commands/llms.txt

Installs GudaStudio commands for Claude Code on Windows systems using PowerShell. It provides equivalent options for user-level, project-level, and custom path installations via a PowerShell script.

```powershell
# User-level installation (applies to all projects)
.\install.ps1 -User

# Project-level installation (applies to current project only)
.\install.ps1 -Project

# Custom path installation
.\install.ps1 -Target C:\your\custom\path
```

--------------------------------

### Check MCP Tools Availability

Source: https://github.com/gudastudio/commands/blob/main/gudaspec/init.md

These commands check for the availability of specific MCP tools, 'mcp__codex__codex' and 'mcp__gemini__gemini'. If a tool is not found, a warning message with installation instructions is displayed, indicating that these tools are required for GudaSpec workflows.

```bash
# Check Codex MCP availability (example command, actual check might vary)
# If not available, display: "The `mcp__codex__codex` tool is not available. Please install it from: https://github.com/GuDaStudio/codexmcp"

# Check Gemini MCP availability (example command, actual check might vary)
# If not available, display: "The `mcp__gemini__gemini` tool is not available. Please install it from: https://github.com/GuDaStudio/geminimcp"
```

--------------------------------

### Initialize OpenSpec Project

Source: https://github.com/gudastudio/commands/blob/main/gudaspec/init.md

Initializes the OpenSpec environment for the current project, enabling specific tools like Claude. This command creates the necessary directory structure and configuration files for OpenSpec within the project.

```bash
openspec init --tools claude
```

--------------------------------

### Refine Proposals into Task Flows (/gudaspec:plan)

Source: https://context7.com/gudastudio/commands/llms.txt

Refines OpenSpec proposals into zero-decision executable task flows using multi-model analysis with Codex and Gemini. It identifies ambiguities and assumptions, and extracts Property-Based Testing properties for verification.

```bash
# In Claude Code, invoke to view and select proposals:
/gudaspec:plan

# The command performs:
# 1. Displays active changes:
openspec view

# 2. User confirms proposal ID to refine (e.g., proposal-001)

# 3. Runs multi-model ambiguity detection:
# Codex analysis request:
"Review proposal proposal-001 for decision points that remain unspecified.
List each as: [AMBIGUITY] <description> → [REQUIRED CONSTRAINT] <what must be decided>."

# Gemini analysis request:
"Identify implicit assumptions in proposal proposal-001.
For each: [ASSUMPTION] <description> → [EXPLICIT CONSTRAINT NEEDED] <specification>."

# 4. Target patterns for approval (anti-patterns are rejected):

```

--------------------------------

### Research Requirements into Constraints (/gudaspec:research)

Source: https://context7.com/gudastudio/commands/llms.txt

Transforms user requirements into structured constraint sets by exploring the codebase in parallel. This command uses subagents to analyze code boundaries, identifies constraints, and generates a proposal.md document.

```bash
# In Claude Code, invoke with your requirements:
/gudaspec:research
I need to create a real-time weather display page. Requirements:
  1. Real weather data including temperature and humidity
  2. City selection: Beijing, Shanghai, Shenzhen
  3. Different UI for weather conditions (wind, rain, sun, snow)
  4. Apple-quality frontend design

# The command performs:
# 1. Runs /opsx:explore to generate initial OpenSpec proposal
# 2. Scans codebase using mcp__auggie-mcp__codebase-retrieval
# 3. Spawns parallel Explore subagents for context boundaries:
#    - Subagent 1: User domain code (models, services, UI)
#    - Subagent 2: Auth & authorization (middleware, tokens)
#    - Subagent 3: Config & infrastructure (configs, builds)

# Each subagent returns structured JSON:
{
  "module_name": "user-domain",
  "existing_structures": ["UserModel", "UserService"],
  "existing_conventions": ["camelCase naming", "REST patterns"],
  "constraints_discovered": ["Must use existing auth middleware"],
  "open_questions": ["Which weather API to use?"],
  "dependencies": ["auth-module", "config-module"],
  "risks": ["API rate limits"],
  "success_criteria_hints": ["Weather updates within 5s"]
}

# 4. Aggregates findings and resolves ambiguities via AskUserQuestions
# 5. Generates proposal.md with full constraint sets
# After completion, clear context:
/clear
```

--------------------------------

### Clone Repository using Git

Source: https://github.com/gudastudio/commands/blob/main/docs/README_EN.md

Clones the GudaStudio Commands repository from GitHub. This is a standard Git command used to obtain a local copy of the project.

```bash
git clone https://github.com/GuDaStudio/commands
cd commands
```

--------------------------------

### Standardized Output Template for Explore Subagents

Source: https://github.com/gudastudio/commands/blob/main/gudaspec/research.md

Defines the unified JSON schema that all Explore subagents must adhere to for consistent output. This template includes fields for module name, discovered structures and conventions, constraints, open questions, dependencies, risks, and success criteria hints.

```json
{
  "module_name": "string - context boundary explored",
  "existing_structures": ["list of key structures/patterns found"],
  "existing_conventions": ["list of conventions/standards in use"],
  "constraints_discovered": ["list of hard constraints that limit solution space"],
  "open_questions": ["list of ambiguities requiring user input"],
  "dependencies": ["list of dependencies on other modules/systems"],
  "risks": ["list of potential risks or blockers"],
  "success_criteria_hints": ["observable behaviors that indicate success"]
}
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.