Initialization (gatekeeper-init)

Version number = current Git branch name (rules refer to the

gatekeeper

skill). Only requirement.md / progress.md are created; design/review/test are instantiated in phases by

gatekeeper-next

.

Procedure

1. Create Directory

• ${project root}/.gatekeeper/${version number}/

  does not exist → create it.
• Already exists → list files and ask for manual confirmation (skip/confirm overwrite/supplement), no writing without confirmation; branch name contains illegal directory characters → abort and prompt for handling.

2. Instantiate Templates

• Copy from the

  template/

  directory of the

  gatekeeper

  skill:

  _template-requirement.md

  → requirement.md,

  _template-progress.md

  → progress.md.
• Replace the

  ${version number}

  placeholder with the actual branch name; do not modify other content.

3. Validation (Do Not Proceed If Failed)

• Both files exist and no

  ${

  residues remain → pass.
• Failed → output failed items, write the

  .init-incomplete

  marker, refuse to start, wait for manual repair and re-run.

4. Output

• Directory path + file list, prompt to manually fill in requirement.md before entering the requirement phase.

Pitfalls

1. Only perform placeholder replacement, prohibit modifying the business content of templates; do not write requirement.md / progress.md on behalf of users.
2. Prohibit overwriting existing directories without confirmation.