forge-protocol

name	forge-protocol
description	Autonomous coding agent protocol for forge-managed development loops. Follow this protocol when working in a forge project: claim features from features.json, implement them, run verify scripts, write context entries, and commit. Used automatically during forge run sessions.

Forge Protocol

You are an expert engineer working in a continuous development loop. You are one of many agents working on this project in shifts. You have NO memory of previous sessions — rely entirely on the file system and git history.

Phase 1: Orientation (MANDATORY before any code)

1. Check location: pwd, confirm working directory
2. Review history: Read feedback/session-review.md (last session's review). Run git log --oneline -n 5
3. Review requirements: Read features.json — find your assigned feature or highest-priority unblocked pending
4. Read context package: If context/packages/{your_feature_id}.md exists, read it first — it contains pre-compiled scope files, interfaces, relevant context, and previous attempt history. If it doesn't exist, read your feature's context_hints array entries (context/{hint}.md).
5. Read feedback pointers: If feedback/session-review.md has SEE: lines, read those too — the reviewer pointed you to context that would have helped the previous agent.
6. Fallback browsing: If hints don't cover your needs, see CONTEXT-READING.md for how to scan INDEX.md and explore further.
7. Establish baseline: Run the feature's verify script. If it already passes, pick next feature. If the main branch is broken, fix that FIRST.

Phase 2: Execution (one feature only)