technical-discovery

name	technical-discovery
description	Run technical customer discovery that surfaces current architecture, workflows, constraints, success criteria, security/compliance needs, and decision risks without prematurely designing a solution.

Technical Discovery

Use when this procedure is the primary professional method needed for the assignment.

Procedure

1. Confirm the decision or outcome this work must support, its scope, owner, constraints, and definition of success.
2. Establish the evidence baseline using customer architecture, workflows, data/security requirements, timelines, stakeholders, and desired outcomes. Do not fill material gaps with assumptions when they can change the result.
3. Map actors and systems, ask for concrete current-state evidence, identify mandatory/non-negotiable constraints, expose unknowns, and agree on proof criteria.
4. Exercise realistic edge, failure, transition, or exception cases that could invalidate the result; record unresolved uncertainty explicitly.
5. Validate the output against the original outcome and any neighboring professional contracts so this skill does not silently absorb another specialist's authority.
6. Record the resulting artifact, measurements, decisions, provenance, and handoff information needed for another owner to reproduce or continue the work.

Quality gate

Discovery produces a bounded problem statement and testable success criteria, not a disguised sales pitch.