W00 Workflow Checkpoint (Save + Resume Only)

This is a basic capability layer independent of

w01~w05

, responsible for only two things: save (checkpoint) and resume.

⚠️ Core Mandatory Requirements

Strict Responsibility Boundaries

• w00-workflow-checkpoint

  is only responsible for:
  • Save: Write/update checkpoint
  • Resume: Read and restore the latest checkpoint context

• w00-workflow-checkpoint

  is NOT responsible for:
  • Initializing issues (triggered by main workflow stages like

    w01/w02

    )
  • Closing tasks (triggered by

    w05-task-closure

    )

Terminology Conventions (Avoid Ambiguity)

• Save: By default, refers to checkpoint update (not task closure)
• Resume: By default, refers to restoring checkpoint context
• Archiving/Closing: Handled by

  w05-task-closure

  , not part of this skill

Trigger Methods (Automatic + Manual)

• Automatic Trigger: Main workflow stages automatically call this skill to perform "save/resume" at key nodes.
• High-Frequency Manual Trigger: Triggered when the user says

  save

  or

  resume

  .
• Additional Condition (Save Fallback): When performing "save", if there is no updatable issue in the context (no

  #issue

  provided, no bound

  Issue #

  , 0 candidates allowed), directly create an issue and write the first checkpoint (create and save).

Managed Objects

• Repository: No fixed default value, parsed by context (user explicit specification > current Git repository remote > user selection)
• Example Repository:

  qiao-925/qiao-skills

  (example only, not used as default)
• Task Title:

  [<repo>] <target short sentence>

  (Example:

  [qiao-skills] Optimize W00 automatic save trigger

  )
• Repository Name Format: Follow the original repository definition, no additional case conversion
• Labels:

  status:*

  +

  type:*

  +

  repo:*

  +

  wf:*

  (optional:

  term:*

  )

• wf:*

  Specification: Use full stage name (Example:

  wf:w02-task-planning

  )
• Minimum Fields:

  Goal / Next

AI Agent Behavior Requirements

Two Standard Actions

1. Save (checkpoint)
   • Write:

     Completed / Blocked / Next Step

   • If blocked: Suggest updating status to

     status:blocked

2. Resume
   • Read issue + latest checkpoint
   • Return: Last status + next step

Save Decision Process (Which One to Update)

1. User provides

   #issue

   : Directly update this issue.
2. Context has bound

   Issue #

   : Update this issue.
3. Otherwise, pull candidate issues from the current repository (open +

   repo:*

   ).
4. Branches:
   • 0 candidates: Trigger the "Additional Condition (Create and Save)" below.
   • 1 candidate: Automatically select and report back.
   • 2+ candidates: List 3~5 candidates for user selection; do not write until selection is made.

Resume Decision Process (Which One to Read)

1. User provides

   #issue

   : Directly resume.
2. Context has bound

   Issue #

   : Prioritize resuming this issue.
3. Otherwise, list candidates from the current repository (prioritize

   status:in-progress

   /

   status:blocked

   ).
4. Output resume summary after confirmation.

Command Reference (Use Original

gh issue

Commands Exclusively)

• Save:

  gh issue comment <id> -R <owner>/<repo> --body "Checkpoint YYYY-MM-DD HH:mm\nCompleted: ...\nBlocked: ...\nNext Step: ..."

• Resume:

  gh issue view <id> -R <owner>/<repo> --comments

• Candidate List:

  gh issue list -R <owner>/<repo> --state open --label "repo:<repo>" --limit 20 --json number,title,updatedAt,labels,url

Output Specifications

• After each call, return: Executed action, Issue number/link, current status, next step suggestion.
• When there are multiple candidates, must first list them and request user confirmation.

Mandatory One-Line Receipt Template

• Save Receipt:

  • Saved #<issue> | Status:<status> | Next Step:<next> | <url>

• Resume Receipt:

  • Resumed #<issue> | Status:<status> | Next Step:<next> | <url>

• If

  status

  /

  next

  is missing, use

  -

  as placeholder, do not omit the field.
• Receipt must be a single line for quick scanning and copying.

Additional Condition (Create and Save)

• This condition only takes effect when performing "save", it is a fallback branch and does not change the main responsibility of "only save + resume".
• Trigger Condition: No

  #issue

  provided, no bound

  Issue #

  , 0 candidate issues.
• Action: Create an issue and immediately write the first checkpoint (no requirement for user to manually initialize first).
• Receipt: Follow the save receipt template (

  Saved #<issue> | Status:<status> | Next Step:<next> | <url>

  ).

Relationship with W01~W05

• w01/w02

  : Responsible for initializing or binding issues; then call W00 to save.

• w03/w04

  : Call W00 frequently to save/resume during execution.

• w05

  : Responsible for closing tasks; call W00 to save one last time if necessary.

Manual Call Examples

• save

• resume

Interaction Rules: Users only need to enter keywords; issue selection, field completion and candidate lists are automatically determined and confirmed by the system.

Edge Cases

• No issue provided and no candidates: Trigger "Additional Condition (Create and Save)".
• Too many candidates: Only display the 3~5 most recently updated ones.
• Unclear repository context: First ask user to confirm

  <owner>/<repo>

  , then perform save/resume.

• gh

  not logged in: Prompt

  gh auth login

  .
• Do not use aliases, execute exclusively with original commands as specified above.