[rig-claude] Improve Claude dynamic-workflow compatibility for rig - #505
Merged
Merged
Conversation
Add a navigation table near the top of the conversion reference that routes a Claude dynamic-workflow developer to the right sample based on their script's structure (flat, canonical, nested, budget/log, multi-stage pipeline, or Anthropic engine). Fixes the discoverability gap where the relevant migration samples were listed only at the bottom of the doc after the reader had already parsed the full primitive table. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
Author
|
🧠 Matt Pocock Skills Reviewer has completed the skills-based review. ✅ |
Contributor
Author
There was a problem hiding this comment.
Skills-Based Review 🧠
Applied /grill-with-docs — no blocking issues. The routing table is well-structured and all links verified.
📋 Key Themes & Highlights
Positive Highlights
- ✅ All six relative links resolve to existing sample files
- ✅
#behavior-differences-to-keep-in-mindanchor is valid - ✅ Routing table placed before the primitive-mapping table — good information architecture
- ✅ Row descriptions match structural patterns Claude developers would recognize
- ✅ Consistent vocabulary with the rest of the reference doc
🧠 Reviewed using Matt Pocock's skills by Matt Pocock Skills Reviewer · sonnet46 19.3 AIC · ⌖ 4.04 AIC · ⊞ 6.3K
Comment /matt to run again
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
注册 for free
to join this conversation on GitHub.
Already have an account?
登录 to comment
1 participant
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
skills/rig/references/claude-workflow-conversion.mdhad no navigation entry point near the top. A Claude dynamic-workflow developer landing on the page needed to scan the entire primitive-mapping table before reaching the sample links at the bottom — the most common discoverability gap when transferring knowledge.Why this improves transfer
Added a "Where to start" routing table immediately after the one-paragraph intro, before the primitive table. Each row matches a structural pattern a Claude developer would recognize in their own script, and links directly to the most relevant rig sample:
args→inputbody workflowworkflow(ref, args)log/budget/whilelooppipelineThe table also points the reader to the "Behavior differences" section before they finalize a port.
Files changed
skills/rig/references/claude-workflow-conversion.md— 15 lines addedValidation
Docs-only change. Verified all six relative links resolve to existing sample files. No API, test, or TypeScript changes were made.
Remaining intentional differences
All existing intentional differences (
effort,agentType, pipeline stage signature, budget denominator) are already documented in the "Behavior differences" section. No new gaps were introduced.