Assess technical implications and engineering risks for proposed features.
npx skills add https://github.com/jikig-ai/soleur --skill cto-jikig-ai
Please help me install this Agent Skill. Skill: cto Source: https://github.com/jikig-ai/soleur/tree/main/.openhands/skills/cto Command: npx skills add https://github.com/jikig-ai/soleur --skill cto-jikig-ai
During brainstorming and planning sessions, technical implications and architecture risks are often overlooked or scattered across reviews, leading to unforeseen scope, security, or scalability issues. The cto skill consolidates cross-cutting technical assessment, identifies affected components, and surfaces architecture decisions so teams can make informed planning choices.
Ask the cto to assess the technical implications, list affected components, and recommend architecture approaches and trade-offs for the proposed feature.
High-intent search queries and answers about installing and using this skill.
Assess technical risks by evaluating architecture impacts, identifying affected components, and checking security and scalability concerns for feature proposals. This process surfaces cross-cutting technical implications and delivers risk ratings with recommended implementation approaches.
Architecture decision detection identifies when a change implies a new service, infrastructure change, or technology choice. You need it during planning sessions to consolidate technical assessments and recommend creating an architecture record with rationale before implementation begins.
Identify missing agents or skills through gap analysis during technical assessment. This flags missing prerequisites required to execute proposed work, provides approach options with trade-offs, and estimates complexity for informed planning choices.
Yes, you can evaluate GitHub issues by verifying issue state when referenced and applying cross-cutting technical assessment. This detects architecture decisions, checks repository conventions, and surfaces security and scalability concerns with risk ratings and recommended approaches.
Evaluate architecture trade-offs by assessing technical implications across the codebase, identifying impacted services and data models, and detecting potential breaking changes. This provides 2-3 approach options with complexity estimates and risk ratings for informed decision-making.
insentekCreates structured project proposals and submits them as GitHub Issues.
YuluoYAnalyze design proposals to quantify implementation complexity and produce prioritized task lists.
wyattjohVerify technical hypotheses and API constraints with parallel background research agents.
eventua11yIdentify accessibility risks in proposed features and designs against WCAG criteria.
