add pdftomd
This commit is contained in:
@@ -0,0 +1,28 @@
|
||||
---
|
||||
description: Plan the direct local MinerU CLI adapter and failure/reporting behavior
|
||||
argument-hint: [integration-scope]
|
||||
allowed-tools: [Read, Glob, Grep, Bash, WebFetch, Edit]
|
||||
---
|
||||
|
||||
# /plan-mineru-integration
|
||||
|
||||
Plan the future implementation shape for the MinerU adapter without writing converter code.
|
||||
|
||||
## Arguments
|
||||
|
||||
The user invoked this command with: $ARGUMENTS
|
||||
|
||||
## Workflow
|
||||
|
||||
1. Read `PLAN.md`, `PROGRESS.md`, `PRD.md`, and `ARCHITECTURE.md`.
|
||||
2. Verify any MinerU CLI facts that may have changed before changing docs.
|
||||
3. Define the smallest adapter contract for command construction, working directories, outputs, stdout/stderr capture, exit handling, warnings, and provenance.
|
||||
4. Ensure failure behavior is explicit: no silent fallback and no alternate engine route.
|
||||
5. Identify mocked-output tests and optional MinerU-dependent checks.
|
||||
6. Update `PLAN.md` only if implementation sequencing changes; update `PROGRESS.md` after the planning work.
|
||||
|
||||
## Guardrails
|
||||
|
||||
- Do not implement program code during planning.
|
||||
- Do not introduce runtime engine selection or cloud-compatible endpoints.
|
||||
- Keep GPU limitations and CPU messaging explicit for GTX 1070 Ti 8GB.
|
||||
Reference in New Issue
Block a user