SuperAPI AI Directory

soia-dev-task-execute

Coding & development

View repository

Updated 10-16 08:24

About this skill

soia-dev-task-execute

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 independent paths 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" simultaneously satisfies: the requested observable result has been achieved; the relevant verification has actually run; key conclusions have independent evidence; the working tree contains only the changes for this task. When 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, first stop at the preview or diagnostic stage.

Dependencies and installation

This skill requires no installer 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

The process reports only the stages, scope changes, verification results, and blocking reasons that affect judgment. 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 individually falsified, and specify evidence for each, such as test names, command output, generated artifacts, or manual reproduction steps.

Distinguish "diagnosis" from "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 the 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 scope minimal during implementation: every line of change 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. Verify results

Choose checks based on risk, not just the most convenient command to run:

Risk surface At least one kind of evidence
Logic or data boundaries Unit tests, fixtures, or boundary inputs
Flows 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 operating steps, screenshots, or automated UI checks

When fixing a problem, first reproduce it or establish the narrowest failing check; after the fix, run the relevant regression. If tests fail, cannot be run, or only cover the happy path, state this truthfully, and do not substitute "looks correct" for evidence.

4. Independent review

Do not only verify your own implementation intent. Review 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 generated results.

Then search for the same pattern: whether the same kind of defect appears in adjacent modules or the same calling convention. Write the search scope and the reasons for inclusion or exclusion into the receipt. If unrelated problems are found, only report them; do not expand the changes along the way.

5. Delivery receipt

Before finishing, check the staging area and working tree to confirm that 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 what is unknown.

完成:<可观察结果>。

边界:<目标、非目标和关键假设>
文件变化:<每项变化如何对应目标>
验证:<实际运行的命令、结果和独立复核>
残余风险:<未覆盖情况;无则写“无”>

Anti-Fake-Fix Gate

Before calling it complete, confirm item by item:

  • The diff of the changes exists, and each item can be mapped to the request;
  • Verification commensurate with the risk was actually run;
  • No TODO, comment, swallowed error, or empty commit was used to disguise a behavioral fix;
  • The same pattern has been searched for and the handling conclusion recorded;
  • Unrelated uncommitted files were not included in the delivery.

Security 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. Only report checks and results that were actually performed.