Unify workflow/pipeline nomenclature (user-facing → workflow, pipeline alias)#634
Open
bborn wants to merge 4 commits into
Open
Unify workflow/pipeline nomenclature (user-facing → workflow, pipeline alias)#634bborn wants to merge 4 commits into
bborn wants to merge 4 commits into
Conversation
…, pipeline alias) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Implements PLAN.md. NOTE: session was evicted before the Code agent ran the test suite; TestToolsList still references the old MCP tool name and fails — left for the Verify step to catch and resolve. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Addresses the one blocking issue from REVIEW.md: TestToolsList asserted the old taskyou_create_pipeline tool name. Updated to taskyou_create_workflow. Full suite (go test ./...) is green. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.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
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.
Produced by the plan-code-verify workflow (dogfooding run), Plan → Code → Review → Verify on one shared branch.
What
Unify the user-facing "pipeline" vs "workflow" nomenclature. Settles on workflow as the single user-facing term (CLI command,
taskyou_create_workflowMCP tool, help text, docs) while keeping a backward-compatiblepipelineCLI alias so existing scripts/muscle memory keep working. No behavior change — naming/wording only.Workflow artifacts on the branch
PLAN.md— the plan (Plan step)REVIEW.md— independent review; flagged 1 blocking issue (Review step)VERIFY.md— verification evidence (Verify step)Review → Verify
Review flagged one blocking issue:
TestToolsListstill asserted the oldtaskyou_create_pipelinetool name. Verify fixed it (taskyou_create_workflow) and confirmed the suite.Verification
go build ./...cleango test ./...all packages PASSty workflow --listandty pipeline --list(alias) both resolve🤖 Generated with Claude Code