harness-everything 0.2.1 → 0.3.6

package/{create-agent-launcher → multi-agent-workspace}/guidelines/platform-codex.md

@@ -1,146 +1,146 @@
----
-description: "Platform guidelines for generating agent scaffolds targeting Codex / Custom API environments. Covers naming, OpenAI Tool Spec / JSON Schema format, directory layout, and custom ask_user function calling."
----
-
-# Platform Guidelines: Codex / Custom API Environment
-
-## Naming Convention
-
-- Follow system variable / key-value naming conventions (e.g., `requirement_analyzer`, `backend_developer`).
-- Use lowercase with underscores or hyphens; avoid spaces.
-- Names serve as JSON object keys — they must be valid identifiers in most languages.
-
-## Tools Declaration
-
-There are **no built-in tools**. All tools must be defined using the **OpenAI Tool Spec (JSON Schema)** format and implemented in your local orchestrator code.
-
-When generating agent files from templates (if not using pure JSON), substitute the placeholders as follows:
-- `{{TOOLS_ARRAY_DECLARATION}}`: *(Leave empty in Markdown, handled via JSON configuration)*
-- `{{READ_TOOL_NAME}}`: `read_file`
-- `{{EDIT_TOOL_NAME}}`: `write_file`
-- `{{SEARCH_TOOL_NAME}}`: `search`
-- `{{EXECUTE_TOOL_NAME}}`: `execute_command`
-
-Each agent definition includes a `tools` array of JSON Schema objects:
-
-```json
-{
-  "agents": {
-    "requirement_analyzer": {
-      "name": "requirement_analyzer",
-      "description": "Analyzes user requirements and creates implementation documents.",
-      "tools": [
-        {
-          "type": "function",
-          "function": {
-            "name": "read_file",
-            "description": "Read a file from the project.",
-            "parameters": {
-              "type": "object",
-              "properties": {
-                "path": { "type": "string", "description": "File path to read." }
-              },
-              "required": ["path"]
-            }
-          }
-        },
-        {
-          "type": "function",
-          "function": {
-            "name": "ask_user",
-            "description": "Pause the agent loop and ask the user a question.",
-            "parameters": {
-              "type": "object",
-              "properties": {
-                "question": { "type": "string" },
-                "options": {
-                  "type": "array",
-                  "items": { "type": "string" }
-                }
-              },
-              "required": ["question"]
-            }
-          }
-        }
-      ]
-    }
-  }
-}
-```
-
-## Directory Layout
-
-All paths are **custom** — defined by the local orchestrator implementation:
-
-| Artifact | Suggested Path |
-|----------|---------------|
-| Agent definitions | `config/agents/*.json` or `config/agents.json` |
-| System prompt | `config/system_prompt.txt` |
-| Tool schemas | `config/tools/*.json` |
-| Global config | `~/.config/myapp/` or as defined by your app |
-
-Default target directory is `config/`.
-
-## User Interaction Mechanism
-
-There is **no built-in confirmation mechanism**. Implement a custom `ask_user` function tool that follows the OpenAI Function Calling / Tool Use pattern:
-
-1. The agent calls `ask_user` with a `question` and optional `options`.
-2. The API returns the function call in its response.
-3. Your **local orchestrator code** intercepts the call, renders the UI (terminal prompt, web form, etc.), and submits the user's answer back as a tool result.
-4. The agent resumes execution.
-
-The `ask_user` schema should mirror `vscode_askQuestions` for portability:
-
-```json
-{
-  "type": "function",
-  "function": {
-    "name": "ask_user",
-    "description": "Ask the user a question and wait for their response before continuing.",
-    "parameters": {
-      "type": "object",
-      "properties": {
-        "header": { "type": "string", "description": "Short identifier for the question." },
-        "question": { "type": "string", "description": "The question to ask." },
-        "options": {
-          "type": "array",
-          "items": {
-            "type": "object",
-            "properties": {
-              "label": { "type": "string" },
-              "recommended": { "type": "boolean" }
-            },
-            "required": ["label"]
-          }
-        },
-        "allowFreeformInput": { "type": "boolean", "default": true }
-      },
-      "required": ["header", "question"]
-    }
-  }
-}
-```
-
-## System Prompt / Instructions File
-
-The system prompt format is fully custom. Suggested location: `config/system_prompt.txt` or `config/system_prompt.md`. Include the orchestrator rules adapted for your API loop implementation.
-
-## Agent File Format
-
-Agent definitions are typically JSON objects:
-
-```json
-{
-  "name": "requirement_analyzer",
-  "description": "Analyzes requirements and creates implementation documents.",
-  "system_prompt": "You are an expert AI Architect...",
-  "tools": ["read_file", "edit_file", "ask_user"],
-  "constraints": [
-    "DO NOT implement features yourself.",
-    "ALWAYS create a structured implementation document first."
-  ]
-}
-```
-
-Implement `read_file`, `edit_file`, and all other tools referenced in `tools` arrays in your orchestrator's backend code.
+---
+description: "Platform guidelines for generating agent scaffolds targeting Codex / Custom API environments. Covers naming, OpenAI Tool Spec / JSON Schema format, directory layout, and custom ask_user function calling."
+---
+
+# Platform Guidelines: Codex / Custom API Environment
+
+## Naming Convention
+
+- Follow system variable / key-value naming conventions (e.g., `requirement_analyzer`, `backend_developer`).
+- Use lowercase with underscores or hyphens; avoid spaces.
+- Names serve as JSON object keys — they must be valid identifiers in most languages.
+
+## Tools Declaration
+
+There are **no built-in tools**. All tools must be defined using the **OpenAI Tool Spec (JSON Schema)** format and implemented in your local orchestrator code.
+
+When generating agent files from templates (if not using pure JSON), substitute the placeholders as follows:
+- `{{TOOLS_ARRAY_DECLARATION}}`: *(Leave empty in Markdown, handled via JSON configuration)*
+- `{{READ_TOOL_NAME}}`: `read_file`
+- `{{EDIT_TOOL_NAME}}`: `write_file`
+- `{{SEARCH_TOOL_NAME}}`: `search`
+- `{{EXECUTE_TOOL_NAME}}`: `execute_command`
+
+Each agent definition includes a `tools` array of JSON Schema objects:
+
+```json
+{
+  "agents": {
+    "requirement_analyzer": {
+      "name": "requirement_analyzer",
+      "description": "Analyzes user requirements and creates implementation documents.",
+      "tools": [
+        {
+          "type": "function",
+          "function": {
+            "name": "read_file",
+            "description": "Read a file from the project.",
+            "parameters": {
+              "type": "object",
+              "properties": {
+                "path": { "type": "string", "description": "File path to read." }
+              },
+              "required": ["path"]
+            }
+          }
+        },
+        {
+          "type": "function",
+          "function": {
+            "name": "ask_user",
+            "description": "Pause the agent loop and ask the user a question.",
+            "parameters": {
+              "type": "object",
+              "properties": {
+                "question": { "type": "string" },
+                "options": {
+                  "type": "array",
+                  "items": { "type": "string" }
+                }
+              },
+              "required": ["question"]
+            }
+          }
+        }
+      ]
+    }
+  }
+}
+```
+
+## Directory Layout
+
+All paths are **custom** — defined by the local orchestrator implementation:
+
+| Artifact | Suggested Path |
+|----------|---------------|
+| Agent definitions | `config/agents/*.json` or `config/agents.json` |
+| System prompt | `config/system_prompt.txt` |
+| Tool schemas | `config/tools/*.json` |
+| Global config | `~/.config/myapp/` or as defined by your app |
+
+Default target directory is `config/`.
+
+## User Interaction Mechanism
+
+There is **no built-in confirmation mechanism**. Implement a custom `ask_user` function tool that follows the OpenAI Function Calling / Tool Use pattern:
+
+1. The agent calls `ask_user` with a `question` and optional `options`.
+2. The API returns the function call in its response.
+3. Your **local orchestrator code** intercepts the call, renders the UI (terminal prompt, web form, etc.), and submits the user's answer back as a tool result.
+4. The agent resumes execution.
+
+The `ask_user` schema should mirror `vscode_askQuestions` for portability:
+
+```json
+{
+  "type": "function",
+  "function": {
+    "name": "ask_user",
+    "description": "Ask the user a question and wait for their response before continuing.",
+    "parameters": {
+      "type": "object",
+      "properties": {
+        "header": { "type": "string", "description": "Short identifier for the question." },
+        "question": { "type": "string", "description": "The question to ask." },
+        "options": {
+          "type": "array",
+          "items": {
+            "type": "object",
+            "properties": {
+              "label": { "type": "string" },
+              "recommended": { "type": "boolean" }
+            },
+            "required": ["label"]
+          }
+        },
+        "allowFreeformInput": { "type": "boolean", "default": true }
+      },
+      "required": ["header", "question"]
+    }
+  }
+}
+```
+
+## System Prompt / Instructions File
+
+The system prompt format is fully custom. Suggested location: `config/system_prompt.txt` or `config/system_prompt.md`. Include the orchestrator rules adapted for your API loop implementation.
+
+## Agent File Format
+
+Agent definitions are typically JSON objects:
+
+```json
+{
+  "name": "requirement_analyzer",
+  "description": "Analyzes requirements and creates implementation documents.",
+  "system_prompt": "You are an expert AI Architect...",
+  "tools": ["read_file", "edit_file", "ask_user"],
+  "constraints": [
+    "DO NOT implement features yourself.",
+    "ALWAYS create a structured implementation document first."
+  ]
+}
+```
+
+Implement `read_file`, `edit_file`, and all other tools referenced in `tools` arrays in your orchestrator's backend code.

