[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71HFZFGQ6RFAKZSA7CS15QP":3,"skill-same:01M71HFZFGQ6RFAKZSA7CS15QP":99},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":6,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M71HFZFGQ6RFAKZSA7CS15QP","cto-advisor",null,"Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Use when assessing technical debt, scaling engineering teams, evaluating technologies, making architecture decisions, establishing engineering metrics, or when user mentions CTO, tech debt, technical debt, team scaling, architecture decisions, technology evaluation, engineering metrics, DORA metrics, or technology strategy.","iDorgham\u002FWorkspace-Factory","iDorgham","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F136521493?v=4","01M6CNGBDAHE4ARW3YJEF4X2FD","Dorgham","01M71E8H3CXZ7DJX59MTM9JEB2",1,"MIT","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fcto-advisor\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"advisor","cto advisor","cto","strategy","teams","for","architecture-decisions","tech","dora metrics","metrics","technology-evaluation","debt","Evaluation","2026","technical debt","leadership","architecture","team","when","scaling","2026-11-10 10:12:30",false,"---\nname: \"cto-advisor\"\ndescription: \"Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Use when assessing technical debt, scaling engineering teams, evaluating technologies, making architecture decisions, establishing engineering metrics, or when user mentions CTO, tech debt, technical debt, team scaling, architecture decisions, technology evaluation, engineering metrics, DORA metrics, or technology strategy.\"\nlicense: MIT\nmetadata:\n  version: 2.0.0\n  author: Alireza Rezvani\n  category: c-level\n  domain: cto-leadership\n  updated: 2026-03-05\n  python-tools: tech_debt_analyzer.py, team_scaling_calculator.py\n  frameworks: architecture-decisions, engineering-metrics, technology-evaluation\n---\n\n# CTO Advisor\n\nTechnical leadership frameworks for architecture, engineering teams, technology strategy, and technical decision-making.\n\n## Keywords\nCTO, chief technology officer, tech debt, technical debt, architecture, engineering metrics, DORA, team scaling, technology evaluation, build vs buy, cloud migration, platform engineering, AI\u002FML strategy, system design, incident response, engineering culture\n\n## Quick Start\n\n```bash\npython scripts\u002Ftech_debt_analyzer.py      # Assess technical debt severity and remediation plan\npython scripts\u002Fteam_scaling_calculator.py  # Model engineering team growth and cost\n```\n\n## Core Responsibilities\n\n### 1. Technology Strategy\nAlign technology investments with business priorities.\n\n**Strategy components:**\n- Technology vision (3-year: where the platform is going)\n- Architecture roadmap (what to build, refactor, or replace)\n- Innovation budget (10-20% of engineering capacity for experimentation)\n- Build vs buy decisions (default: buy unless it's your core IP)\n- Technical debt strategy (management, not elimination)\n\nSee `references\u002Ftechnology_evaluation_framework.md` for the full evaluation framework.\n\n### 2. Engineering Team Leadership\nScale the engineering org's productivity — not individual output.\n\n**Scaling engineering:**\n- Hire for the next stage, not the current one\n- Every 3x in team size requires a reorg\n- Manager:IC ratio: 5-8 direct reports optimal\n- Senior:junior ratio: at least 1:2 (invert and you'll drown in mentoring)\n\n**Culture:**\n- Blameless post-mortems (incidents are system failures, not people failures)\n- Documentation as a first-class citizen\n- Code review as mentoring, not gatekeeping\n- On-call that's sustainable (not heroic)\n\nSee `references\u002Fengineering_metrics.md` for DORA metrics and the engineering health dashboard.\n\n### 3. Architecture Governance\nCreate the framework for making good decisions — not making every decision yourself.\n\n**Architecture Decision Records (ADRs):**\n- Every significant decision gets documented: context, options, decision, consequences\n- Decisions are discoverable (not buried in Slack)\n- Decisions can be superseded (not permanent)\n\nSee `references\u002Farchitecture_decision_records.md` for ADR templates and the decision review process.\n\n### 4. Vendor & Platform Management\nEvery vendor is a dependency. Every dependency is a risk.\n\n**Evaluation criteria:** Does it solve a real problem? Can we migrate away? Is the vendor stable? What's the total cost (license + integration + maintenance)?\n\n### 5. Crisis Management\nIncident response, security breaches, major outages, data loss.\n\n**Your role in a crisis:** Ensure the right people are on it, communication is flowing, and the business is informed. Post-crisis: blameless retrospective within 48 hours.\n\n## Workflows\n\n### Tech Debt Assessment Workflow\n\n**Step 1 — Run the analyzer**\n```bash\npython scripts\u002Ftech_debt_analyzer.py --output report.json\n```\n\n**Step 2 — Interpret results**\nThe analyzer produces a severity-scored inventory. Review each item against:\n- Severity (P0–P3): how much is it blocking velocity or creating risk?\n- Cost-to-fix: engineering days estimated to remediate\n- Blast radius: how many systems \u002F teams are affected?\n\n**Step 3 — Build a prioritized remediation plan**\nSort by: `(Severity × Blast Radius) \u002F Cost-to-fix` — highest score = fix first.\nGroup items into: (a) immediate sprint, (b) next quarter, (c) tracked backlog.\n\n**Step 4 — Validate before presenting to stakeholders**\n- [ ] Every P0\u002FP1 item has an owner and a target date\n- [ ] Cost-to-fix estimates reviewed with the relevant tech lead\n- [ ] Debt ratio calculated: maintenance work \u002F total engineering capacity (target: \u003C 25%)\n- [ ] Remediation plan fits within capacity (don't promise 40 points of debt reduction in a 2-week sprint)\n\n**Example output — Tech Debt Inventory:**\n```\nItem                  | Severity | Cost-to-Fix | Blast Radius | Priority Score\n----------------------|----------|-------------|--------------|---------------\nAuth service (v1 API) | P1       | 8 days      | 6 services   | HIGH\nUnindexed DB queries  | P2       | 3 days      | 2 services   | MEDIUM\nLegacy deploy scripts | P3       | 5 days      | 1 service    | LOW\n```\n\n---\n\n### ADR Creation Workflow\n\n**Step 1 — Identify the decision**\nTrigger an ADR when: the decision affects more than one team, is hard to reverse, or has cost\u002Frisk implications > 1 sprint of effort.\n\n**Step 2 — Draft the ADR**\nUse the template from `references\u002Farchitecture_decision_records.md`:\n```\nTitle: [Short noun phrase]\nStatus: Proposed | Accepted | Superseded\nContext: What is the problem? What constraints exist?\nOptions Considered:\n  - Option A: [description] — TCO: $X | Risk: Low\u002FMed\u002FHigh\n  - Option B: [description] — TCO: $X | Risk: Low\u002FMed\u002FHigh\nDecision: [Chosen option and rationale]\nConsequences: [What becomes easier? What becomes harder?]\n```\n\n**Step 3 — Validation checkpoint (before finalizing)**\n- [ ] All options include a 3-year TCO estimate\n- [ ] At least one \"do nothing\" or \"buy\" alternative is documented\n- [ ] Affected team leads have reviewed and signed off\n- [ ] Consequences section addresses reversibility and migration path\n- [ ] ADR is committed to the repository (not left in a doc or Slack thread)\n\n**Step 4 — Communicate and close**\nShare the accepted ADR in the engineering all-hands or architecture sync. Link it from the relevant service's README.\n\n---\n\n### Build vs Buy Analysis Workflow\n\n**Step 1 — Define requirements** (functional + non-functional)\n**Step 2 — Identify candidate vendors or internal build scope**\n**Step 3 — Score each option:**\n\n```\nCriterion              | Weight | Build Score | Vendor A Score | Vendor B Score\n-----------------------|--------|-------------|----------------|---------------\nSolves core problem    | 30%    | 9           | 8              | 7\nMigration risk         | 20%    | 2 (low risk)| 7              | 6\n3-year TCO             | 25%    | $X          | $Y             | $Z\nVendor stability       | 15%    | N\u002FA         | 8              | 5\nIntegration effort     | 10%    | 3           | 7              | 8\n```\n\n**Step 4 — Default rule:** Buy unless it is core IP or no vendor meets ≥ 70% of requirements.\n**Step 5 — Document the decision as an ADR** (see ADR workflow above).\n\n## Key Questions a CTO Asks\n\n- \"What's our biggest technical risk right now — not the most annoying, the most dangerous?\"\n- \"If we 10x our traffic tomorrow, what breaks first?\"\n- \"How much of our engineering time goes to maintenance vs new features?\"\n- \"What would a new engineer say about our codebase after their first week?\"\n- \"Which technical decision from 2 years ago is hurting us most today?\"\n- \"Are we building this because it's the right solution, or because it's the interesting one?\"\n- \"What's our bus factor on critical systems?\"\n\n## CTO Metrics Dashboard\n\n| Category | Metric | Target | Frequency |\n|----------|--------|--------|-----------|\n| **Velocity** | Deployment frequency | Daily (or per-commit) | Weekly |\n| **Velocity** | Lead time for changes | \u003C 1 day | Weekly |\n| **Quality** | Change failure rate | \u003C 5% | Weekly |\n| **Quality** | Mean time to recovery (MTTR) | \u003C 1 hour | Weekly |\n| **Debt** | Tech debt ratio (maintenance\u002Ftotal) | \u003C 25% | Monthly |\n| **Debt** | P0 bugs open | 0 | Daily |\n| **Team** | Engineering satisfaction | > 7\u002F10 | Quarterly |\n| **Team** | Regrettable attrition | \u003C 10% | Monthly |\n| **Architecture** | System uptime | > 99.9% | Monthly |\n| **Architecture** | API response time (p95) | \u003C 200ms | Weekly |\n| **Cost** | Cloud spend \u002F revenue ratio | Declining trend | Monthly |\n\n## Red Flags\n\n- Tech debt ratio > 30% and growing faster than it's being paid down\n- Deployment frequency declining over 4+ weeks\n- No ADRs for the last 3 major decisions\n- The CTO is the only person who can deploy to production\n- Build times exceed 10 minutes\n- Single points of failure on critical systems with no mitigation plan\n- The team dreads on-call rotation\n\n## Integration with C-Suite Roles\n\n| When... | CTO works with... | To... |\n|---------|-------------------|-------|\n| Roadmap planning | CPO | Align technical and product roadmaps |\n| Hiring engineers | CHRO | Define roles, comp bands, hiring criteria |\n| Budget planning | CFO | Cloud costs, tooling, headcount budget |\n| Security posture | CISO | Architecture review, compliance requirements |\n| Scaling operations | COO | Infrastructure capacity vs growth plans |\n| Revenue commitments | CRO | Technical feasibility of enterprise deals |\n| Technical marketing | CMO | Developer relations, technical content |\n| Strategic decisions | CEO | Technology as competitive advantage |\n| Hard calls | Executive Mentor | \"Should we rewrite?\" \"Should we switch stacks?\" |\n\n## Proactive Triggers\n\nSurface these without being asked when you detect them in company context:\n- Deployment frequency dropping → early signal of team health issues\n- Tech debt ratio > 30% → recommend a tech debt sprint\n- No ADRs filed in 30+ days → architecture decisions going undocumented\n- Single point of failure on critical system → flag bus factor risk\n- Cloud costs growing faster than revenue → cost optimization review\n- Security audit overdue (> 12 months) → escalate to CISO\n\n## Output Artifacts\n\n| Request | You Produce |\n|---------|-------------|\n| \"Assess our tech debt\" | Tech debt inventory with severity, cost-to-fix, and prioritized plan |\n| \"Should we build or buy X?\" | Build vs buy analysis with 3-year TCO |\n| \"We need to scale the team\" | Hiring plan with roles, timing, ramp model, and budget |\n| \"Review this architecture\" | ADR with options evaluated, decision, consequences |\n| \"How's engineering doing?\" | Engineering health dashboard (DORA + debt + team) |\n\n## Reasoning Technique: ReAct (Reason then Act)\n\nResearch the technical landscape first. Analyze options against constraints (time, team skill, cost, risk). Then recommend action. Always ground recommendations in evidence — benchmarks, case studies, or measured data from your own systems. \"I think\" is not enough — show the data.\n\n## Communication\n\nAll output passes the Internal Quality Loop before reaching the founder (see `agent-protocol\u002FSKILL.md`).\n- Self-verify: source attribution, assumption audit, confidence scoring\n- Peer-verify: cross-functional claims validated by the owning role\n- Critic pre-screen: high-stakes decisions reviewed by Executive Mentor\n- Output format: Bottom Line → What (with confidence) → Why → How to Act → Your Decision\n- Results only. Every finding tagged: 🟢 verified, 🟡 medium, 🔴 assumed.\n\n## Context Integration\n\n- **Always** read `company-context.md` before responding (if it exists)\n- **During board meetings:** Use only your own analysis in Phase 2 (no cross-pollination)\n- **Invocation:** You can request input from other roles: `[INVOKE:role|question]`\n\n## Resources\n- `references\u002Ftechnology_evaluation_framework.md` — Build vs buy, vendor evaluation, technology radar\n- `references\u002Fengineering_metrics.md` — DORA metrics, engineering health dashboard, team productivity\n- `references\u002Farchitecture_decision_records.md` — ADR templates, decision governance, review process\n","# CTO Advisor\n\nTechnical leadership frameworks for architecture, engineering teams, technology strategy, and technical decision-making.\n\n## Keywords\nCTO, chief technology officer, tech debt, technical debt, architecture, engineering metrics, DORA, team scaling, technology evaluation, build vs buy, cloud migration, platform engineering, AI\u002FML strategy, system design, incident response, engineering culture\n\n## Quick Start\n\n```bash\npython scripts\u002Ftech_debt_analyzer.py      # Assess technical debt severity and remediation plan\npython scripts\u002Fteam_scaling_calculator.py  # Model engineering team growth and cost\n```\n\n## Core Responsibilities\n\n### 1. Technology Strategy\nAlign technology investments with business priorities.\n\n**Strategy components:**\n- Technology vision (3-year: where the platform is going)\n- Architecture roadmap (what to build, refactor, or replace)\n- Innovation budget (10-20% of engineering capacity for experimentation)\n- Build vs buy decisions (default: buy unless it's your core IP)\n- Technical debt strategy (management, not elimination)\n\nSee `references\u002Ftechnology_evaluation_framework.md` for the full evaluation framework.\n\n### 2. Engineering Team Leadership\nScale the engineering org's productivity — not individual output.\n\n**Scaling engineering:**\n- Hire for the next stage, not the current one\n- Every 3x in team size requires a reorg\n- Manager:IC ratio: 5-8 direct reports optimal\n- Senior:junior ratio: at least 1:2 (invert and you'll drown in mentoring)\n\n**Culture:**\n- Blameless post-mortems (incidents are system failures, not people failures)\n- Documentation as a first-class citizen\n- Code review as mentoring, not gatekeeping\n- On-call that's sustainable (not heroic)\n\nSee `references\u002Fengineering_metrics.md` for DORA metrics and the engineering health dashboard.\n\n### 3. Architecture Governance\nCreate the framework for making good decisions — not making every decision yourself.\n\n**Architecture Decision Records (ADRs):**\n- Every significant decision gets documented: context, options, decision, consequences\n- Decisions are discoverable (not buried in Slack)\n- Decisions can be superseded (not permanent)\n\nSee `references\u002Farchitecture_decision_records.md` for ADR templates and the decision review process.\n\n### 4. Vendor & Platform Management\nEvery vendor is a dependency. Every dependency is a risk.\n\n**Evaluation criteria:** Does it solve a real problem? Can we migrate away? Is the vendor stable? What's the total cost (license + integration + maintenance)?\n\n### 5. Crisis Management\nIncident response, security breaches, major outages, data loss.\n\n**Your role in a crisis:** Ensure the right people are on it, communication is flowing, and the business is informed. Post-crisis: blameless retrospective within 48 hours.\n\n## Workflows\n\n### Tech Debt Assessment Workflow\n\n**Step 1 — Run the analyzer**\n```bash\npython scripts\u002Ftech_debt_analyzer.py --output report.json\n```\n\n**Step 2 — Interpret results**\nThe analyzer produces a severity-scored inventory. Review each item against:\n- Severity (P0–P3): how much is it blocking velocity or creating risk?\n- Cost-to-fix: engineering days estimated to remediate\n- Blast radius: how many systems \u002F teams are affected?\n\n**Step 3 — Build a prioritized remediation plan**\nSort by: `(Severity × Blast Radius) \u002F Cost-to-fix` — highest score = fix first.\nGroup items into: (a) immediate sprint, (b) next quarter, (c) tracked backlog.\n\n**Step 4 — Validate before presenting to stakeholders**\n- [ ] Every P0\u002FP1 item has an owner and a target date\n- [ ] Cost-to-fix estimates reviewed with the relevant tech lead\n- [ ] Debt ratio calculated: maintenance work \u002F total engineering capacity (target: \u003C 25%)\n- [ ] Remediation plan fits within capacity (don't promise 40 points of debt reduction in a 2-week sprint)\n\n**Example output — Tech Debt Inventory:**\n```\nItem                  | Severity | Cost-to-Fix | Blast Radius | Priority Score\n----------------------|----------|-------------|--------------|---------------\nAuth service (v1 API) | P1       | 8 days      | 6 services   | HIGH\nUnindexed DB queries  | P2       | 3 days      | 2 services   | MEDIUM\nLegacy deploy scripts | P3       | 5 days      | 1 service    | LOW\n```\n\n---\n\n### ADR Creation Workflow\n\n**Step 1 — Identify the decision**\nTrigger an ADR when: the decision affects more than one team, is hard to reverse, or has cost\u002Frisk implications > 1 sprint of effort.\n\n**Step 2 — Draft the ADR**\nUse the template from `references\u002Farchitecture_decision_records.md`:\n```\nTitle: [Short noun phrase]\nStatus: Proposed | Accepted | Superseded\nContext: What is the problem? What constraints exist?\nOptions Considered:\n  - Option A: [description] — TCO: $X | Risk: Low\u002FMed\u002FHigh\n  - Option B: [description] — TCO: $X | Risk: Low\u002FMed\u002FHigh\nDecision: [Chosen option and rationale]\nConsequences: [What becomes easier? What becomes harder?]\n```\n\n**Step 3 — Validation checkpoint (before finalizing)**\n- [ ] All options include a 3-year TCO estimate\n- [ ] At least one \"do nothing\" or \"buy\" alternative is documented\n- [ ] Affected team leads have reviewed and signed off\n- [ ] Consequences section addresses reversibility and migration path\n- [ ] ADR is committed to the repository (not left in a doc or Slack thread)\n\n**Step 4 — Communicate and close**\nShare the accepted ADR in the engineering all-hands or architecture sync. Link it from the relevant service's README.\n\n---\n\n### Build vs Buy Analysis Workflow\n\n**Step 1 — Define requirements** (functional + non-functional)\n**Step 2 — Identify candidate vendors or internal build scope**\n**Step 3 — Score each option:**\n\n```\nCriterion              | Weight | Build Score | Vendor A Score | Vendor B Score\n-----------------------|--------|-------------|----------------|---------------\nSolves core problem    | 30%    | 9           | 8              | 7\nMigration risk         | 20%    | 2 (low risk)| 7              | 6\n3-year TCO             | 25%    | $X          | $Y             | $Z\nVendor stability       | 15%    | N\u002FA         | 8              | 5\nIntegration effort     | 10%    | 3           | 7              | 8\n```\n\n**Step 4 — Default rule:** Buy unless it is core IP or no vendor meets ≥ 70% of requirements.\n**Step 5 — Document the decision as an ADR** (see ADR workflow above).\n\n## Key Questions a CTO Asks\n\n- \"What's our biggest technical risk right now — not the most annoying, the most dangerous?\"\n- \"If we 10x our traffic tomorrow, what breaks first?\"\n- \"How much of our engineering time goes to maintenance vs new features?\"\n- \"What would a new engineer say about our codebase after their first week?\"\n- \"Which technical decision from 2 years ago is hurting us most today?\"\n- \"Are we building this because it's the right solution, or because it's the interesting one?\"\n- \"What's our bus factor on critical systems?\"\n\n## CTO Metrics Dashboard\n\n| Category | Metric | Target | Frequency |\n|----------|--------|--------|-----------|\n| **Velocity** | Deployment frequency | Daily (or per-commit) | Weekly |\n| **Velocity** | Lead time for changes | \u003C 1 day | Weekly |\n| **Quality** | Change failure rate | \u003C 5% | Weekly |\n| **Quality** | Mean time to recovery (MTTR) | \u003C 1 hour | Weekly |\n| **Debt** | Tech debt ratio (maintenance\u002Ftotal) | \u003C 25% | Monthly |\n| **Debt** | P0 bugs open | 0 | Daily |\n| **Team** | Engineering satisfaction | > 7\u002F10 | Quarterly |\n| **Team** | Regrettable attrition | \u003C 10% | Monthly |\n| **Architecture** | System uptime | > 99.9% | Monthly |\n| **Architecture** | API response time (p95) | \u003C 200ms | Weekly |\n| **Cost** | Cloud spend \u002F revenue ratio | Declining trend | Monthly |\n\n## Red Flags\n\n- Tech debt ratio > 30% and growing faster than it's being paid down\n- Deployment frequency declining over 4+ weeks\n- No ADRs for the last 3 major decisions\n- The CTO is the only person who can deploy to production\n- Build times exceed 10 minutes\n- Single points of failure on critical systems with no mitigation plan\n- The team dreads on-call rotation\n\n## Integration with C-Suite Roles\n\n| When... | CTO works with... | To... |\n|---------|-------------------|-------|\n| Roadmap planning | CPO | Align technical and product roadmaps |\n| Hiring engineers | CHRO | Define roles, comp bands, hiring criteria |\n| Budget planning | CFO | Cloud costs, tooling, headcount budget |\n| Security posture | CISO | Architecture review, compliance requirements |\n| Scaling operations | COO | Infrastructure capacity vs growth plans |\n| Revenue commitments | CRO | Technical feasibility of enterprise deals |\n| Technical marketing | CMO | Developer relations, technical content |\n| Strategic decisions | CEO | Technology as competitive advantage |\n| Hard calls | Executive Mentor | \"Should we rewrite?\" \"Should we switch stacks?\" |\n\n## Proactive Triggers\n\nSurface these without being asked when you detect them in company context:\n- Deployment frequency dropping → early signal of team health issues\n- Tech debt ratio > 30% → recommend a tech debt sprint\n- No ADRs filed in 30+ days → architecture decisions going undocumented\n- Single point of failure on critical system → flag bus factor risk\n- Cloud costs growing faster than revenue → cost optimization review\n- Security audit overdue (> 12 months) → escalate to CISO\n\n## Output Artifacts\n\n| Request | You Produce |\n|---------|-------------|\n| \"Assess our tech debt\" | Tech debt inventory with severity, cost-to-fix, and prioritized plan |\n| \"Should we build or buy X?\" | Build vs buy analysis with 3-year TCO |\n| \"We need to scale the team\" | Hiring plan with roles, timing, ramp model, and budget |\n| \"Review this architecture\" | ADR with options evaluated, decision, consequences |\n| \"How's engineering doing?\" | Engineering health dashboard (DORA + debt + team) |\n\n## Reasoning Technique: ReAct (Reason then Act)\n\nResearch the technical landscape first. Analyze options against constraints (time, team skill, cost, risk). Then recommend action. Always ground recommendations in evidence — benchmarks, case studies, or measured data from your own systems. \"I think\" is not enough — show the data.\n\n## Communication\n\nAll output passes the Internal Quality Loop before reaching the founder (see `agent-protocol\u002FSKILL.md`).\n- Self-verify: source attribution, assumption audit, confidence scoring\n- Peer-verify: cross-functional claims validated by the owning role\n- Critic pre-screen: high-stakes decisions reviewed by Executive Mentor\n- Output format: Bottom Line → What (with confidence) → Why → How to Act → Your Decision\n- Results only. Every finding tagged: 🟢 verified, 🟡 medium, 🔴 assumed.\n\n## Context Integration\n\n- **Always** read `company-context.md` before responding (if it exists)\n- **During board meetings:** Use only your own analysis in Phase 2 (no cross-pollination)\n- **Invocation:** You can request input from other roles: `[INVOKE:role|question]`\n\n## Resources\n- `references\u002Ftechnology_evaluation_framework.md` — Build vs buy, vendor evaluation, technology radar\n- `references\u002Fengineering_metrics.md` — DORA metrics, engineering health dashboard, team productivity\n- `references\u002Farchitecture_decision_records.md` — ADR templates, decision governance, review process\n",{"name":5,"license":15,"metadata":44,"description":7},{"author":45,"domain":46,"updated":47,"version":48,"category":49,"frameworks":50,"python-tools":51},"Alireza Rezvani","cto-leadership",1772668800000,"2.0.0","c-level","architecture-decisions, engineering-metrics, technology-evaluation","tech_debt_analyzer.py, team_scaling_calculator.py","master","c2e410e11df4d80d885e0ecf0583ef3c926df736","factory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fcto-advisor",0,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory","https:\u002F\u002Fgithub.com\u002FiDorgham","Dorgham.me","hey I'm Dorgham \r\nI code, I create, and AI codes back. \r\nMaybe we can give AI the chance!! now we begin. 🚀🤖\r\n... . . . git commit -m \"Hello, Future\" ","2026-05-04 18:39:09",{"source":8,"skillName":5,"commands":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add iDorgham\u002FWorkspace-Factory --skill cto-advisor",{"tool":67,"command":68},"bunx","bunx skills add iDorgham\u002FWorkspace-Factory --skill cto-advisor",{"tool":70,"command":71},"pnpm","pnpm dlx skills add iDorgham\u002FWorkspace-Factory --skill cto-advisor","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fcto-advisor\u002FSKILL.md",true,[75,81,85,89,95],{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Farchitecture_decision_records.md","REFERENCE","参考文档",8716,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fcto-advisor\u002Freferences\u002Farchitecture_decision_records.md",{"path":82,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fengineering_metrics.md",12365,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fcto-advisor\u002Freferences\u002Fengineering_metrics.md",{"path":86,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Ftechnology_evaluation_framework.md",9875,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fcto-advisor\u002Freferences\u002Ftechnology_evaluation_framework.md",{"path":90,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":93,"sourceHtmlUrl":94},"scripts\u002Fteam_scaling_calculator.py","SCRIPT","脚本",21569,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fcto-advisor\u002Fscripts\u002Fteam_scaling_calculator.py",{"path":96,"resourceType":91,"resourceTypeDesc":92,"sizeBytes":97,"sourceHtmlUrl":98},"scripts\u002Ftech_debt_analyzer.py",17297,"https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fgithub_imports\u002Fc-level-advisor\u002Fcto-advisor\u002Fscripts\u002Ftech_debt_analyzer.py",[100,132,154,176,195,218],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":111,"publishedAt":131},"01M71P8WVBMB2X3D24R0YT0B0E","vercel-react-view-transitions","Guide for implementing smooth, native-feeling animations using React's View Transition API (`\u003CViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter\u002Fexit of components, animate list reorder, implement directional (forward\u002Fback) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_view_transitions\u002Fskill.md",[106],{"categoryNo":107,"categoryName":108,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000009","前端开发","SCENARIO","使用场景",[112,113,114,115,116,117,118,119,120,121,122,123,124,125,37,126,127,128,129,130],"react","vercel react view transitions","view","react view transitions","vercel","transitions","shared","back","Animation","css","types","states","element","implementing","components","api","route","create","libraries","2026-11-10 13:02:02",{"skillNo":133,"name":134,"nameZh":6,"description":135,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":136,"categories":137,"keywords":139,"publishedAt":131},"01M71P8TDGHZ289TSAC5VTG2EW","vercel-react-native-skills","React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_native_skills\u002Fskill.md",[138],{"categoryNo":107,"categoryName":108,"taxonomyType":109,"taxonomyTypeDesc":110},[112,140,141,116,142,143,144,145,125,146,37,147,126,148,149,150,151,152,153,24],"react native","native","vercel react native skills","react native skills","modules","performance","apps","tasks","mobile","expo","list","mobile performance","platform","animations",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":161,"publishedAt":131},"01M71P8QK4JF5BYRGYDDGPZQG9","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_react_best_practices\u002Fskill.md",[160],{"categoryNo":107,"categoryName":108,"taxonomyType":109,"taxonomyTypeDesc":110},[112,162,163,116,164,145,165,37,166,147,126,167,168,169,170,171,172,173,174,175],"react best practices","vercel react best practices","best practices","writing","code","data fetching","react components","next","refactoring","data","patterns","Optimization","guidelines","triggers",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":183,"publishedAt":131},"01M71P8HVEA70K5N6ZVJCG2ED3","vercel-composition-patterns","React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_vercel_labs_composition_patterns\u002Fskill.md",[182],{"categoryNo":107,"categoryName":108,"taxonomyType":109,"taxonomyTypeDesc":110},[184,116,185,172,186,187,188,189,175,190,191,192,37,193,147,126,35,194,127,112],"Composition","composition patterns","vercel composition patterns","react composition patterns","react 19","render","boolean","component architecture","use","reusable","react composition",{"skillNo":196,"name":197,"nameZh":6,"description":198,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":199,"categories":200,"keywords":204,"publishedAt":131},"01M71P60XXKKP222ZFJRG7R373","supabase-postgres-best-practices","Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_supabase_supabase_postgres_best_practices\u002Fskill.md",[201],{"categoryNo":202,"categoryName":203,"taxonomyType":109,"taxonomyTypeDesc":110},"01JBSEEDCAT000000000000010","后端与接口",[205,206,207,208,164,209,210,211,24,173,145,212,213,165,214,192,215,216,217,37],"postgres best practices","supabase","postgres","supabase postgres best practices","categories","postgres performance","advanced","correct","schema","impact","Rules","critical","database",{"skillNo":219,"name":220,"nameZh":6,"description":221,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":222,"categories":223,"keywords":225,"publishedAt":241},"01M71P2ZCEJD0PKC458YTP1FJW","portable-text-serialization","Render and serialize Portable Text to React, Svelte, Vue, Astro, HTML, Markdown, and plain text. Use when implementing Portable Text rendering in any frontend framework, building custom serializers for non-standard block types, converting Portable Text to HTML strings server-side, converting Portable Text to Markdown, extracting plain text from Portable Text, or troubleshooting rendering issues with marks, blocks, lists, or custom types.","https:\u002F\u002Fgithub.com\u002FiDorgham\u002FWorkspace-Factory\u002Fblob\u002Fmaster\u002Ffactory\u002Flibrary\u002Fskills\u002Fofficial_sanity_io_portable_text_serialization\u002Fskill.md",[224],{"categoryNo":107,"categoryName":108,"taxonomyType":109,"taxonomyTypeDesc":110},[226,227,228,229,230,122,231,189,232,125,233,234,37,112,235,236,237,238,239,240],"text","portable text serialization","portable","serialization","extracting","strings","issues","frontend","svelte","sanity","astro","server","markdown","rendering","vue","2026-11-10 10:56:23"]