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 materials, confirm the delivery purpose, target size or duration, scope of modification, 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 gridcraft-editor skill. Standalone installation:npx skills add full-aigc-skills/gridcraft-skills --skill gridcraft-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
- Clarify the period, currency, and expense categories, and enter the budget baseline.
- Enter actual incurred amounts, and establish budget variance and completion rate formulas.
- Distinguish one-time expenses from recurring expenses, and mark missing data.
- Use conditional formatting to highlight deviations and check extreme values.
Handle missing values and numeric zero separately: when budget or actual is missing, display pending confirmation, and do not automatically treat it as zero for subtraction.
Tool Implementation
Use open_workbook/new_workbook to manage workbooks; read_range to check, set_cell to edit, execute_command to use complete commands; save_workbook to save.
First read the actual tool schema, then fill in the parameters; use the return values for object or document IDs. The 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, and do not pass off a similar name as the real thing.
Result Checking
- When the budget is zero, no division-by-zero error occurs.
- The total matches the sum of category amounts.
- The formula area is maintainable, and the original input is traceable.
Check the actual content against the user's goal, 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 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 modify it locally, preserving the content that has already been accepted.