Repository navigation
refactor(plugin)!: Rename to corpflow and collapse the seam to one CORPFLOW.md - #15
Merged
Merged
Conversation
The corpflow plugin (formerly company-workflow, formerly igrsoft) renamed its plugin id in its 4.0.13 release, following the repository rename to IGRSoft/corpflow. Every corpflow:<agent|skill> id this plugin names, and the Task(company-workflow:...) grants in agent frontmatter, resolve through that id, so they stop resolving until this lands. Prose drops the doubled noun rather than carrying it across the rename: "inside a company-workflow workflow" became "inside corpflow", and "company-workflow 11-stage workflow system" became "corpflow 11-stage pipeline", reusing the word corpflow's own README uses for the stage chain. Compatibility pins move to v4.0.13. Version markers that record WHEN a contract or field landed keep their original version -- the artifact filename contract, the handoff frontmatter schema, and ui_visual_check were introduced at v4.0.0 and still were. CHANGELOG history is left verbatim, since a changelog row records what shipped under the name in force at the time. BREAKING CHANGE: requires corpflow >= 4.0.13. The company-workflow:* ids these docs previously named no longer resolve and there is no back-compat alias.
Corpflow knowledge was spread across agents, commands, skills, hooks, manifests and the README -- 20-40 files. Two renames this month each had to sweep all of them. The integration is now one file at the repository root, CORPFLOW.md, generated from corpflow's template. Delete that file and this plugin is standalone with no other edit; restore it and it participates in worktasks again. Removed, because their content is now in CORPFLOW.md: - the skills/_shared/workflow-integration skill tree - per-agent "Workflow Integration" / "Workflow Stage Participation" / "Workflow Collaboration" sections; agents no longer carry a corpflow preamble, because corpflow injects "Read CORPFLOW.md and follow it" at dispatch time - the corpflow companion docs under docs/ Hooks now say "the orchestrator" rather than naming corpflow. They were always orchestrator-agnostic by design -- emitting advisory rows with a matching dedupe_key and standing alone when no orchestrator is present -- so naming corpflow in a comment coupled a file that had no reason to be coupled. The compatibility pin moves out of the README badge and into CORPFLOW.md's "Targets corpflow" row, so there is one place to bump.
This plugin's own multi-stage commands borrowed orchestrator agents by id, which made every one of them a second corpflow seam. They now name the role -- "the orchestrator's architect" -- and CORPFLOW.md maps role to id, so the id appears in exactly one file. Behaviour is unchanged when corpflow is present. When CORPFLOW.md is absent the plugin is standalone and those phases are skipped rather than failed. Shared standards (code-comment-standard, security-review-process, claude-constitution, logging-conventions) stay referenced by id. They are vocabulary rather than orchestration; vendoring copies would let the wording drift, and a drifting standard is worse than a named one.
ikorich
changed the title
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.
Motivation
Two changes that belong together. The corpflow plugin (formerly
company-workflow, formerlyigrsoft) renamed its plugin id in its 4.0.13 release — and doing that rename exposed why it hurt so much.Corpflow knowledge lived in 20–40 files here: per-agent intake preambles, a
workflow-integrationskill tree, stage-handoff references, command delegations, hook comments, manifest blurbs, README sections. That is two renames this month that each had to sweep all of them. A seam that costs dozens of file edits every time it moves is the bug.The integration is now one file at the repository root: CORPFLOW.md. Delete it and this plugin is standalone with no other edit; restore it and it participates in worktasks again.
Companion to IGRSoft/corpflow#286, which must merge first.
Changes
Renamed — every
company-workflow:<agent|skill>id andTask(...)grant →corpflow:;COMPANY_WORKFLOW_DIR→CORPFLOW_DIRwhere present.Collapsed to one seam. Removed, because their content is now in
CORPFLOW.md:skills/_shared/workflow-integrationskill treeRead CORPFLOW.md and follow itat dispatch timedocs/Hooks say "the orchestrator" rather than naming corpflow. They were always orchestrator-agnostic by design — advisory rows with a matching
dedupe_key, standing alone when no orchestrator is present — so naming corpflow in a comment coupled a file that had no reason to be coupled.Commands name roles, not ids. This plugin's own multi-stage commands borrowed orchestrator agents by id, making each one a second seam. They now say "the orchestrator's architect";
CORPFLOW.mdmaps role → id. Behaviour is unchanged when corpflow is present; without it those phases are skipped rather than failed.Kept: shared standards (
corpflow:code-comment-standard,corpflow:security-review-process,claude-constitution,logging-conventions) are still referenced by id. They are vocabulary rather than orchestration, and vendoring copies into each plugin would let the wording drift — a drifting standard is worse than a named one.The compatibility pin moves out of the README badge into
CORPFLOW.md's "Targets corpflow" row, so there is one place to bump.Test plan
scripts/validate.sh— 0 errors, 0 warnings (repos that ship it).bash -n; both manifests parse as JSON.CORPFLOW.mdwith computed relative paths; zero dangling links remain.company-workflowoutside CHANGELOG history; nocorpflowoutsideCORPFLOW.md, MEMORY/CHANGELOG history, and the kept standards.corpflow:<id>this repo names resolves.Notes
BREAKING: requires corpflow >= 4.0.13. The
company-workflow:*ids these docs previously named no longer resolve and there is no back-compat alias.MEMORY.md and CHANGELOG.md keep their original text — they record what shipped under the name in force at the time.