feat: rewrite authoring bundle creation as wizard-style flow @W-21220749@ #326
+493
−54
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Replace autocomplete spec selector with two-step type picker and file picker from specs/ directory. Remove interactive API name prompt in favor of auto-generation. Add MultiStageOutput progress reporting.
Add 18 unit tests covering flag-based usage, interactive wizard prompts, name/API name validation, error handling, and spec file filtering. Also restore the interactive API name prompt and refine wizard prompt text.
Contributor
jshackell-sfdc
left a comment
jshackell-sfdc
left a comment
There was a problem hiding this comment.
See my edits. NOTE that I'm not sure where these messages really appear, so I'm making a guess. Please fix things like incorrect punctuation (like me adding a period when there shouldn't be), etc.
| # error.failed-to-create-agent | ||
|
|
||
| Failed to create an authoring bundle from the agent spec YAML file. | ||
| Failed to generate authoring bundle: %s |
Contributor
There was a problem hiding this comment.
Suggested change
| Failed to generate authoring bundle: %s | |
| Failed to generate authoring bundle: %s. |
|
|
||
| # wizard.specType.prompt | ||
|
|
||
| Select authoring bundle template |
Contributor
There was a problem hiding this comment.
Suggested change
| Select authoring bundle template | |
| Select an authoring bundle template |
|
|
||
| # wizard.specType.option.default.name | ||
|
|
||
| Default template (recommended) |
Contributor
There was a problem hiding this comment.
Suggested change
| Default template (recommended) | |
| Default template (Recommended) |
|
|
||
| # wizard.specType.option.fromSpec.name | ||
|
|
||
| From YAML spec (advanced) |
Contributor
There was a problem hiding this comment.
Suggested change
| From YAML spec (advanced) | |
| From an agent spec YAML file (Advanced) |
|
|
||
| # wizard.specType.option.default.description | ||
|
|
||
| Start with a ready-to-use Agent Script template |
Contributor
There was a problem hiding this comment.
Suggested change
| Start with a ready-to-use Agent Script template | |
| Start with a ready-to-use Agent Script template. |
|
|
||
| # wizard.specFile.prompt | ||
|
|
||
| Select authoring bundle YAML spec |
Contributor
There was a problem hiding this comment.
Suggested change
| Select authoring bundle YAML spec | |
| Select the agent spec YAML file. |
|
|
||
| # wizard.name.prompt | ||
|
|
||
| Enter authoring bundle name |
Contributor
There was a problem hiding this comment.
Suggested change
| Enter authoring bundle name | |
| Enter the authoring bundle name. |
|
|
||
| # wizard.name.validation.required | ||
|
|
||
| Bundle name is required |
Contributor
There was a problem hiding this comment.
Suggested change
| Bundle name is required | |
| Authoring bundle name is required. |
|
|
||
| # wizard.name.validation.empty | ||
|
|
||
| Bundle name can't be empty. |
Contributor
There was a problem hiding this comment.
Suggested change
| Bundle name can't be empty. | |
| Authroring bundle name can't be empty. |
|
|
||
| # warning.noSpecDir | ||
|
|
||
| No agent spec directory found at %s |
Contributor
There was a problem hiding this comment.
Suggested change
| No agent spec directory found at %s | |
| No agent spec directory found at %s. |
WillieRuemmele
approved these changes
Feb 10, 2026
Contributor
WillieRuemmele
left a comment
WillieRuemmele
left a comment
There was a problem hiding this comment.
all seems fine, personally, I feel that the MSO is excessive, given it's a 17ms operation
──── Generating authoring bundle: my_agent_2 ────
✔ Creating authoring bundle structure... 4ms
✔ Generating Agent Script file... 5ms
✔ Complete! 0ms
Elapsed Time: 17ms
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Rewrites the
agent generate authoring-bundleinteractive flow to use a wizard-style pattern that mirrors the VS Code extension. Replaces the autocomplete spec selector with a two-step approach (template type picker → YAML spec file picker fromspecs/directory), addsMultiStageOutputprogress reporting, and updates all user-facing prompt text. Includes 18 unit tests covering the full wizard flow.What issues does this PR fix or reference?
@W-21220749@
Functionality Before
*AgentSpec.yml/yamlfilesFunctionality After
specs/directoryMultiStageOutputprogress stages: "Creating authoring bundle structure..." → "Generating Agent Script file..." → "Complete!"-testSpec) are filtered out of the spec file listTesting Setup Notes
specs/directory exists at the project root with.yaml/.ymlfilessf agent generate authoring-bundleinteractively to verify:sf agent generate authoring-bundle --no-spec --name "Test" --api-name TestAgent --target-org <org>--specwith a direct path to verify it bypasses wizard promptsnpx mocha "test/commands/agent/generate/authoring-bundle.test.ts"