菜单
Professional CTO consultation workflow for feature strategy, architecture direction, infrastructure choices, market positioning, and enterprise self-hosting tradeoffs.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Run the canonical build plus all nine per-project test commands from docs/TESTING.md. Never uses solution-level dotnet test.
Create or re-baseline lean, repository-grounded implementation plans and persistent dev docs when users ask for an implementation plan, technical plan, feature plan, refactor plan, or dev-docs workstream.
Senior CTO review workflow for repository-grounded implementation-plan workstreams used before coding.
Apply project EF Core conventions for repositories, DbContext setup, query filters, migrations, and seeded lookup data.
Create a self-contained HTML artifact focused on a high-quality SVG architecture or system diagram with minimal supporting prose.
Create a pragmatic self-contained HTML plan that organizes the user's plan content visually without expanding the scope unnecessarily.
| name | cto-consultation |
| description | Professional CTO consultation workflow for feature strategy, architecture direction, infrastructure choices, market positioning, and enterprise self-hosting tradeoffs. |
| type | workflow |
| enforcement | suggest |
| priority | high |
Use this skill when the user wants strategic or architectural consultation rather than immediate implementation. It turns open-ended product, infrastructure, UX, market, compliance, or enterprise-readiness questions into a grounded recommendation with options, tradeoffs, risks, and a decision path.
Consultation output shape:
1. Decision needed
2. Current repo facts
3. Options
4. Recommendation
5. Enterprise/self-hosting impact
6. Implementation path
7. Verification and documentation impact
Example stance:
TickerQ should remain a default internal scheduler for Basic Dispatch Mode, while its dashboard stays optional, instance-admin-only, and never the source of truth for email delivery state.
dotnet test --project Event.Architecture.Tests/Event.Architecture.Tests.csproj --configuration Release --verbosity quiet --filter FullyQualifiedName~Event.Architecture.Tests.AgentContextSchemaTestsdotnet test --project Event.Architecture.Tests/Event.Architecture.Tests.csproj --configuration Release --verbosity quiet --filter FullyQualifiedName~Event.Architecture.Tests.AgentContextLinkTestsdotnet build --configuration Release --verbosity quiet