package/multi-agent-workspace/guidelines/platform-continue.md

@@ -0,0 +1,38 @@
+---
+description: "Platform guidelines for generating agent scaffolds targeting Continue.dev. Covers naming, tool declarations, directory layout, and interaction mechanisms."
+---
+
+# Platform Guidelines: Continue.dev
+
+## Naming Convention
+
+- Rule files use kebab-case (e.g., `harness.md`, `backend-developer.md`).
+
+## Tools Declaration
+
+Continue manages tool execution permissions at the extension level. Use standard intent names:
+
+```yaml
+tools: [read, edit, search, execute]
+```
+
+When generating agent files from templates, substitute the placeholders as follows:
+- `{{TOOLS_ARRAY_DECLARATION}}`: `tools: [read, edit, search, execute]`
+- `{{READ_TOOL_NAME}}`: `read`
+- `{{EDIT_TOOL_NAME}}`: `edit`
+- `{{SEARCH_TOOL_NAME}}`: `search`
+- `{{EXECUTE_TOOL_NAME}}`: `execute`
+
+## Directory Layout
+
+| Artifact | Path |
+|----------|------|
+| Native Project Rules | `.continue/rules/*.md` (project) / `~/.continue/rules/*.md` (global) |
+| System Prompt | `.continue/rules/harness.md` (with YAML frontmatter `alwaysApply: true`) |
+
+Default target directory is `.continue/rules/`.
+
+## User Interaction & Enforcement Mechanism
+
+Continue.dev does not provide lifecycle execution hooks. Rules are loaded with `alwaysApply: true` frontmatter and act as **Advisory Guidance**.
+Ask clarifying questions directly within the Continue Chat interface.

