For new documents, prefer the document templates below; for modifying existing files, refer to Craft scenario commands and parameters, first locating the target area and the current session.
Task starting point
First read the materials and confirm the delivery purpose, target size or duration, modification scope, and required formats. Directly adopt reasonable defaults for details that can be determined from the task and materials; only ask about missing conditions that would change the result.
When a visible editor is needed, hand off 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 determine the audience and decision questions, and clearly list goals and constraints.
- Organize the body by background, solution, implementation, and delivery, using heading styles.
- Organize time, responsibilities, and costs into tables, with necessary assumptions attached.
- Check section logic, numbering, and attachment references.
Tool implementation
Use open_document/new_document to manage documents; use get_text to verify, type_text to input, and for other edits follow the live tool list; use save_document to save, and render_page to check layout.
First read the actual tool schema, then fill in parameters; use returned values for object or document IDs. Queried commands must be available on the current backend. Before saving, choose a new output path and preserve the input. When the required algorithm, format, or command does not exist, explain the gap; do not pass off a similar name as a substitute.
Result check
- Facts and assumptions are clearly distinguished.
- Tables do not overflow, and heading levels and page numbers are consistent.
- Deliver an editable document and a reading version.
Check the actual content against user goals, not just process exit codes. 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 repeating irreversible operations.
Delivery
Return the editable project, actual derived files, and a brief explanation: what modifications were made, which steps were not executed due to current capabilities, and what content requires user judgment. List only files that actually exist and have been checked. If the user later reworks it, read this session's source project and modify locally, preserving accepted content.
Fillable project proposal template
Readfilling guide, prepare the fields for this session, usethis type of templateto generate native headings, body text, and editable tables. Do not copy the examples verbatim; clearly mark missing facts as to be confirmed.