Establish a traceable execution closed loop for any engineering task. The input is a clear objective and an accessible workspace; the output is the minimal change, reproducible verification evidence, and an honest completion receipt.
Scope of application
Applies to verifiable tasks such as code, configuration, documentation, migration preparation, and repository maintenance. It does not replace the local rules of the target repository; after entering the repository, first read the applicable contribution instructions and testing conventions.
If a task requires a specific organization's process state, dedicated directories, or approval records, first load that organization's binding-layer skill; this skill only provides a portable execution method.
Customer-readable description
What this skill can do
| The customer wants | Execution closed loop | The customer can see |
|---|---|---|
| Implement or modify an engineering work item | Define boundaries, then make the minimal reliable change | Change mapping and verification results |
| Complete a risky maintenance task | Identify high-risk surfaces and review them via an independent path | Verified facts, unverified items, and risks |
| Hand off a completed task | Summarize inputs, artifacts, checks, and residual risks | A reproducible completion receipt |
Definition of done
"Done" is satisfied simultaneously when: the requested observable result has been achieved; the relevant verification has actually been run; key conclusions have independent evidence; and the working tree contains only the changes for this task. If any of these cannot be satisfied, clearly report the blocker or uncovered scope, and do not write intent as completion.
How the customer uses it
Provide the objective, the target workspace, the expected observable result, and any known tests or reproduction methods. When deletion, overwriting, sending, publishing, remote writes, or irreversible data changes are involved, state the scope of authorization; if this information is missing, stop at the preview or diagnostic stage first.
Dependencies and installation
Installation:
npx skills add soia-team/soia-open-dev-coding-skills -g -a '*' -s soia-dev-task-execute -y
This skill does not require other installers or private configuration. Its hard dependencies are an accessible target workspace and at least one reproducible verification method; if the repository already has contribution instructions, test entry points, or local rules, read them first and take them as authoritative.
Logs and completion receipt
During the process, report only the stages that affect judgment, scope changes, verification results, and reasons for blockers. The final receipt must list the actual changes, the commands actually run, the independent review, and residual risks, and must not print credentials or local private information.
Execution flow
1. Define the task boundaries
Before starting, write down four things: objective, non-objectives, acceptance criteria, and verification plan. Break the input into work items that can be falsified individually, and specify evidence for each, such as test names, command output, generated artifacts, or manual reproduction steps.
Distinguish between "diagnosis" and "change": when the user only asks for localization, deliver the diagnosis first, unless the user also authorizes a fix. When deletion, overwriting, sending, publishing, or remote state changes are involved, reconfirm the objective and scope of authorization.
2. Inspect the site and implement
First inspect the working tree, baseline, and relevant conventions; existing unrelated changes must not be staged or mixed into this task. Keep the implementation scope minimal: every line changed should map to the objective, necessary verification, or obsolete old behavior.
For uncertain specifications, prefer narrow, reversible interpretations and record assumptions; ambiguities that affect safety, data integrity, public interfaces, or irreversible actions must be asked about first.
3. Verification results
Choose checks by risk, not just by running the most convenient command:
| Risk area | At least one type of evidence |
|---|---|
| Logic or data boundaries | Unit tests, fixtures, or boundary inputs |
| Flow and error paths | Integration tests or end-to-end reproduction |
| Interfaces, configuration, or build | Type checking, lint, build, or consumer paths |
| User-visible interface | Real operation steps, screenshots, or automated UI checks |
When fixing a problem, first reproduce it or establish the narrowest failing check; after fixing, run the relevant regression. If tests fail, cannot be run, or cover only the happy path, state this truthfully and do not substitute "looks correct" for evidence.
4. Independent review
Do not verify only your own implementation intent. Recheck the most fragile assumptions through at least one other path: for example, inspect the diff outside the tests, reproduce with different inputs, check downstream call sites, or manually verify the generated results.
Then search for the same pattern: whether the same defect appears in adjacent modules or the same calling convention. Record the search scope, inclusion or exclusion reasons in the receipt. Report unrelated issues only; do not expand the changes along the way.
5. Delivery receipt
Before finishing, check the staging area and working tree to confirm no unrelated files enter the delivery. Write the receipt according to the strength of the facts: give sources for what was observed; give grounds for inferences; explain the verification path for unknowns.
完成:<可观察结果>。
边界:<目标、非目标和关键假设>
文件变化:<每项变化如何对应目标>
验证:<实际运行的命令、结果和独立复核>
残余风险:<未覆盖情况;无则写“无”>
Anti-Fake-Fix Gate
Before calling it complete, confirm item by item:
- The change diff exists, and each item corresponds to the request;
- Verification commensurate with the risk was actually run;
- No TODO, comment, swallowed error, or empty commit was used to disguise a behavior fix;
- The same pattern was searched for and the handling conclusion recorded;
- Unrelated uncommitted files were not included in the delivery.
Safety boundaries
Do not hardcode local paths, accounts, credentials, internal project details, or private context. Keep explicit confirmation boundaries for remote writes, deletions, overwrites, sends, and releases. Report only checks and results that were actually executed.