add pdftomd
This commit is contained in:
@@ -0,0 +1,27 @@
|
||||
---
|
||||
description: Plan fixture-based quality checks and conversion report requirements
|
||||
argument-hint: [sample-or-quality-scope]
|
||||
allowed-tools: [Read, Glob, Grep, Bash, Edit]
|
||||
---
|
||||
|
||||
# /plan-quality-evaluation
|
||||
|
||||
Plan local fixture evaluation and report requirements for math-heavy PDF conversion.
|
||||
|
||||
## Arguments
|
||||
|
||||
The user invoked this command with: $ARGUMENTS
|
||||
|
||||
## Workflow
|
||||
|
||||
1. Read `PLAN.md`, `PROGRESS.md`, `PRD.md`, and `ARCHITECTURE.md`.
|
||||
2. Inspect `samples/` only as local fixture context; do not stage or commit sample files.
|
||||
3. Define checks for page coverage, reading order, math renderability, delimiter normalization, table handling, asset links, metadata completeness, and warning counts.
|
||||
4. Define `.json` metadata and `.report.md` expectations from the same source data.
|
||||
5. Separate fast mocked checks from optional MinerU/model/GPU-dependent checks.
|
||||
6. Update `PROGRESS.md` with the planned coverage and remaining sample gaps.
|
||||
|
||||
## Guardrails
|
||||
|
||||
- Do not copy sample PDFs into tracked files.
|
||||
- Do not require GPU or large model downloads for the default fast verification loop.
|
||||
Reference in New Issue
Block a user