Before executing the specific method, read Craft scenario commands and parameters, and execute according to the object selection, session, input replacement, and result checking within.
Task starting point
First read the source material, confirm the delivery purpose, target size or duration, modification scope, and required format. Directly adopt reasonable defaults for details that can be determined from the task and source material; 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
- First identify the existing hierarchy and direct formatting, and save a copy.
- Map the same semantics to unified styles, preserving emphasized content.
- Standardize numbering, indentation, spacing before and after paragraphs, and table styles.
- Check pagination after style replacement chapter by chapter.
Tool implementation
Use open_document/new_document to manage documents; verify with get_text, input with type_text, and perform other edits according to the live tool list; save with save_document, and check layout with render_page.
First read the actual tool schema, then fill in the parameters; use the returned values for object or document IDs. The 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, state the gap; do not pass off a similar name as a substitute.
Result checking
- Headings are not mistaken for body text, and list numbering is continuous.
- Cleaning up formatting does not delete content.
- Headers, footers, captions, and table text remain readable.
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 full 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 later requests revisions, read this source project and make local modifications, preserving the accepted content.