Files
awesome-copilot/skills/audit-integrity/references/clarification-protocol.md
T
Burak Kaygusuz c5a2d812f9 fix: adopt progressive disclosure for sast-sca-security-analyzer and modularize audit-integrity 🤖🤖🤖 (#3047)
* feat(skills): modularize audit-integrity references for progressive disclosure

* refactor(agents): adopt progressive disclosure in sast-sca-security-analyzer

* style(skills): format table alignment in security-report-template

* refactor(skills): restore domain-agnostic audit-integrity references

* refactor(agents): make sast-sca-security-analyzer self-contained
2026-09-29 10:12:15 +10:00

807 B

Clarification Protocol

Before you start the analysis, pause and ask the user a maximum of 2 targeted questions when:

  • The system scope, asset boundary, or target module is ambiguous and you cannot infer it from the context
  • A critical trust boundary or privilege tier is undefined
  • The business context for impact prioritization or compliance framework selection is absent
  • The programming language or framework cannot be detected from the workspace

Rules:

  1. State your working assumptions explicitly and proceed.
  2. Do not wait for confirmation unless the ambiguity alters the attack surface definition or trust boundary map.
  3. Ask a maximum of 2 questions. If more ambiguity exists, document your assumptions and proceed.
  4. If no ambiguity exists, proceed directly without questions.