project-pivotlisted

# Skill: project-pivot **Purpose**: Drive a 4-question interview to produce a runtime-derived, tailored project configuration. No static template matches every setup; this skill derives the right defaults from four orthogonal axes: domain, compliance, data handling, and project nature. **Constraint (hard, non-negotiable)**: Never output country-specific law names (e.g., Law NNNN, L[e]y NNNN, CCPA, PIPEDA, LGPD, PDPA, DPA 2018, APPI, POPIA, NDPR). If the operator's answers imply a jurisdiction, output: > "Consult the `regulatory-research-<jurisdiction>` skill family and insert the > applicable statute name here as a placeholder." This constraint exists because country-specific law names require expert interpretation, update over time, and are handled better by dedicated regulatory-research skills than by a generic pivot skill. --- ## Interview Protocol Conduct the questions in strict order. Do not proceed to the next question until the operator has provided a valid answer to the current one. For each question, show the available options and accept a free-text override when noted. --- ### Question 1: Domain / Industry **Ask**: "What is the primary domain or industry of this project?" **Options** (single-select; free-text override allowed): | Key | Domain | |---|---| | `procurement` | Public/private procurement, RFP/tender management | | `healthcare` | Clinical software, patient data, medical devices | | `fintech` | Payments, lending, trading, digital banking | | `dev