/logic-review — Paragraph Logic Review
Purpose
Find paragraphs that may need a topic sentence, a clearer transition, merging,
re-ordering, or removal of duplicated argumentative work. The deterministic
script flags mechanical candidates; the agent separately reviews rhetorical
functions without redefining the manuscript spine.
Trigger Words
This skill activates on: logic review, flow check, paragraph logic, /logic-review.
Workflow
- Run:
python3 scripts/audit-logic.py --base-dir . --json
- Confirm that the research object, core question, intended use, primary
experiment, headline claim, and evidence boundary are stable under the
active
/thesis-control contract. If they are not, stop the language pass
and route the issue to drift control or revision escalation.
- Read the flagged paragraphs and nearby context.
- Label each relevant sentence or paragraph by its main function:
problem,
gap, method, evidence, interpretation, boundary, or transition.
- Flag duplicated functions and monotonous sequences, especially repeated
evidence -> disclaimer endings. Prefer deleting or consolidating repeated
argumentative work over generating synonymous wording.
- Check boundary placement. Scope must remain aligned across the paper, but
full limitation prose need not be repeated after every result. Preserve
essential local qualifiers and concentrate fuller study-boundary language
in the abstract ending, Methods boundary, Discussion/Limitations, and
conclusion when appropriate.
- Present a numbered review table with location, function, issue type, why it
matters, and a proposed edit.
- Wait for user approval before editing chapter files.
- Apply only approved edits, then re-run the audit.
Constraints
- Never auto-fix chapter logic without user approval.
- Preserve the author's argument and section structure.
- Keep edits local to the flagged paragraph unless the user approves a broader rewrite.
- Do not use a logic or style pass to repair an unstable research question,
evidence chain, application purpose, or contribution order.
- No emoji.
1---2name: logic-review3description: Review stable chapter or manuscript drafts for paragraph flow, transitions, argument continuity, and repeated rhetorical functions before editing. Use after the author-approved spine is stable; route structural drift back to thesis-control.4---56# /logic-review — Paragraph Logic Review78## Purpose910Find paragraphs that may need a topic sentence, a clearer transition, merging,11re-ordering, or removal of duplicated argumentative work. The deterministic12script flags mechanical candidates; the agent separately reviews rhetorical13functions without redefining the manuscript spine.1415## Trigger Words1617This skill activates on: `logic review`, `flow check`, `paragraph logic`, `/logic-review`.1819## Workflow20211. Run:22 `python3 scripts/audit-logic.py --base-dir . --json`232. Confirm that the research object, core question, intended use, primary24 experiment, headline claim, and evidence boundary are stable under the25 active `/thesis-control` contract. If they are not, stop the language pass26 and route the issue to drift control or revision escalation.273. Read the flagged paragraphs and nearby context.284. Label each relevant sentence or paragraph by its main function: `problem`,29 `gap`, `method`, `evidence`, `interpretation`, `boundary`, or `transition`.305. Flag duplicated functions and monotonous sequences, especially repeated31 `evidence -> disclaimer` endings. Prefer deleting or consolidating repeated32 argumentative work over generating synonymous wording.336. Check boundary placement. Scope must remain aligned across the paper, but34 full limitation prose need not be repeated after every result. Preserve35 essential local qualifiers and concentrate fuller study-boundary language36 in the abstract ending, Methods boundary, Discussion/Limitations, and37 conclusion when appropriate.387. Present a numbered review table with location, function, issue type, why it39 matters, and a proposed edit.408. Wait for user approval before editing chapter files.419. Apply only approved edits, then re-run the audit.4243## Constraints44451. Never auto-fix chapter logic without user approval.462. Preserve the author's argument and section structure.473. Keep edits local to the flagged paragraph unless the user approves a broader rewrite.484. Do not use a logic or style pass to repair an unstable research question,49 evidence chain, application purpose, or contribution order.505. No emoji.
yha9806