[ctawiah]

Context

The previous PR added the variation create behind AddAction.Create. This PR adds the flags of sync prompts add, and the hint for a variation that LaunchDarkly does not have.

What changes

• sync prompts add gets --content, --model-config-key, --name, and --yes. --content turns the add into a create.
• The help describes both forms, and how the content becomes the prompt of an agent config or of a completion config. It has an example of a create without prompting.
• The project-key/config-key/variation-key form still adds variations that exist. With a create flag, it is an error.
• The error for a variation that LaunchDarkly does not have names the add that creates it:

variation "escalation" does not exist in config "support" in project "demo". To create it, run ldcli sync prompts add --project demo --config-key support --key escalation with --model-config-key and --content.

The new example in the help:

  # Create an agent variation without prompting
  ldcli sync prompts add --project production --config-key support --key escalation \
    --model-config-key claude \
    --content "Hand the conversation to a person when the customer asks for one." \
    --yes --no-input

Design notes

• The hint names the whole add command, for the same reason as for tools: sync prompts also starts this add in a repository without sync files.
• The help now has three examples: choose interactively, add by key, and create. The example that chose variations in one config is gone, because the add by key already shows --project and --config-key.

Review focus

• Is the help clear about the difference between the content of an agent config and of a completion config?

Verification

• go test ./... and golangci-lint run (v2.9.0) pass.
• These new tests failed before the change:
  • the exact flags of sync prompts add, and the create input from its flags
  • the hint for a missing variation
  • a create through the command, and the refusal of a selector with create flags
• I built ldcli and ran a flag-only script against a stand-in for the LaunchDarkly API:
  • the help, and an add without a content flag
  • every flag error, with no request
  • an agent create: a dry run with --diff, no --yes, and --yes
  • completion creates from role blocks and from plain text, and a bad role block
  • an adopt with a newer model config version
  • the refusals, the archived key, a missing model config, and a rejected create that removes its file
• I also ran a create in a terminal: the project, config, key, model config, and name questions, and then the confirmation. While the question waited, the file did not exist.

Related changes

This stack builds on #937 to #941, which are merged.

1. fix: exclude expanded tools from prompt diffs #957: Exclude expanded tools from prompt diffs (ctawiah/fix-prompt-tool-diff-5b1c)
2. fix: plan a tool or skill row when a variation newly references it #945: Plan a tool or skill row when a variation newly references it (ctawiah/plan-referenced-attachments-1e8a)
3. feat: keep unused tools and skills, and detach any resource kind #946: Keep unused tools and skills, and detach any resource kind (ctawiah/keep-unused-attachments-1e8a)
4. feat: add tools and skills from LaunchDarkly #947: Add tools and skills from LaunchDarkly (ctawiah/add-attachments-1e8a)
5. feat: route sync, add, and detach by scope #948: Route sync, add, and detach by scope (ctawiah/route-scopes-1e8a)
6. feat: add the sync all, sync tools, and sync skills commands #949: Add the sync all, sync tools, and sync skills commands (ctawiah/scope-commands-1e8a)
7. feat: create a tool or a skill from the content of an add #950: Create a tool or a skill from the content of an add (ctawiah/create-attachments-1e8a)
8. feat: add the create flags of sync tools add and sync skills add #951: Add the create flags of sync tools add and sync skills add (ctawiah/create-attachment-flags-1e8a)
9. refactor: share the selection of a new variation, and check any kind before an add #952: Share the selection of a new variation, and check any kind before an add (ctawiah/share-variation-selection-1e8a)
10. feat: create a prompt variation from the content of an add #953: Create a prompt variation from the content of an add (ctawiah/create-variations-1e8a)
11. This PR: add the create flags of sync prompts add (ctawiah/create-variation-flags-1e8a)

---

Note

Overview
ldcli sync prompts add can now create a prompt variation in LaunchDarkly (not only sync existing ones). --content switches add into create mode; --model-config-key, --name, and --yes complete non-interactive creation. Help and examples document agent vs completion content shapes.

Shared createInput now maps model-config-key into synccreate.Input for prompt add (alongside tools/skills). Positional project/config/variation selectors are rejected when any create flag is set—create targets must use --project, --config-key, and --key.

Bootstrap errors for unknown variations point users at the full add command with --model-config-key and --content; archived keys get a separate restore-or-pick-another-key message.

^{Reviewed by Cursor Bugbot for commit 3073a87. Bugbot is set up for automated code reviews on this repo. Configure here.}

[nkester-ld]

Should we check if the variation is in the list of archived for the project before saying it doesn't exist?
Like:

if slices.Contains(config.ArchivedVariationKeys, variationKey) {
    return nil, fmt.Errorf(
        "variation %q in config %q in project %q is archived in LaunchDarkly. Restore it in LaunchDarkly, or pass another --key to create a new variation.",
        variationKey, configKey, selection.ProjectKey,
    )
}

[cursor]

Good catch. The config response already includes archived variation keys, so this path has the data that it needs. I reproduced the current “does not exist” error with TestRunExplainsThatASelectedVariationIsArchived. Fixed in 3073a87. An archived key now tells the user to restore it in LaunchDarkly or pass another --key.