cto-plan-reviewer
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.
Ibrahim-3d · 已有静态检查记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add Ibrahim-3d/orchestrator-supaconductor --skill cto-plan-reviewer技能说明
name: cto-plan-reviewer description: "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."
CTO Plan Reviewer -- Technical Architecture Review
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.
When to Use
Automatically invoked during Step 2: EVALUATE PLAN when the track involves:
- Architecture decisions or changes
- Technology selection or integration
- Infrastructure setup or changes
- Database schema or migrations
- API design or contracts
- Scalability or performance concerns
- Security-critical implementations
Also manually invocable via:
claude /cto-advisor
Inputs Required
- Track's
plan.md-- execution plan to review - Track's
spec.md-- requirements and context conductor/tech-stack.md-- current technology decisionsconductor/product.md-- product requirements and constraints- Codebase state -- existing architecture patterns
Review Framework
The agent leverages the cto-advisor skill to perform deep technical analysis across multiple dimensions:
1. Architecture Review
| 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:
- Architecture Decision Records (ADRs)
- System Design Review checklist
- Technology Standards evaluation
2. Tech Debt Assessment
| 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:
- Tech Debt Analyzer framework
- Tech Debt Strategy (40/25/15 allocation)
- Red flags checklist
3. Technology Evaluation
| 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:
- Technology Evaluation Framework (4-week process)
- Vendor Management checklist
- Cost optimization principles
4. Engineering Excellence
| 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:
- DORA Metrics targets (deployment frequency, lead time, MTTR, CFR)
- Quality Metrics (test coverage >80%, code review 100%, tech debt <10%)
- Success Indicators checklist
5. Team & Process
| 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:
- Team Topologies
- Engineering metrics (sprint velocity, unplanned work <20%)
- Communication templates
Review Process
Step 1: Load Context
Use context-loader skill to efficiently load:
- Track's
plan.mdandspec.md conductor/tech-stack.md-- current stack decisionsconductor/product.md-- product constraints- Recent architectural decision files or ADRs
- Existing component/module patterns in codebase
Step 2: Invoke CTO Advisor Frameworks
For 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
Step 3: Generate Technical Review Report
## 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
阅读完整来源 ↗