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/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