prompts-gpt 0.2.19 → 0.3.2

package/README.md

@@ -108,6 +108,9 @@ prompts-gpt sweep --dry-run
 # Run and score multiple providers on one prompt
 prompts-gpt orchestrate --mode parallel -f .prompts-gpt/review.md --providers codex,claude,cursor --criteria correctness,completeness
 
+# Interactive orchestration mode picker
+prompts-gpt orchestrate
+
 # Chain steps with context passing
 cat > pipeline.json <<'EOF'
 [
@@ -122,6 +125,9 @@ prompts-gpt orchestrate --mode pipeline --steps pipeline.json --dry-run
 prompts-gpt orchestrate --mode eval -f .prompts-gpt/review.md --criteria correctness,risk,clarity
 prompts-gpt orchestrate --mode eval --dry-run --eval-criteria correctness,risk,clarity
 
+# Inspect available models for the resolved orchestration providers
+prompts-gpt orchestrate --mode eval --list-models
+
 # Re-run a prompt when the file changes
 prompts-gpt run -f .prompts-gpt/review.md --watch
 
@@ -141,12 +147,11 @@ prompts-gpt models --provider codex
 # Sync model registry from cloud
 prompts-gpt sync-models
 
-# Use model aliases for shorter commands
-prompts-gpt run --model opus     # resolves to claude-opus-4-7
-prompts-gpt run --agent cursor --model opus-4.6  # resolves to claude-4.6-opus-high
-prompts-gpt run --model mini     # resolves to gpt-5.4-mini
-prompts-gpt run --model pro      # resolves to gpt-5.5-pro
-prompts-gpt run --model o3       # resolves to o3
+# Use canonical model names only
+prompts-gpt run --agent claude --model claude-opus-4-7
+prompts-gpt run --agent cursor --model claude-4.6-opus-high
+prompts-gpt run --agent codex --model gpt-5.4-mini
+prompts-gpt run --agent codex --model gpt-5.5
 
 # Sync from cloud
 prompts-gpt sync --agent all
@@ -179,7 +184,7 @@ All options can be overridden via environment variables. See `prompts-gpt help s
 
 ## Orchestration Patterns
 
-- `parallel`: run multiple providers against the same prompt, score outputs, and keep the strongest result with local logs and diffs.
+- `parallel`: run multiple providers against the same prompt, score outputs, and report the strongest result with local logs and diffs.
 - `pipeline`: pass context across named steps when research, implementation, and review should be separated.
 - `eval`: run one provider and force a structured quality score for the output.
 - `eval --dry-run`: if `-f` is omitted, the CLI uses the first discovered `.prompts-gpt` prompt so workspace scaffolds can verify orchestration immediately.
@@ -188,6 +193,24 @@ All options can be overridden via environment variables. See `prompts-gpt help s
 - `run --watch`: rerun automatically when the prompt file changes.
 - `doctor --fix`: scaffold `.prompts-gpt/config.json`, detect prompt sources, and add the artifacts directory to `.gitignore`.
 
+### Visibility implementation workflow
+
+Use orchestration after a monitor or checker identifies a concrete gap:
+
+1. Export the prompt, answer evidence, cited URLs, and desired fix from Prompts-GPT.com.
+2. Run `prompts-gpt orchestrate --mode parallel` when multiple agents should propose competing fixes.
+3. Run `prompts-gpt orchestrate --mode pipeline` when research, implementation, and review should stay separated.
+4. Run `prompts-gpt orchestrate --mode eval` or `prompts-gpt sweep --eval --eval-criteria correctness,risk,clarity` when output quality needs a score.
+5. Run `prompts-gpt diff <run-id>` before sharing the worktree changes.
+
+Dry-runs verify command wiring, prompt resolution, evaluator selection, and criteria parsing without launching a provider:
+
+```bash
+npx prompts-gpt orchestrate --mode eval --dry-run --eval-criteria correctness,risk,clarity
+```
+
+Full pattern guide (parallel vs pipeline vs eval, visibility handoff, diff/watch): [docs/orchestration-patterns.md](../../docs/orchestration-patterns.md) in the main repo.
+
 ---
 
 ## SDK