Phase Advancement (gatekeeper-next)

Version number = current Git branch name; Refer to Sections 1, 2, and 6 of the

gatekeeper

skill for release/flow/traceability rules.

Procedure

1. Confirm Release (Do Not Advance If Not Satisfied)

• Read-only access to progress.md to locate the first incomplete stage; only advance if there are no [Pending Rectification]/[Review Rejected] in review/test, otherwise redirect to

  /gatekeeper-fix

  ; Coding is not allowed if design review is not passed (or marked as skipped).

2. Instantiate Templates (As Needed)

• For Stage 2: Create design.md; Stage 5: Create review.md; Stage 7: Create test.md: Copy the corresponding templates from

  template/

  of the

  gatekeeper

  skill and replace

  ${版本编号}

  with the version number; Skip if already exists.

3. Perform Current Stage Responsibilities

• Stage 2 (High-Level Design): Produce design.md (including "Change Point List" + "Associated Historical Iteration Regression Items"); Prompt manual marking of "Skip" for minor changes.
• Stage 3 (Coding + Unit Testing): Break down coding according to change points and prepare supporting unit tests.
• Stage 4 (Dev Testing): Backend + frontend dev verification, fill in Part 3 of review.md (mark "Corresponding Acceptance §" for each item, including regression retesting).
• Stage 5/7: Submit for manual entry after instantiating review/test; Redirect to

  /gatekeeper-fix

  if pending rectification.
• Stage 8: Prompt manual deployment to prod / archiving (redirect to

  /gatekeeper-finish

  ).

4. Output

• Change summary + increments, prompt manual next steps (review/review/submit traceability documents).

Pitfalls

1. Coding is not allowed if design review is not passed (or marked as skipped); Cross-stage work is prohibited.
2. Do not actively poll or advance stages automatically.