Before executing the specific method, read Craft scenario commands and parameters, and execute according to the object selection, session, input replacement, and result checking therein.
Task Starting Point
First read the materials, confirm the delivery purpose, target size or duration, revision scope, and required format. Details that can be determined from the task and materials should directly adopt reasonable defaults; only ask about missing conditions that would change the result.
When a visible editor is needed, hand it over to the wordcraft-editor skill. Standalone installation:npx skills add full-aigc-skills/wordcraft-skills --skill wordcraft-editor. The currently added skill is a local candidate; before release, use the local companion plugin, and do not treat this installation command as proof of release.
Execution Steps
- Keep both versions of the input, and establish correspondence by chapter and paragraph.
- List additions, deletions, and rewrites, and separately check numbers, dates, and proper nouns.
- Separate pure formatting changes from content changes.
- Output a change list and items requiring confirmation.
Tool Implementation
Use open_document/new_document to manage documents; get_text to verify, type_text to input, other edits according to the real-time tool list; save_document to save, render_page to check layout.
First read the actual tool schema, then fill in the parameters; use the return values for object or document IDs. Queried commands must be available on the current backend. Before saving, choose a new output path and keep the input. When the required algorithm, format, or command does not exist, explain the gap, and do not pass off a similar name as the real thing.
Result Checking
- Paragraph moves are not falsely reported as content loss.
- Changes to key numbers and conclusions are listed separately.
- When revision mode is unavailable, use a comparison table, and do not claim that native revision records were generated.
Check the actual content against the user's goals, not just the process exit code. For local edits, inspect local details; for layout tasks, inspect the entire page; for time-based media, inspect the start, end, and key segments. For abnormal results, first check the current project to avoid repeatedly performing irreversible operations.
Delivery
Return the editable project, the actual derived files, and a brief explanation: what modifications were made, which steps were not executed due to current capabilities, and what content requires the user's judgment. List only files that actually exist and have been checked. If the user subsequently reworks it, read this source project and make local modifications, preserving the content that has already been accepted.