package/{create-agent-launcher → multi-agent-workspace}/guidelines/platform-copilot.md

@@ -1,74 +1,74 @@
----
-description: "Platform guidelines for generating agent scaffolds targeting GitHub Copilot (VS Code). Covers naming, tool declarations, directory layout, and interaction mechanisms."
----
-
-# Platform Guidelines: GitHub Copilot (VS Code)
-
-## Naming Convention
-
-- Agent names are **flexible** — spaces, Chinese characters, and mixed case are allowed.
-- Recommended style: Title Case with spaces (e.g., `Requirement Analyzer`, `Backend Developer`).
-- File names use kebab-case (e.g., `requirement-analyzer.agent.md`).
-
-## Tools Declaration
-
-Use the VS Code-encapsulated permission names as a YAML array:
-
-```yaml
-tools: [read, edit, search, execute]
-```
-
-When generating agent files from templates, substitute the placeholders as follows:
-- `{{TOOLS_ARRAY_DECLARATION}}`: `tools: [read, edit, search, execute]` (exclude `execute` for Requirement Analyzer)
-- `{{READ_TOOL_NAME}}`: `read`
-- `{{EDIT_TOOL_NAME}}`: `edit`
-- `{{SEARCH_TOOL_NAME}}`: `search`
-- `{{EXECUTE_TOOL_NAME}}`: `execute`
-
-## Directory Layout
-
-| Artifact | Path |
-|----------|------|
-| Agent definitions | `<target_dir>/agents/*.agent.md` |
-| Orchestrator instructions | `<target_dir>/instructions/orchestrator.instructions.md` |
-| Skill entry point | `<target_dir>/skills/agent-launcher/SKILL.md` |
-| System prompt | `.github/copilot-instructions.md` |
-| Global config | `~/.config/github-copilot/` |
-
-Default `<target_dir>` is `.github/`.
-
-## User Interaction Mechanism
-
-Use the `vscode_askQuestions` tool to pause the workflow and prompt the user for decisions.
-
-```json
-[{
-  "header": "unique_key",
-  "question": "Your question here?",
-  "options": [
-    { "label": "Option A", "recommended": true },
-    { "label": "Option B" }
-  ],
-  "allowFreeformInput": true
-}]
-```
-
-This renders as a dropdown or input box in the VS Code window.
-
-## System Prompt / Instructions File
-
-After generating agents, ensure `.github/copilot-instructions.md` contains the `## 🤖 State Machine Orchestrator Instructions` block. If the file does not exist, create it.
-
-## Agent File Format
-
-Standard `.agent.md` file with YAML frontmatter:
-
-```yaml
----
-name: "Requirement Analyzer"
-description: "Use when: ..."
-tools: [read, edit, search]
----
-```
-
-All files MUST include a YAML frontmatter `description` field for context optimization.
+---
+description: "Platform guidelines for generating agent scaffolds targeting GitHub Copilot (VS Code). Covers naming, tool declarations, directory layout, and interaction mechanisms."
+---
+
+# Platform Guidelines: GitHub Copilot (VS Code)
+
+## Naming Convention
+
+- Agent names are **flexible** — spaces, Chinese characters, and mixed case are allowed.
+- Recommended style: Title Case with spaces (e.g., `Requirement Analyzer`, `Backend Developer`).
+- File names use kebab-case (e.g., `requirement-analyzer.agent.md`).
+
+## Tools Declaration
+
+Use the VS Code-encapsulated permission names as a YAML array:
+
+```yaml
+tools: [read, edit, search, execute]
+```
+
+When generating agent files from templates, substitute the placeholders as follows:
+- `{{TOOLS_ARRAY_DECLARATION}}`: `tools: [read, edit, search, execute]` (exclude `execute` for Requirement Analyzer)
+- `{{READ_TOOL_NAME}}`: `read`
+- `{{EDIT_TOOL_NAME}}`: `edit`
+- `{{SEARCH_TOOL_NAME}}`: `search`
+- `{{EXECUTE_TOOL_NAME}}`: `execute`
+
+## Directory Layout
+
+| Artifact | Path |
+|----------|------|
+| Agent definitions | `<target_dir>/agents/*.agent.md` |
+| Orchestrator instructions | `<target_dir>/instructions/orchestrator.instructions.md` |
+| Skill entry point | `<target_dir>/skills/agent-launcher/SKILL.md` |
+| System prompt | `.github/copilot-instructions.md` |
+| Global config | `~/.config/github-copilot/` |
+
+Default `<target_dir>` is `.github/`.
+
+## User Interaction Mechanism
+
+Use the `vscode_askQuestions` tool to pause the workflow and prompt the user for decisions.
+
+```json
+[{
+  "header": "unique_key",
+  "question": "Your question here?",
+  "options": [
+    { "label": "Option A", "recommended": true },
+    { "label": "Option B" }
+  ],
+  "allowFreeformInput": true
+}]
+```
+
+This renders as a dropdown or input box in the VS Code window.
+
+## System Prompt / Instructions File
+
+After generating agents, ensure `.github/copilot-instructions.md` contains the `## 🤖 State Machine Orchestrator Instructions` block. If the file does not exist, create it.
+
+## Agent File Format
+
+Standard `.agent.md` file with YAML frontmatter:
+
+```yaml
+---
+name: "Requirement Analyzer"
+description: "Use when: ..."
+tools: [read, edit, search]
+---
+```
+
+All files MUST include a YAML frontmatter `description` field for context optimization.

