article-action-plan

# Article Action Plan ## Workflow 1. Identify the article directory and read applicable `AGENTS.md` files. 2. Read the local review notes, action plan or issue index, `main.tex`, affected section files, and bibliography as needed. 3. If the article uses GitHub Issues as its backlog, inspect the open issues before using Markdown progress markers. 4. If the user does not specify an action, follow the order recorded in the issue backlog or local plan, unless the next action depends on an unresolved editorial target or user decision. 5. Before starting an action, record progress in the issue or mark it `[~]` if the plan uses progress markers. 6. Implement the smallest coherent unit of work. 7. Verify changes with compilation, citation checks, or textual review as appropriate. 8. Close the issue or mark the action `[x]` only after the change, evidence, or decision is actually recorded. 9. Add a short progress note with files changed, verification, limitations, and next steps. ## Progress Marker Rules - Prefer GitHub Issues for operational backlog when the article has migrated to issues. - `[ ]` means pending. - `[~]` means in progress. - `[x]` means completed. - Do not mark an action complete merely because it was discussed. - If the work reveals a dependency or blocker, record that explicitly under the action. ## Prioritization - Prefer actions that unlock later work, define the editorial target, strengthen contribution claims, or improve evidence quality. - For article-to-journal work, establish the target journal before making large structural changes. - Avoid reopening already settled delivery versions unless the user asks for a new publication-oriented revision. - Separate quick editorial wins from actions that require new experiments, new data collection, human annotation, or external publication-policy checks. - If a task requires current journal policies, editorial status, rankings, or publication venues, verify against current official sources before acting. ## Action Completion Standard - A completed action must leave an auditable trace: manuscript edit, bibliography update, table/figure, computed evidence, recorded decision, or explicit rationale for deferral. - The progress note should identify changed files, verification method, unresolved limitations, and the next sensible action. - If the action changes the paper's scope, claims, method, evidence, or submission strategy, update the relevant issue and review notes when local conventions require it. ## Reporting - Summarize what changed and where. - Mention what was verified. - Name unresolved decisions or risks. - Keep issues, local plan/index, and review notes consistent with the manuscript state.