ck:ask

Architecture consultation for an existing codebase provides structured, high-level design direction and risk analysis without initiating direct implementation. It synthesizes systems design and technology strategy to produce actionable recommendations and next actions based on your project's established constraints.

Evaluating technology selection and scalability trade-offs requires applying a structured decision framework to your systems design. This approach identifies potential risks early and yields high-level architectural guidance grounded in your repository's established workflows and documentation.

Yes, you can resolve technical challenges by using your repository's primary workflow and development rules as an authoritative decision framework. This context-aware reasoning ensures architecture recommendations align strictly with your project's orchestration protocol and documentation practices.

No, architecture consultation explicitly focuses on strategy, patterns, and phased decision-making rather than providing direct implementation steps. It controls the scope to deliver high-level design direction, ensuring you receive actionable recommendations without automatically generating code.

Identifying scalability risks before iterative planning involves analyzing your system design against your project's technology strategy. This process highlights structural trade-offs and potential bottlenecks, delivering a structured analysis with recommended next actions to mitigate issues early.

You should use a decision framework for technical consulting when you need clear design direction and risk identification before coding. It is essential for resolving complex architecture challenges during early and iterative planning phases to avoid costly structural mistakes.