package/multi-agent-workspace/guidelines/platform-cursor.md

@@ -0,0 +1,40 @@
+---
+description: "Platform guidelines for generating agent scaffolds targeting Cursor. Covers naming, tool declarations, directory layout, and interaction mechanisms."
+---
+
+# Platform Guidelines: Cursor
+
+## Naming Convention
+
+- Agent/Rule names use lower-kebab-case (e.g., `requirement-analyzer`, `backend-developer`).
+- File names follow `.cursorrules` or `.cursor/rules/*.mdc` depending on project structure.
+
+## Tools Declaration
+
+Cursor manages tool permissions natively through its IDE setting UI. Use standard tool intent categories:
+
+```yaml
+tools: [read, edit, search, execute]
+```
+
+When generating agent files from templates, substitute the placeholders as follows:
+- `{{TOOLS_ARRAY_DECLARATION}}`: `tools: [read, edit, search, execute]`
+- `{{READ_TOOL_NAME}}`: `read`
+- `{{EDIT_TOOL_NAME}}`: `edit`
+- `{{SEARCH_TOOL_NAME}}`: `search`
+- `{{EXECUTE_TOOL_NAME}}`: `execute`
+
+## Directory Layout
+
+| Artifact | Path |
+|----------|------|
+| Native Project Rules | `.cursorrules` (project root) |
+| Modular Rule Definitions | `.cursor/rules/*.mdc` |
+| System Prompt | `.cursorrules` |
+
+Default target directory is `.cursor/`.
+
+## User Interaction & Enforcement Mechanism
+
+Cursor does not provide lifecycle hooks or exit code interception. All rule files operate as **Advisory Context** injected into the model prompt.
+Ask questions directly in chat or request user confirmation before major file modifications.

