Skip to content

Add great-cto to Workflow Orchestration - #441

Open
avelikiy wants to merge 1 commit into
ccplugins:mainfrom
avelikiy:add-great-cto
Open

Add great-cto to Workflow Orchestration#441
avelikiy wants to merge 1 commit into
ccplugins:mainfrom
avelikiy:add-great-cto

Conversation

@avelikiy

@avelikiy avelikiy commented Sep 3, 2026

Copy link
Copy Markdown

Adds great-cto — a Claude Code plugin that runs the tool as a pipeline of specialist agents instead of a single one: architecture, product, implementation, QA, security and deploy, with an independent model reviewing each stage before the next begins and human gates on the steps that are expensive to undo.

On the source field

Listed with an external source — the same shape tree-ring-memory and trigger-tree use — rather than vendoring the plugin into ./plugins. At 71 agents, 44 commands and 39 skills a copy here would be large, and it would drift from the upstream it was copied from. Happy to vendor it instead if that is preferred.

Changes

  • README.md — one row, inserted in the existing order of Workflow Orchestration without reordering the neighbouring entries
  • .claude-plugin/marketplace.json — one entry, category Workflow Orchestration

great_cto runs Claude Code as a pipeline of specialist agents rather than a
single one: architecture, product, implementation, QA, security and deploy,
with an independent model reviewing each stage before the next begins and human
gates on the steps that are expensive to undo.

Listed with an external `source` (as tree-ring-memory and trigger-tree are)
rather than vendoring the plugin into ./plugins — it is 71 agents, 44 commands
and 39 skills, and a copy here would drift from the upstream it is copied from.

- Repository: https://github.com/avelikiy/great_cto
- npm: great-cto@3.22.0
- Docs: https://greatcto.systems
- MIT licensed
avelikiy added a commit to avelikiy/great_cto that referenced this pull request Sep 3, 2026
Submitted as ccplugins/awesome-claude-code-plugins#441. Tracked as `pending`,
not `listed`: absence there is the expected reading until the PR is merged, and
the third column exists precisely so a wait does not file an issue every Monday.
Move it to `listed` when it lands, and the check starts guarding it.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants