[rig-claude] Improve Claude dynamic-workflow compatibility for rig - #366
Draft
github-actions[bot] wants to merge 1 commit into
Draft
[rig-claude] Improve Claude dynamic-workflow compatibility for rig#366github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
Add sample 360 (parallel destructuring) to the example programs table in claude-workflow-conversion.md. The [a, b] = await parallel([...]) pattern is the most common Claude dynamic workflow idiom for a fixed set of concurrent calls and had no entry in the conversion guide. Also add the back-link to claude-workflow-conversion.md in the 360 sample header, consistent with 320 and 330. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Compatibility gap addressed
The
paralleldestructuring pattern —const [a, b] = await parallel([() => ..., () => ...])— is the most common Claude dynamic workflow idiom for a fixed set of concurrent calls. Sample360-parallel-branch-analysis-workflow.mdalready demonstrates this pattern, but it was absent from the Example programs table inclaude-workflow-conversion.md. A user porting a Claude workflow with positionalparallelresults would not find this sample from the conversion guide.Why this improves transfer
Adding the 360 sample row to the conversion guide gives Claude dynamic workflow users a direct pointer to a worked example of the most frequent
parallelpattern. Combined with the back-link added to the sample itself (matching the style of 320/330), discovery is now bidirectional.Files changed
skills/rig/references/claude-workflow-conversion.md— added 360 to the Example programs tableskills/rig/samples/360-parallel-branch-analysis-workflow.md— addedSee [claude-workflow-conversion.md](...)back-link, consistent with 320 and 330Validation run
npm run typecheck— exits 0 (project-wide typecheck passes, no API changes).Docs-only change; no test logic changed.
Remaining intentional differences
{ effort: "high" }— not modeled in rig{ agentType: "Explore" }— no built-in read-only type; covered by prompt wording + narrow tools list