package/multi-agent-workspace/guidelines/platform-hermes.md

@@ -0,0 +1,38 @@
+---
+description: "Platform guidelines for generating agent scaffolds targeting Hermes Agent (Nous Research). Covers naming, tool declarations, directory layout, and interaction mechanisms."
+---
+
+# Platform Guidelines: Hermes Agent (Nous Research)
+
+## Naming Convention
+
+- Uses `.hermes.md` project-level context file or standard markdown rules files.
+
+## Tools Declaration
+
+Hermes Agent auto-detects CLI capabilities. Use standard tool declarations:
+
+```yaml
+tools: [read, edit, search, execute]
+```
+
+When generating agent files from templates, substitute the placeholders as follows:
+- `{{TOOLS_ARRAY_DECLARATION}}`: `tools: [read, edit, search, execute]`
+- `{{READ_TOOL_NAME}}`: `read`
+- `{{EDIT_TOOL_NAME}}`: `edit`
+- `{{SEARCH_TOOL_NAME}}`: `search`
+- `{{EXECUTE_TOOL_NAME}}`: `execute`
+
+## Directory Layout
+
+| Artifact | Path |
+|----------|------|
+| Native Context | `.hermes.md` (project root) |
+| Fallback Context | Reads `AGENTS.md` / `CLAUDE.md` / `.cursorrules` if present |
+
+Default target directory is project root (`.hermes.md`).
+
+## User Interaction & Enforcement Mechanism
+
+Hermes Agent loads `.hermes.md` into session context. Like other non-hook platforms, enforcement is **Advisory Only**.
+Interactions and question prompting happen in the Hermes terminal or web UI session.