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
AGENTS.md
+3
View File
@@ -80,6 +80,7 @@ Strong success criteria let you loop independently. Weak criteria ("make it work
- `ARCHITECTURE.md`: system layers, MinerU adapter contract, intermediate representation, metadata schema, and local-only enforcement.
- `docs/KNOWLEDGEBASE.md`: research basis and implementation background.
- `docs/V1IMPLEMENTATIONPLAN.md`: v1 implementation sequence, sprint contracts, verification gates, and agent ownership.
- `docs/WORKARCHIVE.md`: archived completed work, historical sprint outcomes, setup results, verification history, and sample conversion evidence.
- `docs/Sprints/*.md`: active and historical sprint contracts.
- `.codex/agents/*.toml`: project-scoped custom subagent roles.
- `.codex/commands/*.md`: reusable project prompt commands.
@@ -92,6 +93,7 @@ At the start of every task:
- Read `PLAN.md` and `PROGRESS.md` before deciding what to do.
- Read only the other source documents needed for the task.
- Read `docs/WORKARCHIVE.md` when the task needs historical completed-work context, previous verification results, or sample conversion evidence.
- Use `.codex/agents`, `.codex/commands`, and `.codex/skills` when the user explicitly asks for agent delegation, reusable workflows, or specialized project guidance.
- State the relevant current goal, next action, and blocker if one exists.
- If `PLAN.md` and `PROGRESS.md` conflict, trust `PROGRESS.md` for what has happened and update `PLAN.md` when making the next change.
@@ -102,6 +104,7 @@ Use `PLAN.md` and `PROGRESS.md` to coordinate work across agents.
- Update `PLAN.md` when planned work, ownership, sequencing, open questions, or decisions change.
- Update `PROGRESS.md` after meaningful work, verification, blockers, or next actions change.
- Move completed work from `PROGRESS.md` to `docs/WORKARCHIVE.md` when it is no longer needed for current coordination.
- Keep entries short and factual.
- Do not use these files as scratchpads or long research notes.
- Do not mark work complete until it has been verified.