customer

To simulate client responses during a discovery phase interview, use this skill to role-play the client using an active briefing and context template. It automatically tags outputs as [BRIEFING], [RAG], or [INFERENCE] to ensure traceability of answers.

Maintaining briefing consistency when gathering project requirements requires using the briefing as the primary source of truth. This skill simulates client answers and explicitly tags each response by its origin, preventing scope drift during discovery.

Yes, you need an active briefing to use this customer simulation skill. It acts as a temporary client proxy and relies entirely on the briefing document to generate traceable answers for solution architects and product owners.

Yes, you can use a context-template to align vocabulary during discovery interviews. The skill is compatible with context-templates to match specific terminology and concerns while generating client-style responses from the briefing.

Traceability when generating inferred client answers works by tagging every output with [BRIEFING], [RAG], or [INFERENCE]. This ensures specialists know exactly whether a response is extracted directly from the briefing or logically inferred.

A limitation of briefing-based client simulation is that it cannot answer questions outside the briefing's scope without relying on inference. If the briefing lacks detail, outputs shift from factual [BRIEFING] tags to speculative [INFERENCE] tags, requiring specialist validation.