From 0742913c8174671e2b22aeea84e39b88211116c6 Mon Sep 17 00:00:00 2001 From: Markus Graf Date: Sun, 30 Nov 2025 21:10:35 +0100 Subject: [PATCH] docs: relocate OpenSpec instructions to the beginning of AGENTS.md --- AGENTS.md | 37 +++++++++++++++++++------------------ 1 file changed, 19 insertions(+), 18 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index b150396..eb4ef6f 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -1,3 +1,21 @@ +# OpenSpec Instructions + +These instructions are for AI assistants working in this project. + +Always open `@/openspec/AGENTS.md` when the request: +- Mentions planning or proposals (words like proposal, spec, change, plan) +- Introduces new capabilities, breaking changes, architecture shifts, or big performance/security work +- Sounds ambiguous and you need the authoritative spec before coding + +Use `@/openspec/AGENTS.md` to learn: +- How to create and apply change proposals +- Spec format and conventions +- Project structure and guidelines + +Keep this managed block so 'openspec update' can refresh the instructions. + + + # Git Workflow ## Branching Strategy @@ -46,21 +64,4 @@ When the user requests a new feature, change, or proposal: - All changes go through feature branches - Keeps history clean and reviewable - -# OpenSpec Instructions - -These instructions are for AI assistants working in this project. - -Always open `@/openspec/AGENTS.md` when the request: -- Mentions planning or proposals (words like proposal, spec, change, plan) -- Introduces new capabilities, breaking changes, architecture shifts, or big performance/security work -- Sounds ambiguous and you need the authoritative spec before coding - -Use `@/openspec/AGENTS.md` to learn: -- How to create and apply change proposals -- Spec format and conventions -- Project structure and guidelines - -Keep this managed block so 'openspec update' can refresh the instructions. - - \ No newline at end of file + \ No newline at end of file