SuperAPI AI Directory

work

Coding & development

View repository

Updated 10-15 21:03

About this skill

Implement one change

Work turns an already bounded outcome into actual code, tests, and Git history. Within the agreed boundary, Work chooses the local implementation method, but does not turn implementation convenience into a new goal, acceptance rule, or product boundary.

Before performing this skill, references/communication.mdand apply it to natural language sent to readers or stored in documents during execution. This includes guidance sent when exiting at a gate.

Enter a valid gate

Before performing the target-specific action, references/project-gate.mdand apply the work row. If the gate routes elsewhere, change nothing.

If an index is available, read it before selecting or executing an input.

Work receives exactly one of the following two inputs.

  • A readable state.md의 next_route가 workwith no blockers and a self-contained spec.mdtracked artifact with
  • An ephemeral goal, write boundary, and proportionate checks agreed in the current session

If it is a tracked input, open references/work-state.mdbefore reading or writing Work state. After selecting an artifact, if there is a scoped note corresponding to that ID, or it has a local delta, environment-specific context, or provisional context that must be preserved after handoff, open references/team-context.md. Otherwise skip it. Read the selected spec and state, the spec's read_first document, the details the spec map points to for the current action, the context that module allows, and the current Git revision, status, and relevant diff. Do not expand into unrelated project knowledge. Before touching files, base_revisionand verify that the inherited dirty paths listed in the contract still match.

If required contract documents are missing, unreadable, or contradictory before ownership is clear, do not implement or repair. Report the exact discrepancy and route to resume. If the state is readable and ownership has already been granted to Work, record the discrepancy as a decision question and disclose next_route: direct.

Personal settings are inputs that preserve the shared contract while adjusting how each team member executes. After confirming a valid input and ownership, before the first implementation or closure action, if .devflow/team/exists, check exactly one references/project-gate.mdwith the current team identity of .devflow/team/<current-member>/preferences/work.md . Reuse an identity already confirmed. If the file exists, open references/member-preferences.mdfirst and apply the personal file; if not, proceed with the default method without creating one.

Execute within the contract

Implement the smallest current result or shaping slice that satisfies the spec. Work owns local factoring, naming, algorithms, and test techniques within the write boundary. It does not stage or rewrite unrelated dirty bytes.

Run checks that can reveal whether this implementation and the guardrail are maintained. If the slice is safe, when the repository allows a commit, create a focused commit containing only the owned changes and record that commit as last_safe_point. A dirty tree is not a safe point.

If during implementation a wrong assumption, a required change outside the boundary, or a contract conflict defined by work-stateis revealed, stop at the last safe point. Disclose next_route: direct, including the wrong assumption, the smallest proposed change, the boundary impact, and one decision question. If the affected boundary is not Adoption-ready, state the necessary Adoption decision in next_action. Do not modify the spec.

If it is a shaping contract, complete and observe only the current slice. Send it to directwith the observed signal and the next decision question. A successful intermediate review is not a Verify failure. If the spec specified an intermediate risk criterion for this slice or the stop condition says it is ready to acceptance-judge the closure result, send it to verify.

Keep the handoff recoverable

Before another actor or session takes over stewardship, replace the state with the actual safe point and one scoped next action. If there is a scoped follow-up action under the same contract, use next_route: work; if an amendment or the next shaping decision, a higher-level judgment, an exploration to preserve, or a user answer is needed, use direct; if it is ready for an independent acceptance judgment, use verify. Use useronly for the safe stop required by the common state contract. verification.mdor a verdict is never written.

Persistent facts discovered during implementation are recorded only in knowledge_candidatesof the common state contract. Reproducible tests and code may be handed to Verify, but do not create new evidence files or put verification evidence into state. The shaping handoff's next_actionconveys only the scoped observation signal and decision question needed by Direct. If the spec requires preserving non-reproducible evidence until a later Verify session, do not pretend it was preserved; treat it as a contract conflict and send it to direct. Recording a candidate does not imply adoption or canonical write authority.

Close only verified tracked Work

When the published verification returns stewardship to Work, read the criterion evidence without duplicating the verdict into state. Failed or unproven criteria follow the failure route recorded in verification. Do not close based merely on the existence of a verification file or the provenof some criteria.

If valid tracked Work reaches its closure condition and all required criteria are proven, adopt or reject the candidate, newly reflect or resume pending landing, or before closing the Work artifact references/work-closure.mdopens. Termination without a candidate follows the same contract. Existing pending landings do not substitute for current verification and termination eligibility.

In general implementation, candidate recording, repairing failed verification, shaping/risk review before closure, and ephemeral work, do not perform exploration to open this detail. To integrate confirmed facts into an existing canonical home, if a new meaning/direction, Domain or child structure, decision identity judgment is needed, or there is no landing home, create a new document without closing it, clarify the necessary decision route and questions, and directsend to.

handle work that ends in the current conversation

For ephemeral input, work-state do not open the module and do not create a Work artifact. Read the relevant canon, implement within the agreed boundaries, run the agreed checks, and finish in the current session. If interruption recovery, persistent knowledge decisions, independent verification, or unresolved risk becomes necessary, stop before proceeding further and promote the current dirty delta to base_revision: HEADso that directsend to.

When reflecting persistent facts confirmed in the current conversation directly, within the agreed scope, into .devflow/index.md or .devflow/project/ the canonical document, only immediately before writing, open references/project-knowledge.mdand the contract of the corresponding document type. Do not open it for ephemeral implementation that does not modify the canonical document.

report handoff

return the following.

  • Safe point: commit or none, and the remaining owned dirty paths
  • Route와 행동: one following route and one scoped action, or closed
  • 이탈: a false premise, a spec clause outside the owner's scope, a blocker, a candidate, an unproven observation, or none
  • 읽은 범위: the canonical, Work, and personal configuration files actually opened

Do not direct a new goal, change acceptance, perform an independent Verify judgment, restructure project status, coordinate branches, or absorb a retained brownfield source.