Question
Back to skills
Consultation

Question

/hapo:question

Evidence-backed Q&A for project behavior, source code, specs, docs, configuration, dependencies, and external technical topics.

Use When

  • You need to understand how something works in the current system.
  • You need a source-backed answer before planning or changing code.
  • The repo may not have enough information and current external docs may be needed.

Flow

01 / Classify

Identify whether the question is about code behavior, config, specs, dependencies, workflow, or external knowledge.

02 / Scout

Read README, docs, specs, code, config, tests, and package metadata before making claims.

03 / Research

Use external/current sources only when repo evidence is missing or version-sensitive.

04 / Answer

Separate confirmed source facts from inferences and cite evidence.

05 / Ask back

Ask one focused question only when the answer would otherwise be misleading.

Output

A direct answer with evidence, confidence, gaps, and a next step when useful.

Avoid

Do not implement, scaffold, edit product code, generate specs, or treat unanswered facts as confirmed.

Next Handoff

/hapo:brainstorm, /hapo:specs, /hapo:docs, or /hapo:debug depending on the answer