Solutions Agent

Technical Discovery

Run technical discovery that separates the real requirement from the RFP fiction and ends in a fit read. Use when user needs technical requirements gathering, environment/architecture understanding, or technical qualification before a demo or POC. Do not use when business discovery (pain, budget, decision process) is the need — use @file:discovery-prep; when assessing fit after discovery — use @file:technical-validation.

Demo Engineering

Build a demo environment with prospect-specific data and configuration that shows their future, not your feature list. Covers customization level, realistic data, integration simulation, and a no-crash run plan. Use when user needs a demo environment built, custom data configured, or a prospect-specific technical demo prepared. Do not use when the need is the demo narrative/script — use @file:demo-customization; when planning a hands-on POC — use @file:poc-planning.

POC Planning

Design a POC that proves ONE thing, has written success criteria, and ends in a decision — not an open-ended trial. Covers POC-vs-stall qualification, scope, criteria, and gate discipline. Use when user needs a POC designed, success criteria defined, or proof-of-concept scoping. Do not use when the goal is proving ROI/business value — use @file:proof-of-value; when estimating delivery effort — use @file:implementation-scoping.

Technical Validation

Make the honest go/no-go fit call on a deal — capability, integration, scale, security, timeline, and customer-readiness — with named gaps and conditions. Use when user needs a technical fit assessment, feasibility read, or a should-we-pursue recommendation. Do not use when designing the POC that proves a contested capability — use @file:poc-planning; when gathering the requirements first — use @file:technical-discovery.

RFP Response

Decide whether to bid, then answer the RFP precisely with evidence — winning the ones worth winning and declining the rest professionally. Use when user needs an RFP/RFI response, a bid/no-bid decision, or technical questionnaire answers. Do not use when the document is a security questionnaire — use @file:security-questionnaire; when it's a narrative sales proposal — use @file:proposal-writing.

Integration Assessment

Decide whether an integration is feasible — and at what real cost — before sales promises it. Covers API maturity, pattern selection, complexity scoring, and risk. Use when user needs integration feasibility, API evaluation, connectivity architecture, or a complexity/effort read on a connection. Do not use when broad technical discovery is the need — use @file:technical-discovery; when estimating total project effort — use @file:implementation-scoping.

Security Questionnaire

Complete vendor security questionnaires accurately and fast — reuse a library for the 80%, handle the 20% honestly, and stop security from killing a closed deal. Use when user needs SIG/CAIQ/VSAQ responses, compliance questionnaire completion, or vendor security review handling. Do not use when the document is a commercial RFP — use @file:rfp-response; when it's a broad fit assessment — use @file:technical-validation.

Architecture Review

Review a prospect's architecture across scalability, reliability, security, performance, and cost — to fit your solution into it and surface risk before implementation. Use when user needs architecture analysis, system-design review, or environment-readiness assessment for a deal. Do not use when assessing one integration's feasibility — use @file:integration-assessment; when estimating implementation effort — use @file:implementation-scoping.

Technical Objection

Handle a technical objection with evidence and an honest read on whether it's valid, a misunderstanding, FUD, or a cover for something else — then offer a validation path. Use when user faces a technical objection, needs to defend a capability, or must answer a competitor's technical claim. Do not use when the objection is business/pricing — use @file:objection-handling; when it's competitive positioning broadly — use @file:competitive-battlecard.

Proof Of Value

Design a proof-of-value engagement that proves measurable business impact with a real baseline and a CFO-ready number — not just that the product works. Use when user needs POV planning, ROI validation, value measurement, or CFO-ready value evidence. Do not use when the question is technical ("does it work?") — use @file:poc-planning; when scoping delivery effort — use @file:implementation-scoping.

Implementation Scoping

Scope an implementation accurately — estimate to succeed, not to win — so delivery teams inherit a number they can actually hit. Covers component breakdown, contingency, and risk. Use when user needs an implementation effort estimate, project scope for a deal, or a PS handoff scope. Do not use when designing a POC — use @file:poc-planning; when assessing one integration's feasibility — use @file:integration-assessment.

Technical Documentation

Write technical docs that close deals and de-risk implementations — briefs, solution architecture docs, and handoffs your champion can defend without you in the room. Use when user needs a technical brief, solution architecture document, proposal technical content, or an implementation handoff. Do not use when the audience is end users (product docs); when the content is an RFP answer — use @file:rfp-response.

Demo Scripting

Build the standard demo script — story arc, click path, talk track, persona/duration variations. Use when user needs the standard demo, a demo flow redesign, or scripted talking points sales can repeat. Do not use when deal-specific customization is the need (route to deal-specific demo prep) or the request is technical POC scoping (route to /solutions).