Technical architecture review agent for execution plans. An agent skill from Ibrahim-3d/orchestrator-supaconductor.
$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill cto-plan-reviewer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Ibrahim-3d/orchestrator-supaconductor cto-plan-reviewer --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/cto-plan-reviewer .claude/skills/cto-plan-reviewer && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "cto-plan-reviewer" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/cto-plan-reviewer into .claude/skills/cto-plan-reviewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cto-plan-reviewer", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/cto-plan-reviewerType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill cto-plan-reviewer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Ibrahim-3d/orchestrator-supaconductor cto-plan-reviewer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/cto-plan-reviewer .agents/skills/cto-plan-reviewer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cto-plan-reviewer" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/cto-plan-reviewer into .agents/skills/cto-plan-reviewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cto-plan-reviewer", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill cto-plan-reviewer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Ibrahim-3d/orchestrator-supaconductor cto-plan-reviewer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/cto-plan-reviewer .cursor/skills/cto-plan-reviewer && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "cto-plan-reviewer" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/cto-plan-reviewer into .cursor/skills/cto-plan-reviewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cto-plan-reviewer", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Ibrahim-3d/orchestrator-supaconductor.git --path skills/cto-plan-reviewer--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill cto-plan-reviewer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Ibrahim-3d/orchestrator-supaconductor cto-plan-reviewer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/cto-plan-reviewer .gemini/skills/cto-plan-reviewer && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "cto-plan-reviewer" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/cto-plan-reviewer into .gemini/skills/cto-plan-reviewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cto-plan-reviewer", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Ibrahim-3d/orchestrator-supaconductor cto-plan-reviewerInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill cto-plan-reviewer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/cto-plan-reviewer .github/skills/cto-plan-reviewer && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "cto-plan-reviewer" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/cto-plan-reviewer into .github/skills/cto-plan-reviewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cto-plan-reviewer", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Ibrahim-3d/orchestrator-supaconductor --skill cto-plan-reviewer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Ibrahim-3d/orchestrator-supaconductor cto-plan-reviewer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Ibrahim-3d/orchestrator-supaconductor.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/cto-plan-reviewer .opencode/skills/cto-plan-reviewer && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "cto-plan-reviewer" agent skill from https://github.com/Ibrahim-3d/orchestrator-supaconductor/tree/master/skills/cto-plan-reviewer into .opencode/skills/cto-plan-reviewer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cto-plan-reviewer", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
cto-plan-reviewerTechnical architecture review agent for execution plans. An agent skill from Ibrahim-3d/orchestrator-supaconductor.
Cto Plan Reviewer is an agent skill from Ibrahim-3d/orchestrator-supaconductor. Technical architecture review agent for execution plans. Uses cto-advisor skill to evaluate technical decisions, architecture patterns, tech debt implications, and technology choices in plan.md. Triggered by: 'review technical plan', 'cto review', 'architecture review', or automatically during Step 2 (Evaluate Plan) for tracks involving architecture decisions, integrations, or infrastructure changes.
Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Software architecture and Technical debt. The repository describes itself as: Multi-agent orchestration system for Claude Code with parallel execution, automated quality gates, Board of Directors, and bundled Superpowers skills. The licence is AGPL-3.0.
8 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 76c9b10. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
claudeFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Cto Plan Reviewer loads about 2.9k tokens when it runs. Until then it costs about 105 tokens; SKILL.md has 684 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from Ibrahim-3d/orchestrator-supaconductor at commit 76c9b10, republished under its AGPL-3.0 licence (© Ibrahim-3d). 684 words, ~2,920 tokens.
.claude/skills/cto-plan-reviewer/SKILL.md (or your agent's skills folder).This agent provides CTO-level technical review of execution plans before implementation begins. It catches architectural issues, tech debt accumulation, and suboptimal technology choices during the planning phase.
Automatically invoked during Step 2: EVALUATE PLAN when the track involves:
Also manually invocable via:
claude /cto-advisorplan.md -- execution plan to reviewspec.md -- requirements and contextconductor/tech-stack.md -- current technology decisionsconductor/product.md -- product requirements and constraintsThe agent leverages the cto-advisor skill to perform deep technical analysis across multiple dimensions:
| Check | Uses CTO Advisor For |
|---|---|
| Architecture patterns | Evaluate proposed patterns against team topologies, scalability needs |
| Design decisions | ADR template guidance, decision documentation quality |
| System design | Component boundaries, separation of concerns, modularity |
| Technology standards | Alignment with existing stack, consistency |
CTO Advisor Frameworks Used:
| Check | Uses CTO Advisor For |
|---|---|
| Debt introduction | Will this plan create technical debt? Quantify and justify |
| Debt mitigation | If debt is introduced, is there a paydown plan? |
| Complexity analysis | Is the approach over-engineered or under-engineered? |
| Maintenance burden | Long-term ownership and maintenance implications |
CTO Advisor Tools Used:
| Check | Uses CTO Advisor For |
|---|---|
| Technology choices | Are new libraries/services necessary and well-justified? |
| Vendor dependencies | Lock-in risk, SLA monitoring, cost implications |
| Integration complexity | API design, error handling, retry logic |
| Cost implications | Infrastructure costs, API usage costs, scaling costs |
CTO Advisor Frameworks Used:
| Check | Uses CTO Advisor For |
|---|---|
| Testing strategy | Coverage targets, test types, TDD applicability |
| Performance criteria | Load requirements, optimization strategy |
| Security review | OWASP top 10, input validation, auth patterns |
| Observability | Monitoring, logging, alerting, debugging |
CTO Advisor Metrics Used:
| Check | Uses CTO Advisor For |
|---|---|
| Complexity appropriateness | Can the team execute this plan effectively? |
| Knowledge distribution | Single points of failure in knowledge? |
| Onboarding impact | Will this make onboarding harder? |
| Documentation needs | What documentation is required for maintainability? |
CTO Advisor Principles Used:
Use context-loader skill to efficiently load:
plan.md and spec.mdconductor/tech-stack.md -- current stack decisionsconductor/product.md -- product constraintsFor each technical aspect of the plan, invoke relevant cto-advisor frameworks:
For architecture decisions:
- Apply ADR template guidance
- Check system design review criteria
- Validate against technology standards
For tech debt concerns:
- Run tech debt analyzer concepts
- Apply debt strategy allocation principles
- Check red flags
For new technologies:
- Apply technology evaluation framework
- Assess vendor management needs
- Calculate cost implications
For quality:
- Check against DORA metrics targets
- Verify testing strategy
- Validate security checklist## CTO Technical Review Report
**Track**: [track-id]
**Reviewer**: cto-plan-reviewer (using cto-advisor frameworks)
**Date**: [YYYY-MM-DD]
### Architecture Assessment
#### Design Decisions
- [x] Architecture pattern: [pattern name] -- appropriate for [reason]
- [ ] CONCERN: [specific issue with decision]
- Recommendation: [specific guidance from ADR framework]
#### System Design
- [x] Component boundaries clear and well-defined
- [x] Separation of concerns maintained
- [ ] CONCERN: Tight coupling between [module A] and [module B]
- Recommendation: [refactoring suggestion]
### Tech Debt Analysis
#### Debt Introduction: [NONE / LOW / MEDIUM / HIGH]
- Debt items introduced:
1. [Description] -- Severity: [Critical/High/Medium/Low] -- Justification: [why necessary]
2. [Description] -- Severity: [level] -- Justification: [reason]
#### Mitigation Plan
- [ ] Debt paydown plan required: [yes/no]
- [ ] Capacity allocated: [percentage] -- Aligns with cto-advisor 40/25/15 strategy: [yes/no]
### Technology Evaluation
#### New Dependencies
| Library/Service | Necessity | Alternatives Considered | Lock-in Risk | Cost Impact |
|----------------|-----------|------------------------|--------------|-------------|
| [name] | [justified] | [yes/no - list] | [low/med/high] | [amount/impact] |
#### Integration Assessment
- API design: [quality assessment]
- Error handling: [adequate/needs improvement]
- Retry logic: [present/missing]
- Cost monitoring: [planned/missing]
### Engineering Excellence
#### Testing Strategy: [STRONG / ADEQUATE / WEAK]
- Coverage targets: [percentage] -- Meets cto-advisor 80% threshold: [yes/no]
- TDD applicability: [high/medium/low] -- Justification: [reason]
- Test types planned: [unit/integration/e2e]
#### Performance Criteria: [DEFINED / VAGUE / MISSING]
- Load requirements: [specified/missing]
- Optimization strategy: [present/absent]
#### Security Review: [PASS / NEEDS ATTENTION]
- OWASP top 10 considered: [yes/no]
- Input validation: [planned/missing]
- Auth patterns: [appropriate/needs review]
#### Observability: [COMPREHENSIVE / BASIC / MISSING]
- Monitoring: [planned/missing]
- Logging: [planned/missing]
- Alerting: [planned/missing]
### Team & Process
#### Execution Feasibility: [HIGH / MEDIUM / LOW]
- Team capability match: [assessment]
- Knowledge distribution: [good/concerning]
- Onboarding impact: [low/medium/high]
#### Documentation Plan: [ADEQUATE / NEEDS EXPANSION]
- Technical docs needed: [list]
- ADR required: [yes/no]
- Onboarding docs: [needed/not needed]
### Red Flags
[List any critical concerns from cto-advisor red flags checklist]:
- Increasing technical debt without paydown plan
- Vendor lock-in without escape hatch
- Security vulnerabilities introduced
- Performance bottlenecks designed in
- Tight coupling reducing maintainability
### DORA Metrics Impact Assessment
| Metric | Current Target | Impact of Plan | Assessment |
|--------|---------------|----------------|------------|
| Deployment Frequency | >1/day | [positive/neutral/negative] | [explanation] |
| Lead Time | <1 day | [positive/neutral/negative] | [explanation] |
| MTTR | <1 hour | [positive/neutral/negative] | [explanation] |
| Change Failure Rate | <15% | [positive/neutral/negative] | [explanation] |
### Recommendations
#### Must Fix (Blocking Issues)
1. [Critical issue] -- [specific action required]
2. [Critical issue] -- [specific action required]
#### Should Consider (Improvements)
1. [Suggestion] -- [benefit]
2. [Suggestion] -- [benefit]
#### Nice to Have (Enhancements)
1. [Enhancement] -- [optional benefit]
### Verdict
**Technical Review**: [PASS / PASS WITH CONDITIONS / FAIL]
**PASS**: Technical approach is sound, no blocking issues
**PASS WITH CONDITIONS**: Approved, but recommendations must be addressed during execution
**FAIL**: Blocking issues must be resolved before execution begins
**Rationale**: [1-2 sentence summary of verdict reasoning]plan.md under "## Technical Review"This agent is automatically invoked by conductor-orchestrator during Step 2 (EVALUATE PLAN) when the track's spec.md or plan.md contains technical architecture keywords:
Trigger Keywords:
Invocation:
conductor-orchestrator -> detects technical track -> dispatches cto-plan-reviewer -> receives report -> includes in plan evaluation -> proceeds or blocksThis agent uses:
A successful technical review:
Manual invocation:
# User wants technical review of current plan
claude /cto-advisor
# Agent loads plan.md, applies cto-advisor frameworks, generates technical review reportAutomatic invocation:
# User runs conductor implement
/conductor implement
# Conductor detects Step 2 (Evaluate Plan) + technical track -> automatically calls cto-plan-reviewer
# Report generated -> included in plan evaluation -> execution proceeds or blocks© Ibrahim-3d, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/cto-plan-reviewer of Ibrahim-3d/orchestrator-supaconductor.
Open the folder on GitHubat commit 76c9b10
Cto Plan Reviewer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Cto Plan Reviewer this skillIbrahim-3d/orchestrator-supaconductor | 381 | — | ~2.9k | Automated safety check: Pass | AGPL-3.0 | |
| Vanity Engineering Reviewbencium/bencium-marketplace | 446 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Tech Debt Auditcode-yeongyu/oh-my-openagent | 70k | — | ~2.4k | Automated safety check: Notes | Custom licence | |
| Codebase Pathfinderthedotmack/claude-mem | 99k | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Architecture SurveyYeachan-Heo/oh-my-claudecode | 40k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Technology Radarmagnus919/hermes-profiles | 289 | — | ~1.3k | Automated safety check: Pass | MIT |
bencium/bencium-marketplace
Reviews codebases, architectures, PRs, and technical plans for vanity engineering — code and systems built for the developer's ego, resume, or intellectual pleasure rather than delivering user or…
code-yeongyu/oh-my-openagent
Audits a codebase for technical debt across nine dimensions and writes TECH_DEBT_AUDIT.md with file-cited findings, severity, effort estimates and priorities.
thedotmack/claude-mem
Maps a codebase into feature-grouped Mermaid flowcharts, finds duplicated concerns across features and proposes a unified architecture with handoff prompts for planning.
Yeachan-Heo/oh-my-claudecode
Periodic survey that walks a repo's module graph and reports ranked candidates for deepening, without changing any code itself.
magnus919/hermes-profiles
CTO methodology for technology evaluation, architecture governance, build-vs-buy decisions, engineering metrics, technical debt quantification, and innovation pipeline management.
tt-a1i/archify
Creates interactive architecture, workflow, sequence, data-flow and lifecycle diagrams as standalone HTML with inline SVG, themes and image or video export.
Ibrahim-3d/orchestrator-supaconductor
Technical leadership guidance for engineering teams, architecture decisions, and technology strategy.
Ibrahim-3d/orchestrator-supaconductor
A skill your agent uses when working with Conductor's context-driven development methodology, managing project context artifacts, or understanding the relationship between product.md, tech-stack.md…
Ibrahim-3d/orchestrator-supaconductor
Creates specialized worker agents dynamically from templates.
Ibrahim-3d/orchestrator-supaconductor
Simulate a 5-member expert board deliberation for major decisions.
Ibrahim-3d/orchestrator-supaconductor
A skill your agent uses when completing a track that changes pricing, AI models, product features, or asset pipelines — syncs business context documents across all tiers.
Ibrahim-3d/orchestrator-supaconductor
Load project context efficiently for Conductor workflows. An agent skill from Ibrahim-3d/orchestrator-supaconductor.
Categories
Technical architecture review agent for execution plans. An agent skill from Ibrahim-3d/orchestrator-supaconductor. Cto Plan Reviewer is an agent skill from Ibrahim-3d/orchestrator-supaconductor. Technical architecture review agent for execution plans.
Cto Plan Reviewer fits situations like: tasks that involve Software architecture; tasks that involve Technical debt.
Run `npx skills add Ibrahim-3d/orchestrator-supaconductor --skill cto-plan-reviewer -a claude-code`. Or copy the skill folder (skills/cto-plan-reviewer in Ibrahim-3d/orchestrator-supaconductor) into .claude/skills/cto-plan-reviewer in your project. Claude Code loads it when a task matches its description.
Run `npx skills add Ibrahim-3d/orchestrator-supaconductor --skill cto-plan-reviewer -a codex`. Or copy the skill folder (skills/cto-plan-reviewer in Ibrahim-3d/orchestrator-supaconductor) into .agents/skills/cto-plan-reviewer in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Ibrahim-3d/orchestrator-supaconductor --skill cto-plan-reviewer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cto-plan-reviewer, .gemini/skills/cto-plan-reviewer, .github/skills/cto-plan-reviewer and .opencode/skills/cto-plan-reviewer in your project.
Going by SKILL.md and its folder, Cto Plan Reviewer needs the command-line tools its instructions call (claude).
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Cto Plan Reviewer is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.9k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Cto Plan Reviewer: Vanity Engineering Review (bencium/bencium-marketplace, 446 stars), Tech Debt Audit (code-yeongyu/oh-my-openagent, 70k stars), Codebase Pathfinder (thedotmack/claude-mem, 99k stars) and Architecture Survey (Yeachan-Heo/oh-my-claudecode, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Ibrahim-3d (a GitHub user) maintains it in Ibrahim-3d/orchestrator-supaconductor, which has 381 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on September 27, 2026.
Source: Ibrahim-3d/orchestrator-supaconductor on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.
