product-intentlisted

# Product Intent This skill turns product/strategy/PM knowledge into Yalla's development workflow. It does not create a generic PRD. It creates a concise Product Intent section that `/yalla`, `/yalla-plan`, `/yalla-review`, and the PR body can all use. ## Read First - `${CLAUDE_PLUGIN_ROOT}/knowledge/product/PRODUCT-INTENT-FRAMEWORK.md` - `${CLAUDE_PLUGIN_ROOT}/knowledge/product/ASSUMPTION-TESTING.md` - `${CLAUDE_PLUGIN_ROOT}/knowledge/product/INTENDED-VS-IMPLEMENTED.md` - `${CLAUDE_PLUGIN_ROOT}/knowledge/product/METRICS-FRAMEWORK.md` - `${CLAUDE_PLUGIN_ROOT}/knowledge/product/GTM-DISCOVERY.md` when the change is GTM-facing - `${CLAUDE_PLUGIN_ROOT}/knowledge/product/SHIPPING-ARTIFACTS.md` before deciding where durable docs belong ## Trigger Decision Start by deciding whether Product Intent applies. Return `N/A` only with a specific reason, for example: - `tiny-hotfix preserving existing behavior` - `test-only coverage for unchanged behavior` - `mechanical dependency/config update` - `copy edit that does not change positioning, promise, or flow` If the work changes money, access, data boundaries, delivery, onboarding, public product pages, GTM, pricing, or the Yalla workflow itself, Product Intent applies. ## Output Produce this block for the caller to paste into the plan: ```markdown ## Product Intent - Applies: true|false - Trigger: [why it applies, or N/A reason] - Target actor: - Desired outcome: - Metric moved: - Opportunity/problem: - Current evidence: - MVP s