specfact-cli 0.9.1__tar.gz → 0.11.2__tar.gz

{specfact_cli-0.9.1 → specfact_cli-0.11.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: specfact-cli
-Version: 0.9.1
+Version: 0.11.2
 Summary: Brownfield-first CLI: Reverse engineer legacy Python → specs → enforced contracts. Automate legacy code documentation and prevent modernization regressions.
 Project-URL: Homepage, https://github.com/nold-ai/specfact-cli
 Project-URL: Repository, https://github.com/nold-ai/specfact-cli.git
@@ -226,6 +226,7 @@ Requires-Python: >=3.11
 Requires-Dist: beartype>=0.22.4
 Requires-Dist: crosshair-tool>=0.0.97
 Requires-Dist: gitpython>=3.1.45
+Requires-Dist: graphviz>=0.20.1
 Requires-Dist: hypothesis>=6.142.4
 Requires-Dist: icontract>=2.7.1
 Requires-Dist: jinja2>=3.1.6
@@ -236,7 +237,7 @@ Requires-Dist: opentelemetry-sdk>=1.27.0
 Requires-Dist: pydantic>=2.12.3
 Requires-Dist: python-dotenv>=1.2.1
 Requires-Dist: pyyaml>=6.0.3
-Requires-Dist: rich<14.0.0,>=13.0.0
+Requires-Dist: rich<13.6.0,>=13.5.2
 Requires-Dist: ruamel-yaml>=0.18.16
 Requires-Dist: ruff>=0.14.2
 Requires-Dist: typer>=0.20.0
@@ -244,12 +245,15 @@ Requires-Dist: typing-extensions>=4.15.0
 Requires-Dist: watchdog>=6.0.0
 Provides-Extra: dev
 Requires-Dist: basedpyright>=1.32.1; extra == 'dev'
+Requires-Dist: bearer>=3.1.0; extra == 'dev'
 Requires-Dist: beartype>=0.22.4; extra == 'dev'
 Requires-Dist: crosshair-tool>=0.0.97; extra == 'dev'
+Requires-Dist: graphviz>=0.20.1; extra == 'dev'
 Requires-Dist: hypothesis>=6.142.4; extra == 'dev'
 Requires-Dist: icontract>=2.7.1; extra == 'dev'
 Requires-Dist: isort>=7.0.0; extra == 'dev'
 Requires-Dist: pip-tools>=7.5.1; extra == 'dev'
+Requires-Dist: pyan3>=1.2.0; extra == 'dev'
 Requires-Dist: pylint>=4.0.2; extra == 'dev'
 Requires-Dist: pytest-asyncio>=1.2.0; extra == 'dev'
 Requires-Dist: pytest-cov>=7.0.0; extra == 'dev'
@@ -257,11 +261,16 @@ Requires-Dist: pytest-mock>=3.15.1; extra == 'dev'
 Requires-Dist: pytest-xdist>=3.8.0; extra == 'dev'
 Requires-Dist: pytest>=8.4.2; extra == 'dev'
 Requires-Dist: ruff>=0.14.2; extra == 'dev'
-Requires-Dist: semgrep>=1.141.1; extra == 'dev'
+Requires-Dist: semgrep>=1.144.0; extra == 'dev'
 Requires-Dist: tomlkit>=0.13.3; extra == 'dev'
 Requires-Dist: types-pyyaml>=6.0.12.20250516; extra == 'dev'
+Provides-Extra: enhanced-analysis
+Requires-Dist: bearer>=3.1.0; extra == 'enhanced-analysis'
+Requires-Dist: graphviz>=0.20.1; extra == 'enhanced-analysis'
+Requires-Dist: pyan3>=1.2.0; extra == 'enhanced-analysis'
+Requires-Dist: syft>=0.9.5; extra == 'enhanced-analysis'
 Provides-Extra: scanning
-Requires-Dist: semgrep>=1.141.1; extra == 'scanning'
+Requires-Dist: semgrep>=1.144.0; extra == 'scanning'
 Description-Content-Type: text/markdown
 
 # SpecFact CLI
@@ -316,6 +325,7 @@ A brownfield-first CLI that **reverse engineers your legacy code** into document
 - ✅ **Reverse engineer legacy code** → Extract specs automatically from existing code
 - ✅ **Runtime contract enforcement** → Prevent regressions during modernization
 - ✅ **Symbolic execution** → Discover hidden edge cases with CrossHair
+- ✅ **API contract testing** → Validate OpenAPI/AsyncAPI specs with Specmatic integration
 - ✅ **Works offline** → No cloud required, fully local
 - ✅ **CLI integrations** → Works seamlessly with VS Code, Cursor, GitHub Actions, and any agentic workflow
 
@@ -343,7 +353,7 @@ SpecFact CLI works with your existing tools—no new platform to learn. See real
 
 ```bash
 # Zero-install (just run it)
-uvx specfact-cli@latest --help
+uvx specfact-cli@latest
 
 # Or install with pip
 pip install specfact-cli
@@ -353,13 +363,13 @@ pip install specfact-cli
 
 ```bash
 # Modernizing legacy code? (Recommended)
-specfact import from-code my-project --repo .
+specfact import from-code legacy-api --repo .
 
 # Starting a new project?
-specfact plan init my-project --interactive
+specfact plan init legacy-api --interactive
 
 # Using GitHub Spec-Kit or other tools?
-specfact import from-bridge --repo ./my-project --adapter speckit --write
+specfact import from-bridge --repo . --adapter speckit --write
 ```
 
 That's it! 🎉

{specfact_cli-0.9.1 → specfact_cli-0.11.2}/README.md

@@ -50,6 +50,7 @@ A brownfield-first CLI that **reverse engineers your legacy code** into document
 - ✅ **Reverse engineer legacy code** → Extract specs automatically from existing code
 - ✅ **Runtime contract enforcement** → Prevent regressions during modernization
 - ✅ **Symbolic execution** → Discover hidden edge cases with CrossHair
+- ✅ **API contract testing** → Validate OpenAPI/AsyncAPI specs with Specmatic integration
 - ✅ **Works offline** → No cloud required, fully local
 - ✅ **CLI integrations** → Works seamlessly with VS Code, Cursor, GitHub Actions, and any agentic workflow
 
@@ -77,7 +78,7 @@ SpecFact CLI works with your existing tools—no new platform to learn. See real
 
 ```bash
 # Zero-install (just run it)
-uvx specfact-cli@latest --help
+uvx specfact-cli@latest
 
 # Or install with pip
 pip install specfact-cli
@@ -87,13 +88,13 @@ pip install specfact-cli
 
 ```bash
 # Modernizing legacy code? (Recommended)
-specfact import from-code my-project --repo .
+specfact import from-code legacy-api --repo .
 
 # Starting a new project?
-specfact plan init my-project --interactive
+specfact plan init legacy-api --interactive
 
 # Using GitHub Spec-Kit or other tools?
-specfact import from-bridge --repo ./my-project --adapter speckit --write
+specfact import from-bridge --repo . --adapter speckit --write
 ```
 
 That's it! 🎉

{specfact_cli-0.9.1 → specfact_cli-0.11.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "specfact-cli"
-version = "0.9.1"
+version = "0.11.2"
 description = "Brownfield-first CLI: Reverse engineer legacy Python → specs → enforced contracts. Automate legacy code documentation and prevent modernization regressions."
 readme = "README.md"
 requires-python = ">=3.11"
@@ -34,13 +34,14 @@ dependencies = [
     
     # CLI framework
     "typer>=0.20.0",
-    "rich>=13.0.0,<14.0.0",
+    "rich>=13.5.2,<13.6.0",  # Compatible with semgrep (requires rich~=13.5.2)
     
     # Template engine
     "jinja2>=3.1.6",
     
     # Graph analysis
     "networkx>=3.4.2",
+    "graphviz>=0.20.1",  # Graph visualization (requires system Graphviz: apt-get install graphviz)
     
     # Git operations
     "gitpython>=3.1.45",
@@ -82,19 +83,39 @@ dev = [
     "tomlkit>=0.13.3",  # Style-preserving TOML library (recommended successor to pytoml)
     "types-PyYAML>=6.0.12.20250516",
     "pip-tools>=7.5.1",
-    "semgrep>=1.141.1",
+    "semgrep>=1.144.0",  # Latest version compatible with rich~=13.5.2
     
     # Contract-First Development Dependencies (dev)
     "icontract>=2.7.1",
     "beartype>=0.22.4", 
     "crosshair-tool>=0.0.97",
     "hypothesis>=6.142.4",
+    
+    # Enhanced Analysis Tools (for local development)
+    # Note: syft excluded from dev/test due to rich version conflict with semgrep
+    # Install separately: pip install specfact-cli[enhanced-analysis] if needed
+    "graphviz>=0.20.1",  # Graph visualization (requires system Graphviz: apt-get install graphviz)
+    "pyan3>=1.2.0",  # Python call graph analysis
+    "bearer>=3.1.0",  # Data flow analysis for security
 ]
 
 scanning = [
-    "semgrep>=1.141.1",  # Optional: Only needed for code scanning features
+    "semgrep>=1.144.0",  # Optional: Only needed for code scanning features
+]
+
+enhanced-analysis = [
+    "graphviz>=0.20.1",  # Graph visualization (requires system Graphviz: apt-get install graphviz)
+    "pyan3>=1.2.0",  # Python call graph analysis
+    "syft>=0.9.5",  # Software Bill of Materials (SBOM) generation
+    "bearer>=3.1.0",  # Data flow analysis for security
 ]
 
+# Note: Specmatic integration (specfact spec commands) requires the Specmatic CLI tool
+# to be installed separately. Specmatic is a Java-based CLI tool, not a Python package.
+# Install from: https://docs.specmatic.io/
+# The specfact spec commands will check for Specmatic availability and provide
+# helpful error messages if it's not found.
+
 # Add other optional dependency groups from your original if they existed and are still needed (e.g., server, client, devtools, full from tpl)
 
 [project.urls]
@@ -127,12 +148,18 @@ dependencies = [
     "pylint>=4.0.2",
     "ruff>=0.14.2",
     "yamllint>=1.37.1",
-    "semgrep>=1.141.1",
+    "semgrep>=1.144.0",  # Latest version compatible with rich~=13.5.2
     # Contract-First Development Dependencies
     "icontract>=2.7.1",
     "beartype>=0.22.4", 
     "crosshair-tool>=0.0.97",
     "hypothesis>=6.142.4",
+    # Enhanced Analysis Tools (for local development)
+    # Note: syft excluded from dev/test due to rich version conflict with semgrep
+    # Install separately: pip install specfact-cli[enhanced-analysis] if needed
+    "graphviz>=0.20.1",  # Graph visualization (requires system Graphviz: apt-get install graphviz)
+    "pyan3>=1.2.0",  # Python call graph analysis
+    "bearer>=3.1.0",  # Data flow analysis for security
 ]
 
 [tool.hatch.envs.default.scripts]
@@ -227,6 +254,12 @@ dependencies = [
     "crosshair-tool>=0.0.97",
     "hypothesis>=6.142.4",
     "yamllint>=1.37.1",
+    # Enhanced Analysis Tools (for testing)
+    # Note: syft excluded from test due to rich version conflict with semgrep
+    # Install separately: pip install specfact-cli[enhanced-analysis] if needed
+    "graphviz>=0.20.1",  # Graph visualization (requires system Graphviz: apt-get install graphviz)
+    "pyan3>=1.2.0",  # Python call graph analysis
+    "bearer>=3.1.0",  # Data flow analysis for security
 ]
 dev-mode = true
 parallel = true

specfact_cli-0.11.2/resources/prompts/shared/cli-enforcement.md

@@ -0,0 +1,31 @@
+# CLI Usage Enforcement Rules
+
+## Core Principle
+
+**ALWAYS use SpecFact CLI commands. Never create artifacts directly.**
+
+## Rules
+
+1. **Execute CLI First**: Always run CLI commands before any analysis
+2. **Use CLI for Writes**: All write operations must go through CLI
+3. **Read for Display Only**: Use file reading tools for display/analysis only
+4. **Never Modify .specfact/**: Do not create/modify files in `.specfact/` directly
+5. **Never Bypass Validation**: CLI ensures schema compliance and metadata
+
+## What Happens If You Don't Follow
+
+- ❌ Artifacts may not match CLI schema versions
+- ❌ Missing metadata and telemetry
+- ❌ Format inconsistencies
+- ❌ Validation failures
+- ❌ Works only in Copilot mode, fails in CI/CD
+
+## Available CLI Commands
+
+- `specfact plan init <bundle-name>` - Initialize project bundle
+- `specfact import from-code <bundle-name> --repo <path>` - Import from codebase
+- `specfact plan review <bundle-name>` - Review plan
+- `specfact plan harden <bundle-name>` - Create SDD manifest
+- `specfact enforce sdd <bundle-name>` - Validate SDD
+- `specfact sync bridge --adapter <adapter> --repo <path>` - Sync with external tools
+- See [Command Reference](../../docs/reference/commands.md) for full list

specfact_cli-0.11.2/resources/prompts/specfact.01-import.md

@@ -0,0 +1,61 @@
+---
+description: Import codebase → plan bundle. CLI extracts routes/schemas/relationships. LLM enriches with context.
+---
+
+# SpecFact Import Command
+
+## User Input
+
+```text
+$ARGUMENTS
+```
+
+You **MUST** consider the user input before proceeding (if not empty).
+
+## Purpose
+
+Import codebase → plan bundle. CLI extracts (routes, schemas, relationships, contracts). LLM enriches (context, "why", completeness).
+
+## Parameters
+
+**Target/Input**: `--bundle NAME` (required), `--repo PATH`, `--entry-point PATH`, `--enrichment PATH`  
+**Output/Results**: `--report PATH`  
+**Behavior/Options**: `--shadow-only`, `--enrich-for-speckit`  
+**Advanced/Configuration**: `--confidence FLOAT` (0.0-1.0), `--key-format FORMAT` (classname|sequential)
+
+## Workflow
+
+1. **Execute CLI**: `specfact import from-code <bundle> --repo <path> [options]`
+
+   CLI extracts (no AI): routes (FastAPI/Flask/Django), schemas (Pydantic), relationships (imports/deps), contracts (OpenAPI scaffolds), source tracking, bundle metadata.
+
+2. **LLM Enrichment** (if `--enrichment` provided):
+   - **Context file**: Read `.specfact/projects/<bundle>/enrichment_context.md` for relationships, contracts, schemas
+   - Use CLI output + bundle metadata + enrichment context as context
+   - Enrich: business context, "why" reasoning, missing acceptance criteria
+   - Validate: contracts vs code, feature/story alignment
+   - Complete: constraints, test scenarios, edge cases
+
+3. **Present**: Bundle location, report path, summary (features/stories/contracts/relationships)
+
+## CLI Enforcement
+
+**ALWAYS execute CLI first**. Never modify `.specfact/` directly. Use CLI output as grounding.
+
+## Expected Output
+
+**Success**: Bundle location, report path, summary (features/stories/contracts/relationships)  
+**Error**: Missing bundle name or bundle already exists
+
+## Common Patterns
+
+```bash
+/specfact.01-import --bundle legacy-api --repo .
+/specfact.01-import --bundle legacy-api --repo . --enrichment report.md
+/specfact.01-import --bundle auth-module --repo . --entry-point src/auth/
+/specfact.01-import --bundle legacy-api --repo . --enrich-for-speckit
+```
+
+## Context
+
+{ARGS}

specfact_cli-0.11.2/resources/prompts/specfact.02-plan.md

@@ -0,0 +1,151 @@
+---
+description: Manage project bundles - create, add features/stories, and update plan metadata.
+---
+
+# SpecFact Plan Management Command
+
+## User Input
+
+```text
+$ARGUMENTS
+```
+
+You **MUST** consider the user input before proceeding (if not empty).
+
+## Purpose
+
+Manage project bundles: initialize new bundles, add features and stories, and update plan metadata. This unified command replaces multiple granular commands for better LLM workflow integration.
+
+**When to use:**
+
+- Creating a new project bundle (greenfield)
+- Adding features/stories to existing bundles
+- Updating plan metadata (idea, features, stories)
+
+**Quick Example:**
+
+```bash
+/specfact.02-plan init legacy-api
+/specfact.02-plan add-feature --bundle legacy-api --key FEATURE-001 --title "User Auth"
+```
+
+## Parameters
+
+### Target/Input
+
+- `--bundle NAME` - Project bundle name (required for most operations)
+- `--key KEY` - Feature/story key (e.g., FEATURE-001, STORY-001)
+- `--feature KEY` - Parent feature key (for story operations)
+
+### Output/Results
+
+- (No output-specific parameters for plan management)
+
+### Behavior/Options
+
+- `--interactive/--no-interactive` - Interactive mode. Default: True (interactive)
+- `--scaffold/--no-scaffold` - Create directory structure. Default: True (scaffold enabled)
+
+### Advanced/Configuration
+
+- `--title TEXT` - Feature/story title
+- `--outcomes TEXT` - Expected outcomes (comma-separated)
+- `--acceptance TEXT` - Acceptance criteria (comma-separated)
+- `--constraints TEXT` - Constraints (comma-separated)
+- `--confidence FLOAT` - Confidence score (0.0-1.0)
+- `--draft/--no-draft` - Mark as draft
+
+## Workflow
+
+### Step 1: Parse Arguments
+
+- Determine operation: `init`, `add-feature`, `add-story`, `update-idea`, `update-feature`, `update-story`
+- Extract required parameters (bundle name, keys, etc.)
+
+### Step 2: Execute CLI
+
+```bash
+# Initialize bundle
+specfact plan init <bundle-name> [--interactive/--no-interactive] [--scaffold/--no-scaffold]
+
+# Add feature
+specfact plan add-feature --bundle <name> --key <key> --title <title> [--outcomes <outcomes>] [--acceptance <acceptance>]
+
+# Add story
+specfact plan add-story --bundle <name> --feature <feature-key> --key <story-key> --title <title> [--acceptance <acceptance>]
+
+# Update idea
+specfact plan update-idea --bundle <name> [--title <title>] [--narrative <narrative>] [--target-users <users>] [--value-hypothesis <hypothesis>] [--constraints <constraints>]
+
+# Update feature
+specfact plan update-feature --bundle <name> --key <key> [--title <title>] [--outcomes <outcomes>] [--acceptance <acceptance>] [--constraints <constraints>] [--confidence <score>] [--draft/--no-draft]
+
+# Update story
+specfact plan update-story --bundle <name> --feature <feature-key> --key <story-key> [--title <title>] [--acceptance <acceptance>] [--story-points <points>] [--value-points <points>] [--confidence <score>] [--draft/--no-draft]
+```
+
+### Step 3: Present Results
+
+- Display bundle location
+- Show created/updated features/stories
+- Present summary of changes
+
+## CLI Enforcement
+
+**CRITICAL**: Always use SpecFact CLI commands. See [CLI Enforcement Rules](./shared/cli-enforcement.md) for details.
+
+**Rules:**
+
+1. **ALWAYS execute CLI first**: Run appropriate `specfact plan` command before any analysis
+2. **ALWAYS use non-interactive mode for CI/CD**: Use `--no-interactive` flag in Copilot environments
+3. **NEVER modify .specfact folder directly**: All operations must go through CLI
+4. **NEVER create YAML/JSON directly**: All artifacts must be CLI-generated
+5. **Use CLI output as grounding**: Parse CLI output, don't regenerate it
+
+## Expected Output
+
+## Success (Init)
+
+```text
+✓ Project bundle created: .specfact/projects/legacy-api/
+✓ Bundle initialized with scaffold structure
+```
+
+## Success (Add Feature)
+
+```text
+✓ Feature 'FEATURE-001' added successfully
+Feature: User Authentication
+Outcomes: Secure login, Session management
+```
+
+## Error (Missing Bundle)
+
+```text
+✗ Project bundle name is required
+Usage: specfact plan <operation> --bundle <name> [options]
+```
+
+## Common Patterns
+
+```bash
+# Initialize new bundle
+/specfact.02-plan init legacy-api
+/specfact.02-plan init auth-module --no-interactive
+
+# Add feature with full metadata
+/specfact.02-plan add-feature --bundle legacy-api --key FEATURE-001 --title "User Auth" --outcomes "Secure login, Session management" --acceptance "Users can log in, Sessions persist"
+
+# Add story to feature
+/specfact.02-plan add-story --bundle legacy-api --feature FEATURE-001 --key STORY-001 --title "Login API" --acceptance "API returns JWT token" --story-points 5
+
+# Update feature metadata
+/specfact.02-plan update-feature --bundle legacy-api --key FEATURE-001 --title "Updated Title" --confidence 0.9
+
+# Update idea section
+/specfact.02-plan update-idea --bundle legacy-api --target-users "Developers, DevOps" --value-hypothesis "Reduce technical debt"
+```
+
+## Context
+
+{ARGS}

specfact_cli-0.11.2/resources/prompts/specfact.03-review.md

@@ -0,0 +1,152 @@
+---
+description: Review project bundle to identify ambiguities, resolve gaps, and prepare for promotion.
+---
+
+# SpecFact Review Command
+
+## User Input
+
+```text
+$ARGUMENTS
+```
+
+You **MUST** consider the user input before proceeding (if not empty).
+
+## Purpose
+
+Review project bundle to identify and resolve ambiguities, missing information, and unclear requirements. Asks targeted questions to make the bundle ready for promotion through development stages.
+
+**When to use:**
+
+- After creating or importing a plan bundle
+- Before promoting to review/approved stages
+- When plan needs clarification or enrichment
+
+**Quick Example:**
+
+```bash
+/specfact.03-review legacy-api
+/specfact.03-review legacy-api --max-questions 3 --category "Functional Scope"
+```
+
+## Parameters
+
+### Target/Input
+
+- `bundle NAME` (required argument) - Project bundle name (e.g., legacy-api, auth-module)
+- `--category CATEGORY` - Focus on specific taxonomy category. Default: None (all categories)
+
+### Output/Results
+
+- `--list-questions` - Output questions in JSON format. Default: False
+- `--list-findings` - Output all findings in structured format. Default: False
+- `--findings-format FORMAT` - Output format: json, yaml, or table. Default: json for non-interactive, table for interactive
+
+### Behavior/Options
+
+- `--no-interactive` - Non-interactive mode (for CI/CD). Default: False (interactive mode)
+- `--answers JSON` - JSON object with question_id -> answer mappings. Default: None
+- `--auto-enrich` - Automatically enrich vague acceptance criteria. Default: False
+
+### Advanced/Configuration
+
+- `--max-questions INT` - Maximum questions per session. Default: 5 (range: 1-10)
+
+## Workflow
+
+### Step 1: Parse Arguments
+
+- Extract bundle name (required)
+- Extract optional parameters (max-questions, category, etc.)
+
+### Step 2: Execute CLI
+
+```bash
+# Interactive review
+specfact plan review <bundle-name> [--max-questions <n>] [--category <category>]
+
+# Non-interactive with answers
+specfact plan review <bundle-name> --no-interactive --answers '{"Q001": "answer1", "Q002": "answer2"}'
+
+# List questions only
+specfact plan review <bundle-name> --list-questions
+
+# List findings
+specfact plan review <bundle-name> --list-findings --findings-format json
+```
+
+### Step 3: Present Results
+
+- Display questions asked and answers provided
+- Show sections touched by clarifications
+- Present coverage summary by category
+- Suggest next steps (promotion, additional review)
+
+## CLI Enforcement
+
+**CRITICAL**: Always use SpecFact CLI commands. See [CLI Enforcement Rules](./shared/cli-enforcement.md) for details.
+
+**Rules:**
+
+1. **ALWAYS execute CLI first**: Run `specfact plan review` before any analysis
+2. **ALWAYS use non-interactive mode for CI/CD**: Use `--no-interactive` flag in Copilot environments
+3. **NEVER modify .specfact folder directly**: All operations must go through CLI
+4. **NEVER create YAML/JSON directly**: All plan updates must be CLI-generated
+5. **Use CLI output as grounding**: Parse CLI output, don't regenerate it
+
+## Expected Output
+
+### Success
+
+```text
+✓ Review complete: 5 question(s) answered
+
+Project Bundle: legacy-api
+Questions Asked: 5
+
+Sections Touched:
+  • idea.narrative
+  • features[FEATURE-001].acceptance
+  • features[FEATURE-002].outcomes
+
+Coverage Summary:
+  ✅ Functional Scope: clear
+  ✅ Technical Constraints: clear
+  ⚠️ Business Context: partial
+```
+
+### Error (Missing Bundle)
+
+```text
+✗ Project bundle 'legacy-api' not found
+Create one with: specfact plan init legacy-api
+```
+
+## Common Patterns
+
+```bash
+# Interactive review
+/specfact.03-review legacy-api
+
+# Review with question limit
+/specfact.03-review legacy-api --max-questions 3
+
+# Review specific category
+/specfact.03-review legacy-api --category "Functional Scope"
+
+# Non-interactive with answers
+/specfact.03-review legacy-api --no-interactive --answers '{"Q001": "answer1", "Q002": "answer2"}'
+
+# List questions for LLM processing
+/specfact.03-review legacy-api --list-questions
+
+# List all findings
+/specfact.03-review legacy-api --list-findings --findings-format json
+
+# Auto-enrich mode
+/specfact.03-review legacy-api --auto-enrich
+```
+
+## Context
+
+{ARGS}