specs: Add an AGENTS.md file for working on the specs

Author: zah

.obsidian/workspace.json

@@ -13,12 +13,12 @@
             "state": {
               "type": "markdown",
               "state": {
-                "file": "specs/cli-spec.md",
+                "file": "specs/AGENTS.md",
                 "mode": "source",
                 "source": false
               },
               "icon": "lucide-file",
-              "title": "cli-spec"
+              "title": "AGENTS"
             }
           },
           {
@@ -194,8 +194,10 @@
   },
   "active": "01bf72509d2b5652",
   "lastOpenFiles": [
-    "specs/@initial-developer-input/Configuration.md",
+    "specs/agent-time-travel.md",
+    "specs/AGENTS.md",
     "specs/cli-spec.md",
+    "specs/@initial-developer-input/Configuration.md",
     "specs/@initial-developer-input/WebUI, TUI, REST Service.md",
     "specs/@initial-developer-input",
     "specs/local-mode.md",
@@ -205,7 +207,6 @@
     "specs/fs-snapshots/milestone_3.md",
     "specs/fs-snapshots/milestone_2.md",
     "specs/fs-snapshots/milestone_1.md",
-    "specs/agent-time-travel.md",
     "specs/webui-prd.md",
     "specs/tui-prd.md",
     "specs/rest-service.md",
@@ -220,7 +221,6 @@
     "specs/connectivity-layer.md",
     "specs/configuration.md",
     "specs/schemas/AGENTS.md",
-    "specs/agents/_template.md",
     "specs/@research"
   ]
 }

specs/AGENTS.md

@@ -0,0 +1,7 @@
+This folder contains a work-in-progress specification for the next iteration of the agents-workflow product.
+
+The main ideas of the product are described in the [marketing-one-pager](../docs/marketing-one-pager.md) document.
+
+Currently, the spec is not finalized and we are not ready to start the implementation of the software. The folder `specs/@initial-developer-input` contains files that should be treated as a ground truth for the specification effort. You are expected to work on the markdown files in the specs folder, which should detail everything with a much higher precision, but not all information in them has been fully reviewed by the development team yet.
+
+Some of the markdown files have standardized Obsidian headers indicating their current review status. Avoid modifying files which status is "Reviewed" or "Final" unless explicitly asked.