---
name: requirements_discovery
phase: discover
description: Guidance for discovering, analyzing, and documenting GCP solution requirements.
---

# Phase 0: Requirements Discovery Skill

When performing requirements discovery for a Google Cloud Solution Architecture:

1. **Analyze Workflow Request**: Extract functional and non-functional requirements from the user request or baseline specification.
2. **Defer Product Selection**: During discovery, product selection must explicitly be marked as `deferred: true`. Do not commit to specific GCP products (e.g. Cloud Run vs GKE) until the design phase.
3. **Capture Core Requirements**:
   - Authenticated HTTPS ingress, stateless processing, asynchronous domain events.
   - High availability within a selected GCP region.
   - At-least-once delivery with idempotent processing.
   - Least-privilege IAM service accounts and private networking where practical.
4. **Document Assumptions and Open Questions**: Highlight unknowns regarding scale, traffic spikes, compliance, and specific region requirements.
5. **Output Standard**: Produce a valid `docs/requirements.md` file matching the phase spec.