SuperAPI AI Directory

resume

General & other

View repository

Updated 10-15 21:04

About this skill

Resume a Devflow project

Devflow places project knowledge and active work state .devflow/ below. The sole purpose of Resume is to recover a trustworthy position in the current checkout and find one safe next route and action. It is a read-only orientation task, not an execution stage.

Before performing this skill, open references/communication.mdand apply it to natural language sent to the reader or saved to documents during the performance. This includes guidance sent when exiting at a gate.

Entry gate

Before any target-specific action, open references/project-gate.mdand apply the resume row. If the gate stops Resume, change nothing.

.devflow/exists but index.mdis absent or unreadable, without writing, inventory all currently existing .devflow/project/, .devflow/team/<current-member>/sketches/*/state.md, .devflow/adoption/state.md, .devflow/work/*/state.md paths. Before choosing a route based on foundation documents alone, check all scoped active state locations. Determine a writer route to recover the index from remaining project or artifact evidence. If that route cannot be determined, send to the user. Do not restart an unmanaged bootstrap on top of existing state.

Otherwise, .devflow/index.mdfirst and follow the scoped orientation and question route. The project's routing detail is owned by the index, so do not replace it with a generic lifecycle.

Recover the current position

  1. Enumerate only immediate active state with the index's bounded glob. Sketch follows only the current member's glob and does not find or read another member's Sketch. Do not recursively read all project or Domain documents.
  2. Compare the current checkout's Git revision and bytes with the intent, base, last safe point, and next action of each selected state. A dirty change without an active artifact is ownerless work, not evidence that nothing is in progress.
  3. If there are multiple active items, report all of them and send to the user to choose one. If there is one, open only the project documents that the corresponding spec.md or brief.md, Work의 team/*/<work-id>.md or Adoption's team/*/adoption.md, and Resume itself needs to interpret the current route. The spec or brief's read_firstis the routed actor's input. Do not follow it during orientation unless the selected state, sibling, and Git evidence conflict and that project document is needed to find the recovery owner.
  4. A foundation document is considered current only when its content is complete enough to satisfy the contract and readiness rule specified by the index. Do not consider a partial Product, Architecture, or Design current merely because the file exists.
  5. When there is no spec, state, verification, foundation, or Git evidence, or it is unreadable or they differ, do not guess. Report the inconsistency and send it to the exact writer or decision route that owns recovery. verification's failure_routeis the judgment owner and state's next_routeis the current stewardship, so they are not considered inconsistent merely because they differ, and the next route reports the state value.
  6. If there is no active item, do not report only “no work in progress”; derive the next foundation route. If there is no Product, bootstrap is possible, and if the Product is complete but there is no Architecture, architecture, if Architecture requires Design but there is no Design, send it to design.

Return one direction confirmation report

without progress or reconstructed conversation, use the following four fields.

  • 활성 항목: the item whose discovered scope is defined, or none
  • 불일치/차단: evidence that prevents trusting or continuing the state, or none
  • 다음 route와 행동: exactly one route and one action whose scope is defined. Do not execute.
  • 최소 읽기 범위: the project paths actually opened for judgment

Do not explain the entire Domain, choose a batching or implementation strategy, modify project files, repair state, execute the next route, aggregate other branches or worktrees, or claim verification. That responsibility lies with the routed skill, the user, Git, or an external orchestrator.

This target has no optional module. It is complete when the current disk and Git evidence support the report, there is a safe next route and one action, the actually read scope is listed, and no project write was made.