plan-tune

# plan-tune ## Usage **Invoke**: `/plan-tune [prd-path] [--product | --eng]` - Slash command: `/plan-tune` - Natural language: "tune the PRD", "certify the PRD", "run the contract certifier", "check the PRD before plan-em" - Context: a path to an existing PRD `.md` file, or invocation immediately after `plan-pm` or `plan-em` saved one **Flags:** | Flag | Tune type | Checks run (from `refs/certification.md`) | |------|-----------|-------------------------------------------| | `--product` | Product tune | Checks 1 (criteria testability), 2 (breaking/DB labeled), 3 (intent fidelity), 6 (frontmatter graph) | | `--eng` | Eng tune | Checks 2, 4 (exec-table/eng integrity), 5 (ticket graph validity), 6, 7 (cross-agent contract coherence) | | _(none)_ | Auto-selected | Decided from PRD content — **not** asked (see Step 1) | **Path rules:** - If a file path is provided and valid, use it directly. - If a directory path is provided (e.g. `features/prd-1-user-auth/`), derive the file as `<dir>/prd-[n]-[slug].md` (the `.md` inside it sharing the directory's basename). - If no path is provided, ask the user (see Step 1). - Path must match `features/prd-*/prd-*.md` after resolution. If it does not, ask again — do not refuse silently. **Hard refusals:** - PRD path resolves to a file that does not exist after two ask attempts: refuse. State the expected location and offer to run `/plan-pm` to create one. ## Tune types | Type | Flag | Auto-select trigger (when no flag) | Checks | |----...