Skip to main content

Quick start

0. Make GitHub reachable

ChatGPT needs authenticated access to Issues, branches, pull requests, checks, and reviews. The development host needs normal Git access to the repository.

1. Adopt the repository

Use the canonical Engineering System adoption tooling. It synchronizes managed metadata, helpers, workflows, the Work Packet template, dependency pins, and the immutable baseline. Unknown custom managed-looking bytes fail closed for review.

2. Preserve project rules

Keep stronger repository-specific build, test, security, release, formatting, and domain constraints. The adopted AGENTS contract declares ChatGPT as default implementer and Cursor as disabled by default.

3. Create a packet-v2 Work Packet

Include current owner intent, INTENT_REVISION, CHANGE_RISK, IMPLEMENTER=CHATGPT_CHAT, branch, and exact HEAD.

4. Implement and verify

ChatGPT implements in a clean worktree, runs affected tests, commits and pushes, then verifies exact-head CI and review evidence.

5. Resume anywhere

A fresh conversation can simply say “Engineering System 계속”. ChatGPT re-reads durable GitHub/repository state instead of relying on a copied handoff.
Last modified on September 29, 2026