ck:ask

Answer technical and architectural questions through structured advisory roles.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/tonamson/please-done --skill ck-ask-tonamson
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ck:ask
Source: https://github.com/tonamson/please-done/tree/main/ck/.opencode/skills/ask
Command: npx skills add https://github.com/tonamson/please-done --skill ck-ask-tonamson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides concise, expert consultation to answer technical and architectural questions, helping teams make informed design decisions.

Core Features & Use Cases

  • Structured advisory sessions across architecture, technology strategy, scalability, and risk assessment.
  • Roles coordination: Systems Designer, Technology Strategist, Scalability Consultant, Risk Analyst.
  • Use Cases: architecture reviews, high-level design guidance, decision trade-offs, and risk mitigation planning.

Quick Start

Pose a technical question about your system to receive strategic architectural guidance.

Frequently Asked Questions about ck:ask

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get architectural guidance for systems design decisions?

To get architectural guidance, the Skill orchestrates four advisory roles to deliver structured consultation covering high-level design, technology strategy, scalability input, and risk assessment for your specific project context.

What is the best way to evaluate risk and scalability for a new system architecture?

Evaluating risk and scalability is handled by coordinating dedicated advisory roles that assess architecture problems and deliver structured guidance, ensuring documented trade-offs and mitigation planning for your system.

Can I use this for technology strategy consultation and decision trade-offs?

Yes, you can use this for technology strategy consultation. It orchestrates a Technology Strategist role to provide high-level design guidance and analyze decision trade-offs based on your project context.

How do I structure an architecture review with advisory roles?

Structuring an architecture review involves coordinating four distinct roles: Systems Designer, Technology Strategist, Scalability Consultant, and Risk Analyst, to answer technical questions with documented process and expert consultation.

Does this consultation tool require any specific dependencies or project documentation?

No dependencies are required. The consultation uses your provided project documentation to satisfy requirements for structured guidance and clear roles, analyzing project context to deliver architectural advice.