43 lines
5.8 KiB
Markdown
43 lines
5.8 KiB
Markdown
# Execution choices and review
|
|
|
|
Use the user's confirmed arrangement for the current report. This reference coordinates production with a content workflow; it does not introduce a compiler schema, scheduler or extra approval round. A local revision or single-page task only uses the relevant parts of the existing arrangement.
|
|
|
|
## Confirm once and reuse
|
|
|
|
Receive the existing execution table or equivalent readable choices with the content handoff. For a new or substantially restructured report, combine the review scope, assignments, budget and production choices into one request before dependent work. Offer a default arrangement and editable choices together; accepting the listed default once covers subsequent authorized pages, blocks and necessary revisions within that scope. Do not ask again for settled choices.
|
|
|
|
The arrangement identifies the following as relevant to the task:
|
|
|
|
| Choice | Record |
|
|
|---|---|
|
|
| Content transitions and page purpose | Main Agent, fresh-context serial reviewer, authorized block-parallel reviewers, or skipped specialist review; scope and budget |
|
|
| Language, terminology and prior knowledge | Assignment, covered content and how results are reported |
|
|
| Mathematics and other professional reasoning | Assignment, audience knowledge, scope and budget |
|
|
| Review after revision | Default independent reviewer who did not edit that portion; any explicit main-Agent self-check or skip choice, and affected scope |
|
|
| Production | Page-by-page or authorized block-parallel work, permitted pages and review granularity |
|
|
| ImageGen layout drafts | Enabled scope/budget, skipped image drafts, or a user-selected main-Agent text composition/template preview alternative |
|
|
|
|
These are human-readable decisions in existing project notes or the page plan, not mandatory JSON fields or a new file format. A choice can remain pending until first needed. Resolve consequential pending choices together before using the relevant tool or assignment; progress on independent authorized work can continue.
|
|
|
|
Declining parallel Agents does not authorize serial sub-Agents. Declining all sub-Agents does not select main-Agent work for every step. Declining ImageGen does not decide whether to skip image drafts or use a text composition/template preview. Ask the user to settle the affected steps together, then reuse the answer. Do not silently choose a replacement, claim a different arrangement or remove all checks. Required production fidelity and current-page checks remain distinct from optional specialist reviews.
|
|
|
|
A user's later change affects the stated scope; revise the same arrangement and apply it to affected work. Reviewing a new page layout is content feedback, not a new request for the same tool permission. A page-by-page choice never grants permission for unreviewed later pages; block production only covers the authorized block.
|
|
|
|
## Review after revision
|
|
|
|
The mandatory project build, approved-sample fidelity and full-page hierarchy checks apply regardless of whether specialist review is selected. Every page must be retained in its buildable project, reconstructed without unauthorized element loss and checked as a whole for sizes, families, weights, spacing and visual grouping. These are production requirements, not an additional review assignment or approval round; follow [mockup fidelity and page checks](visual-design.md#approved-mockup-fidelity).
|
|
|
|
By default, the agreed post-revision review uses a fresh-context Agent who did not participate in editing that portion. Reuse the once-confirmed assignment and budget. If the user explicitly selected main-Agent checking or skipped this review, follow and label that choice; do not describe it as independent review.
|
|
|
|
Provide current deliverable source and preview as relevant, confirmed report/section/page goals, audience knowledge, criteria, original evidence and sufficient prior content to verify dependencies. Include precise premises, symbol meanings, conditions and source locations needed for the current use. Do not make the reviewer assume a preceding block has already explained them. A missing item in the review input is not proof that the whole report lacks it; allow source lookup, and distinguish missing evidence from an input gap.
|
|
|
|
Before the reviewer forms a judgment, omit author self-assessments, expected pass/fail verdicts, defenses of the edits, leading summaries and earlier approval or resolution conclusions. Keep any old issue list separate. The reviewer first checks the current material and records locations and reasons; only afterwards compare specific old findings when needed. Preserve useful evidence rather than shortening away context to make the packet look neutral.
|
|
|
|
The reviewer reports the actual version/scope, concrete issues, unresolved evidence and passed checks, with no finding quota or expectation of agreement/disagreement. The author resolves findings against sources. After a substantive further revision, independently recheck the affected portion and dependencies under the same agreed arrangement; old approval does not cover new text. Reuse unaffected valid checks.
|
|
|
|
## What production checks
|
|
|
|
Every title, paragraph, formula, label, figure and meaningful decorative group has an expression role serving the page, its section and the report goal. Keep the demonstrated contribution/judgment and supporting evidence. Do not add a limitations list, self-doubt or preventive defense merely because review began. Explain premises and facts that actually change the judgment with the relevant content.
|
|
|
|
Review current reading order, visible evidence associations, required visual relationships, capacity and template fidelity. Keep content-plan review, image-draft feedback, native structure, actual rendering, editing and projection evidence separate. General review input principles do not require this Skill to repeat the structure Skill's full content analysis.
|