---
name: xiaoma-validate-prd
description: 'DEPRECATED — consolidated into `xiaoma-prd` (validate intent); will be removed in v7. Use when a legacy invocation or override targets `xiaoma-validate-prd` by name; it forwards to `xiaoma-prd`.'
---

# DEPRECATED — forwards to xiaoma-prd (validate intent)

This skill was consolidated into `xiaoma-prd`. The full XiaoMa PRD quality standard it used to enforce — measurability, traceability, SMART (FR/NFR), implementation-leakage, information-density, domain-compliance, project-type fit, dual-audience readiness, and the rest of the 13-dimension rubric — now lives inside `xiaoma-prd`'s validate intent (see `xiaoma-prd/assets/prd-validation-checklist.md`). This stub is retained as a thin compatibility shim so existing invocations by name and `_xiaoma/custom/xiaoma-validate-prd.toml` override files keep working. New work should invoke `xiaoma-prd` directly — it detects create / update / validate intent from the conversation.

## On Activation

1. Resolve customization: `node {project-root}/_xiaoma/scripts/resolve_customization.js --skill {skill-root} --key workflow`. This picks up any `{project-root}/_xiaoma/custom/xiaoma-validate-prd.toml` and `xiaoma-validate-prd.user.toml` overrides for the legacy fields (`activation_steps_prepend`, `activation_steps_append`, `persistent_facts`, `on_complete`). On failure, read `{skill-root}/customize.toml` directly and use defaults.

2. Load `{project-root}/_xiaoma/xmc/config.yaml` (and `config.user.yaml` if present) to resolve `{user_name}` and `{communication_language}`.

3. Emit a deprecation notice to the user in `{communication_language}`:

   > Notice: `xiaoma-validate-prd` is deprecated and will be removed in a future release. It now forwards to `xiaoma-prd` with validate intent. To silence this notice and access the full new customization surface (`prd_template`, `validation_checklist_template`, `validation_report_template`, `doc_standards`, `finalize_reviewers`, `external_sources`, `external_handoffs`), migrate `_xiaoma/custom/xiaoma-validate-prd.toml` to `_xiaoma/custom/xiaoma-prd.toml` and invoke `xiaoma-prd` directly next time.

4. Invoke `xiaoma-prd` with the following context. Pass these as the activating context so `xiaoma-prd` honors them instead of resolving its own customization from scratch:

   - **Intent:** `validate` — skip `xiaoma-prd`'s usual intent detection step; critique the existing PRD without changing it.
   - **Pre-resolved legacy customization** — use these in place of resolving from `xiaoma-prd`'s own `customize.toml` for the four legacy fields. For everything else (`prd_template`, `validation_checklist_template`, `validation_report_template`, `doc_standards`, `finalize_reviewers`, `external_sources`, `external_handoffs`), use `xiaoma-prd`'s own defaults and overrides as normal:
     - `activation_steps_prepend` = the resolved value from step 1
     - `activation_steps_append` = the resolved value from step 1
     - `persistent_facts` = the resolved value from step 1
     - `on_complete` = the resolved value from step 1
   - **Original user input:** forward whatever the user said when invoking this skill verbatim.

   `xiaoma-prd` takes the workflow from here. Do not execute any further steps in this shim.