baram2584/PDFToMD
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

modify documents

Browse Source
This commit is contained in:
김경종
2026-05-08 17:03:40 +09:00
parent 73f955a8ce
commit a4dcfbdedc
23 changed files with 181 additions and 464 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.codex/commands/plan-mineru-integration.md
+6 -5
View File
@@ -15,11 +15,12 @@ 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.
2. Read `docs/WORKARCHIVE.md` when prior MinerU setup, verification, or sample conversion evidence is needed.
3. Verify any MinerU CLI facts that may have changed before changing docs.
4. Define the smallest adapter contract for command construction, working directories, outputs, stdout/stderr capture, exit handling, warnings, and provenance.
5. Ensure failure behavior is explicit: no silent fallback and no alternate engine route.
6. Identify mocked-output tests and optional MinerU-dependent checks.
7. Update `PLAN.md` only if implementation sequencing changes; update `PROGRESS.md` after the planning work.
## Guardrails
.codex/commands/plan-quality-evaluation.md
+6 -5
View File
@@ -15,11 +15,12 @@ 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.
2. Read `docs/WORKARCHIVE.md` for prior sample conversion evidence and historical fixture coverage.
3. Inspect `samples/` only as local fixture context; do not stage or commit sample files.
4. Define checks for page coverage, reading order, math renderability, delimiter normalization, table handling, asset links, metadata completeness, and warning counts.
5. Define `.json` metadata and `.report.md` expectations from the same source data.
6. Separate fast mocked checks from optional MinerU/model/GPU-dependent checks.
7. Update `PROGRESS.md` with the planned coverage and remaining sample gaps.
## Guardrails
.codex/commands/review-project-docs.md
+5 -4
View File
@@ -15,10 +15,11 @@ The user invoked this command with: $ARGUMENTS
## Workflow
1. Read `PLAN.md` and `PROGRESS.md`.
2. Read the requested document scope, defaulting to `AGENTS.md`, `PRD.md`, `ARCHITECTURE.md`, and `docs/KNOWLEDGEBASE.md`.
3. Check for contradictions against fixed decisions: MinerU 3.1.0 only, local-only, direct CLI execution, CLI-internal temporary local `mineru-api` allowed, no `--api-url` or remote API path, Python 3.12, uv, Obsidian Markdown, metadata JSON, and `.report.md`.
4. Report findings first with file and line references.
5. If edits are requested, make only surgical documentation changes and update `PROGRESS.md`.
2. Read `docs/WORKARCHIVE.md` when reviewing completed-work history, prior verification, or sample conversion evidence.
3. Read the requested document scope, defaulting to `AGENTS.md`, `PRD.md`, `ARCHITECTURE.md`, and `docs/KNOWLEDGEBASE.md`.
4. Check for contradictions against fixed decisions: MinerU 3.1.0 only, local-only, direct CLI execution, CLI-internal temporary local `mineru-api` allowed, no `--api-url` or remote API path, Python 3.12, uv, Obsidian Markdown, metadata JSON, and `.report.md`.
5. Report findings first with file and line references.
6. If edits are requested, make only surgical documentation changes and update `PROGRESS.md`.
## Guardrails
.codex/commands/run-mineru-research.md
+6 -5
View File
@@ -15,11 +15,12 @@ The user invoked this command with: $ARGUMENTS
## Workflow
1. Read `PLAN.md`, `PROGRESS.md`, `ARCHITECTURE.md`, and `docs/KNOWLEDGEBASE.md`.
2. Use official MinerU documentation, the MinerU GitHub repository, primary papers, and official dependency documentation.
3. Verify facts that can change: install commands, supported Python/CUDA versions, CLI flags, output formats, model download behavior, and licenses.
4. Record sources with URLs and access dates when updating docs.
5. Keep findings scoped to MinerU 3.1.0; do not add candidate-engine comparisons.
6. Update `PROGRESS.md` with what was verified and what remains uncertain.
2. Read `docs/WORKARCHIVE.md` when prior MinerU setup, verification, or sample conversion evidence is needed.
3. Use official MinerU documentation, the MinerU GitHub repository, primary papers, and official dependency documentation.
4. Verify facts that can change: install commands, supported Python/CUDA versions, CLI flags, output formats, model download behavior, and licenses.
5. Record sources with URLs and access dates when updating docs.
6. Keep findings scoped to MinerU 3.1.0; do not add candidate-engine comparisons.
7. Update `PROGRESS.md` with what was verified and what remains uncertain.
## Guardrails
.codex/commands/start-agent-work.md
+8 -6
View File
@@ -16,12 +16,14 @@ The user invoked this command with: $ARGUMENTS
1. Read `PLAN.md` and `PROGRESS.md`.
2. State the current goal, the next action, and any blocker that matters for the task.
3. Read only the additional source documents needed for the requested work.
4. If subagents are useful and the user explicitly asked for delegated agent work, choose the smallest set of `.codex/agents/*.toml` roles that covers the task.
5. For substantial implementation work, use the harness sequence: `harness-planner-agent` drafts the plan and contract, `feature-generator-agent` implements one agreed chunk, and `evaluation-agent` reviews the contract and completed work.
6. Do not implement converter code unless the user explicitly requests implementation.
7. After meaningful changes, update `PROGRESS.md`; update `PLAN.md` only when sequencing, decisions, ownership, or blockers change.
8. Run the smallest useful verification, check git status, and commit project changes while excluding `samples/`.
3. Read `docs/WORKARCHIVE.md` when historical completed-work context, previous verification, or sample conversion evidence is needed.
4. Read only the additional source documents needed for the requested work.
5. If subagents are useful and the user explicitly asked for delegated agent work, choose the smallest set of `.codex/agents/*.toml` roles that covers the task.
6. For substantial implementation work, use the harness sequence: `harness-planner-agent` drafts the plan and contract, `feature-generator-agent` implements one agreed chunk, and `evaluation-agent` reviews the contract and completed work.
7. Do not implement converter code unless the user explicitly requests implementation.
8. After meaningful changes, update `PROGRESS.md`; update `PLAN.md` only when sequencing, decisions, ownership, or blockers change.
9. Archive completed work in `docs/WORKARCHIVE.md` when it no longer needs to stay in `PROGRESS.md`.
10. Run the smallest useful verification, check git status, and commit project changes while excluding `samples/`.
## Guardrails