opencode-orchestrator-plugin 1.0.0-beta.1 → 1.0.0-beta.11

package/README.md

@@ -121,9 +121,42 @@ This project follows **Conventional Commits**. Releases are automated via Semant
 
 ---
 
-## 🔁 Origin Notice
+## 🔁 Origin & Lineage
 
-This project started as a fork of https://github.com/derekbar90/opencode-conductor, but has been reworked into an OpenCode-first orchestrator with new command and agent conventions.
+This project is part of the Context-Driven Development lineage:
+
+- **Original Source**: [gemini-cli-extensions/conductor](https://github.com/gemini-cli-extensions/conductor) - The original Gemini CLI framework
+- **Direct Parent**: [derekbar90/opencode-conductor](https://github.com/derekbar90/opencode-conductor) - OpenCode port
+- **This Project**: Evolution with new command and agent conventions for OpenCode v1.1.1+
+
+## 🔄 Relationship to Conductor
+
+Orchestrator brings the proven Context-Driven Development methodology from Gemini CLI to OpenCode with architectural adaptations:
+
+### Architectural Differences
+- **Command Format**: TOML-based Gemini CLI commands → JSON-based OpenCode plugin prompts
+- **Execution Model**: Direct CLI invocation → Agent-based execution with `@orchestrator`
+- **Permission System**: Gemini CLI native → OpenCode v1.1.1 granular permissions
+
+### Feature Parity
+See [Conductor Feature Parity Gap Analysis](./orchestrator/tracks/conductor_parity_20260118/gap-analysis.md) for a comprehensive comparison. 
+
+**Status**: ✅ **100% Feature Parity Achieved** (51/51 features)
+
+Key highlights:
+- ✅ All 5 core commands implemented
+- ✅ Context → Spec → Plan → Implement lifecycle
+- ✅ Documentation synchronization
+- ✅ TDD workflow with Red-Green-Refactor
+- ✅ Brownfield project support
+- ✅ Autogenerate option for faster onboarding
+- ✅ Phase completion verification with checkpoints
+- ✅ Git notes integration for task tracking
+
+### Orchestrator Enhancements
+- 23 code styleguide templates (vs 8 in conductor)
+- Native OpenCode plugin system integration
+- Multi-agent workflow support (OhMyOpenCode synergy)
 
 ## 📜 License
 

package/dist/index.js

@@ -5,92 +5,35 @@ import NewTrackPromptJson from "./prompts/orchestrator/newTrack.json" with { typ
 import RevertPromptJson from "./prompts/orchestrator/revert.json" with { type: "json" };
 import SetupPromptJson from "./prompts/orchestrator/setup.json" with { type: "json" };
 import StatusPromptJson from "./prompts/orchestrator/status.json" with { type: "json" };
+import { detectOrchestratorConfig } from "./utils/configDetection.js";
 const asPrompt = (prompt) => (typeof prompt === "string" ? prompt : "");
 const asDescription = (description) => typeof description === "string" ? description : undefined;
 export const MyPlugin = async ({ directory, }) => {
     const orchestratorPath = path.join(directory, "orchestrator");
     let fileHeirarchy = "";
-    const readIgnoreFile = (filePath) => {
-        if (!fs.existsSync(filePath))
-            return [];
-        return fs
-            .readFileSync(filePath, "utf-8")
-            .split("\n")
-            .map((line) => line.trim())
-            .filter((line) => line.length > 0 && !line.startsWith("#"));
-    };
-    const buildIgnoreMatcher = (rootDir) => {
-        const ignoreFile = path.join(rootDir, ".ignore");
-        const geminiIgnoreFile = path.join(rootDir, ".geminiignore");
-        const gitIgnoreFile = path.join(rootDir, ".gitignore");
-        const gitIgnorePatterns = readIgnoreFile(gitIgnoreFile);
-        const ignoreOverrides = readIgnoreFile(ignoreFile)
-            .filter((pattern) => pattern.startsWith("!"))
-            .map((pattern) => pattern.slice(1));
-        const geminiIgnorePatterns = readIgnoreFile(geminiIgnoreFile);
-        const ignored = new Set();
-        for (const pattern of gitIgnorePatterns.concat(geminiIgnorePatterns)) {
-            if (!pattern.startsWith("#") && !pattern.startsWith("!")) {
-                ignored.add(pattern.replace(/\/$/, ""));
-            }
-        }
-        const allowed = new Set(ignoreOverrides.map((pattern) => pattern.replace(/\/$/, "")));
-        const isIgnored = (relativePath) => {
-            const normalized = relativePath.replace(/\\/g, "/");
-            if (allowed.size > 0) {
-                for (const allow of allowed) {
-                    if (normalized === allow || normalized.startsWith(`${allow}/`))
-                        return false;
-                }
+    const getFilesRecursively = (dir) => {
+        let results = [];
+        if (!fs.existsSync(dir))
+            return results;
+        const list = fs.readdirSync(dir);
+        list.forEach((file) => {
+            const filePath = path.join(dir, file);
+            const stat = fs.statSync(filePath);
+            if (stat && stat.isDirectory()) {
+                results = results.concat(getFilesRecursively(filePath));
             }
-            for (const ignorePattern of ignored) {
-                if (normalized === ignorePattern || normalized.startsWith(`${ignorePattern}/`)) {
-                    return true;
-                }
-            }
-            return false;
-        };
-        return { ignores: isIgnored };
-    };
-    const getFileTreeSummary = (rootDir, maxEntries = 200, maxChars = 4000) => {
-        const ig = buildIgnoreMatcher(rootDir);
-        const directories = new Set();
-        const queue = [rootDir];
-        while (queue.length > 0) {
-            const current = queue.shift();
-            if (!current)
-                continue;
-            const entries = fs.readdirSync(current, { withFileTypes: true });
-            for (const entry of entries) {
-                const entryPath = path.join(current, entry.name);
-                const relativePath = path.relative(rootDir, entryPath) || ".";
-                if (ig.ignores(relativePath)) {
-                    continue;
-                }
-                if (entry.isDirectory()) {
-                    directories.add(path.relative(rootDir, entryPath) || ".");
-                    queue.push(entryPath);
+            else {
+                if (filePath.endsWith(".json") || filePath.endsWith(".md")) {
+                    results.push(filePath);
                 }
             }
-        }
-        const sorted = Array.from(directories).sort();
-        let summary = "";
-        let count = 0;
-        for (const dir of sorted) {
-            if (summary.length >= maxChars || count >= maxEntries)
-                break;
-            summary += `${dir}\n`;
-            count += 1;
-        }
-        if (summary.length >= maxChars || count >= maxEntries) {
-            summary += "...\n";
-        }
-        return summary.trim();
+        });
+        return results;
     };
     if (fs.existsSync(orchestratorPath)) {
-        fileHeirarchy = getFileTreeSummary(directory)
-            .split("\n")
-            .map((line) => `  - ${line}`)
+        const files = getFilesRecursively(orchestratorPath);
+        fileHeirarchy = files
+            .map((f) => path.relative(directory, f))
             .join("\n                    ");
     }
     const isOrchestratorSetup = () => {
@@ -98,15 +41,18 @@ export const MyPlugin = async ({ directory, }) => {
         return fs.existsSync(setupStatePath);
     };
     const setupOccurred = isOrchestratorSetup();
+    const configDetection = detectOrchestratorConfig();
     return {
         config: async (_config) => {
             _config.command = {
                 ..._config.command,
                 "orchestrator:implement": {
+                    agent: "orchestrator",
                     template: asPrompt(ImplementPromptJson.prompt) + `
             Environment Details: 
               - Directory: ${directory}
               - Orchestrator Setup: ${setupOccurred}
+              - Synergy Active (OMO): ${configDetection.synergyActive}
               - Current Orchestrator Files (Location: ${directory}/orchestrator)
                   File Tree:
                     ${fileHeirarchy}
@@ -114,33 +60,39 @@ export const MyPlugin = async ({ directory, }) => {
                     description: asDescription(ImplementPromptJson.description),
                 },
                 "orchestrator:newTrack": {
+                    agent: "orchestrator",
                     template: asPrompt(NewTrackPromptJson.prompt),
                     description: asDescription(NewTrackPromptJson.description),
                 },
                 "orchestrator:revert": {
+                    agent: "orchestrator",
                     template: asPrompt(RevertPromptJson.prompt),
                     description: asDescription(RevertPromptJson.description),
                 },
                 "orchestrator:setup": {
+                    agent: "orchestrator",
                     template: asPrompt(SetupPromptJson.prompt) + `
             Environment Details: 
               - Directory: ${directory}
               - Orchestrator Setup: ${setupOccurred}
+              - Synergy Active (OMO): ${configDetection.synergyActive}
               - Current Orchestrator Files (with tracks) (${directory}/orchestrator)
                 File Tree:
                   ${fileHeirarchy}
-
+ 
               **CRITICAL ENVIRONTMENTAL OVERRIDE:**: You are running inside OpenCode. Use ./config/opencode/node_modules/opencode-orchestrator-plugin for setup operations and respect .ignore (allowlist), .geminiignore, and .gitignore patterns when excluding files.
           `,
                     description: asDescription(SetupPromptJson.description),
                 },
                 "orchestrator:status": {
+                    agent: "orchestrator",
                     template: asPrompt(StatusPromptJson.prompt) + `
-
+ 
           
           ***Current Environment Details***: 
             - Current Working Directory: ${directory}
             - Orchestrator Setup Process Completed: ${setupOccurred}
+            - Synergy Active (OMO): ${configDetection.synergyActive}
             - Current Orchestrator Files (with tracks) (${directory}/orchestrator)
                 File Tree:
                   ${fileHeirarchy}

package/dist/index.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/index.test.js

@@ -0,0 +1,122 @@
+import { describe, it, expect, beforeEach, afterEach } from "vitest";
+import { buildIgnoreMatcher } from "./utils/ignoreMatcher.js";
+import * as fs from "fs";
+import * as path from "path";
+describe("getFileTreeSummary behavior", () => {
+    const testDir = path.join(process.cwd(), "test-temp-orchestrator-tree");
+    beforeEach(() => {
+        if (fs.existsSync(testDir)) {
+            fs.rmSync(testDir, { recursive: true });
+        }
+        fs.mkdirSync(testDir, { recursive: true });
+    });
+    afterEach(() => {
+        if (fs.existsSync(testDir)) {
+            fs.rmSync(testDir, { recursive: true });
+        }
+    });
+    it("should exclude .git directory from tree", () => {
+        fs.mkdirSync(path.join(testDir, ".git"));
+        fs.mkdirSync(path.join(testDir, "src"));
+        const ig = buildIgnoreMatcher(testDir, {
+            gitignore: [],
+            ignore: [],
+            geminiignore: [],
+        });
+        const directories = new Set();
+        const queue = [testDir];
+        while (queue.length > 0) {
+            const current = queue.shift();
+            if (!current)
+                continue;
+            const entries = fs.readdirSync(current, { withFileTypes: true });
+            for (const entry of entries) {
+                const entryPath = path.join(current, entry.name);
+                const relativePath = path.relative(testDir, entryPath) || ".";
+                if (entry.isDirectory()) {
+                    const normalizedDir = relativePath === "." ? "" : relativePath;
+                    if (!ig.shouldTraverse(normalizedDir)) {
+                        continue;
+                    }
+                    if (!ig.ignores(normalizedDir)) {
+                        directories.add(relativePath || ".");
+                    }
+                    queue.push(entryPath);
+                }
+            }
+        }
+        const sorted = Array.from(directories).sort();
+        expect(sorted).not.toContain(".git");
+        expect(sorted).toContain("src");
+    });
+    it("should exclude node_modules directory from tree", () => {
+        fs.mkdirSync(path.join(testDir, "node_modules"));
+        fs.mkdirSync(path.join(testDir, "src"));
+        const ig = buildIgnoreMatcher(testDir, {
+            gitignore: [],
+            ignore: [],
+            geminiignore: [],
+        });
+        const directories = new Set();
+        const queue = [testDir];
+        while (queue.length > 0) {
+            const current = queue.shift();
+            if (!current)
+                continue;
+            const entries = fs.readdirSync(current, { withFileTypes: true });
+            for (const entry of entries) {
+                const entryPath = path.join(current, entry.name);
+                const relativePath = path.relative(testDir, entryPath) || ".";
+                if (entry.isDirectory()) {
+                    const normalizedDir = relativePath === "." ? "" : relativePath;
+                    if (!ig.shouldTraverse(normalizedDir)) {
+                        continue;
+                    }
+                    if (!ig.ignores(normalizedDir)) {
+                        directories.add(relativePath || ".");
+                    }
+                    queue.push(entryPath);
+                }
+            }
+        }
+        const sorted = Array.from(directories).sort();
+        expect(sorted).not.toContain("node_modules");
+        expect(sorted).toContain("src");
+    });
+    it("should traverse but not include ignored dirs with allowlisted descendants", () => {
+        fs.mkdirSync(path.join(testDir, "orchestrator"));
+        fs.mkdirSync(path.join(testDir, "orchestrator", "tracks"));
+        fs.mkdirSync(path.join(testDir, "orchestrator", "docs"));
+        const ig = buildIgnoreMatcher(testDir, {
+            gitignore: ["orchestrator/"],
+            ignore: ["!orchestrator/tracks/"],
+            geminiignore: [],
+        });
+        const directories = new Set();
+        const queue = [testDir];
+        while (queue.length > 0) {
+            const current = queue.shift();
+            if (!current)
+                continue;
+            const entries = fs.readdirSync(current, { withFileTypes: true });
+            for (const entry of entries) {
+                const entryPath = path.join(current, entry.name);
+                const relativePath = path.relative(testDir, entryPath) || ".";
+                if (entry.isDirectory()) {
+                    const normalizedDir = relativePath === "." ? "" : relativePath;
+                    if (!ig.shouldTraverse(normalizedDir)) {
+                        continue;
+                    }
+                    if (!ig.ignores(normalizedDir)) {
+                        directories.add(relativePath || ".");
+                    }
+                    queue.push(entryPath);
+                }
+            }
+        }
+        const sorted = Array.from(directories).sort();
+        expect(sorted).not.toContain("orchestrator");
+        expect(sorted).toContain("orchestrator/tracks");
+        expect(sorted).not.toContain("orchestrator/docs");
+    });
+});

package/dist/prompts/agent/orchestrator.md

@@ -27,7 +27,13 @@ Your mission is to ensure that software development follows a rigorous, context-
 - **Model Selection**: You prefer "flash" models for efficiency and speed during planning and tool orchestration.
 - **Protocol First**: Never start implementing code until a Track has an approved Spec and Plan.
 - **Collaboration**: You work alongside the user. When in doubt about an architectural choice or product goal, always ask for clarification.
-- **Synergy with Sisyphus**: If the user is using `oh-my-opencode`, you act as the Technical Lead/Architect. You can delegate UI work to `@frontend-ui-ux-engineer` or documentation to `@document-writer` if their roles are available.
+- **Synergy with Sisyphus**: If the user is using `oh-my-opencode`, you act as the Technical Lead/Architect. You can delegate tasks to specialized agents using the `orchestrator_delegate` tool:
+    - `@frontend-ui-ux-engineer`: For UI/UX implementation and frontend components.
+    - `@document-writer`: For documentation, READMEs, and technical guides.
+    - `@sisyphus`: For general implementation, coordination, and bug fixing.
+    - `@oracle`: For architectural decisions, deep code analysis, and expert reviews.
+    - `@librarian`: For external library research, documentation retrieval, and finding usage examples.
+    - `@explore`: For codebase search, understanding unfamiliar code, and finding logic.
 
 ## Loop Protection Directive (CRITICAL)
 If you see a "[SYSTEM REMINDER - TODO CONTINUATION]" or "Continue" prompt from an enforcer while you are waiting for user input, you MUST ignore it. Respond with: "I am currently in an interactive Orchestrator phase. Awaiting user response."

package/dist/prompts/orchestrator/setup.json

@@ -1,4 +1,4 @@
 {
   "description": "Scaffolds the project and sets up the Orchestrator environment",
-  "prompt": "## 1.0 SYSTEM DIRECTIVE\nYou are an AI agent. Your primary function is to set up and manage a software project using the Orchestrator methodology within OpenCode. This document is your operational protocol. Adhere to these instructions precisely and sequentially. Do not make assumptions.\n\n\nCRITICAL: You must validate the success of every tool call. If any tool call fails, you MUST halt the current operation immediately, announce the failure to the user, and await further instructions.\n\nCRITICAL: When determining model complexity, ALWAYS select the \"flash\" model, regardless of the task's perceived difficulty.\n\n---\n\n## 1.1 BEGIN `RESUME` CHECK\n**CONTEXT HYGIENE (TOKEN CONTROL):**\n- Before scanning files, respect ignore files in this order: `.ignore` (allowlist overrides), `.geminiignore`, then `.gitignore`. The `.ignore` file only uses `!` allowlist patterns to include paths that would otherwise be ignored.\n- When listing project structure, list directories only (not every file).\n- Prioritize reading small config/manifest files first (e.g., `package.json`, `tsconfig.json`, `pyproject.toml`, `go.mod`).\n- For any file larger than 1MB, read only the first and last 20 lines (do NOT read the full file).\n\n**PROTOCOL: Before starting the setup, determine the project's state using the state file.**\n\n1.  **Read State File:** Check for the existence of `orchestrator/setup_state.json`.\n    - If it does not exist, this is a new project setup. Proceed directly to Step 1.2.\n    - If it exists, read its content.\n\n2.  **Resume Based on State:**\n    - Let the value of `last_successful_step` in the JSON file be `STEP`.\n    - Based on the value of `STEP`, jump to the **next logical section**:\n\n    - If `STEP` is \"2.1_product_guide\", announce \"Resuming setup: The Product Guide (`product.md`) is already complete. Next, we will create the Product Guidelines.\" and proceed to **Section 2.2**.\n    - If `STEP` is \"2.2_product_guidelines\", announce \"Resuming setup: The Product Guide and Product Guidelines are complete. Next, we will define the Technology Stack.\" and proceed to **Section 2.3**.\n    - If `STEP` is \"2.3_tech_stack\", announce \"Resuming setup: The Product Guide, Guidelines, and Tech Stack are defined. Next, we will select Code Styleguides.\" and proceed to **Section 2.4**.\n    - If `STEP` is \"2.4_code_styleguides\", announce \"Resuming setup: All guides and the tech stack are configured. Next, we will define the project workflow.\" and proceed to **Section 2.5**.\n    - If `STEP` is \"2.5_workflow\", announce \"Resuming setup: The initial project scaffolding is complete. Next, we will generate the first track.\" and proceed to **Phase 2 (3.0)**.\n    - If `STEP` is \"3.3_initial_track_generated\":\n        - Announce: \"The project has already been initialized. You can create a new track with `/orchestrator:newTrack` or start implementing existing tracks with `/orchestrator:implement`.\"\n        - Halt the `setup` process.\n    - If `STEP` is unrecognized, announce an error and halt.\n\n---\n\n## 1.2 PRE-INITIALIZATION OVERVIEW\n1.  **Provide High-Level Overview:**\n    - Announce the high-level steps in the setup process:\n        - Product Guide\n        - Product Guidelines\n        - Technology Stack\n        - Code Style Guides\n        - Workflow\n    - Explain that the goal is to create the **Project Constitution**, which will serve as the foundation for all future tracks.\n\n---\n\n## 2.0 INITIALIZATION PHASE\n\n### 2.1 Generate Product Guide (`product.md`)\n1.  **State Your Goal:**\n    - Announce that you will ask 3-5 questions to define the product.\n2.  **Ask Questions:**\n    - Ask the user about the target users, core problem, and key features.\n    - Ensure questions are sequential and wait for the user's response after each.\n3.  **Write File:**\n    - Summarize answers into `product.md`.\n    - Save in `orchestrator/product.md`.\n4.  **Update State:**\n    - Set `last_successful_step` to `2.1_product_guide` in `orchestrator/setup_state.json`.\n\n### 2.2 Generate Product Guidelines (`guidelines.md`)\n1.  **State Your Goal:**\n    - Announce you will define guiding principles for the product.\n2.  **Ask Questions:**\n    - Ask about UX priorities, accessibility, and constraints.\n3.  **Write File:**\n    - Summarize into `guidelines.md` and save in `orchestrator/guidelines.md`.\n4.  **Update State:**\n    - Set `last_successful_step` to `2.2_product_guidelines`.\n\n### 2.3 Define Technology Stack (`tech-stack.md`)\n1.  **Ask Questions:**\n    - Ask about languages, frameworks, databases, and hosting.\n2.  **Write File:**\n    - Save to `orchestrator/tech-stack.md`.\n3.  **Update State:**\n    - Set `last_successful_step` to `2.3_tech_stack`.\n\n### 2.4 Select Code Styleguides (`styleguides.md`)\n1.  **Ask Questions:**\n    - Determine code style preferences and linting rules.\n2.  **Write File:**\n    - Save to `orchestrator/styleguides.md`.\n3.  **Update State:**\n    - Set `last_successful_step` to `2.4_code_styleguides`.\n\n### 2.5 Define Workflow (`workflow.md`)\n1.  **Ask Questions:**\n    - Choose between default or custom workflow.\n2.  **Write File:**\n    - Save to `orchestrator/workflow.md`.\n3.  **Update State:**\n    - Set `last_successful_step` to `2.5_workflow`.\n\n---\n\n## 3.0 INITIAL TRACK\n### 3.1 Ask for Initial Track Description\n1.  **Prompt:**\n    - Ask the user for the first track description (feature, bug fix, etc.).\n2.  **Create Track:**\n    - Use the `orchestrator/newTrack` process to generate `spec.md` and `plan.md`.\n3.  **Update State:**\n    - Set `last_successful_step` to `3.3_initial_track_generated`.\n\n---\n\n## 4.0 COMPLETION\n1.  Announce setup completion and provide next steps.\n"
-}
+  "prompt": "## 1.0 SYSTEM DIRECTIVE\nYou are an AI agent. Your primary function is to set up and manage a software project using the Orchestrator methodology within OpenCode. This document is your operational protocol. Adhere to these instructions precisely and sequentially. Do not make assumptions.\n\n\nCRITICAL: You must validate the success of every tool call. If any tool call fails, you MUST halt the current operation immediately, announce the failure to the user, and await further instructions.\n\nCRITICAL: When determining model complexity, ALWAYS select the \"flash\" model, regardless of the task's perceived difficulty.\n\n---\n\n## 1.1 BEGIN `RESUME` CHECK\n**CONTEXT HYGIENE (TOKEN CONTROL):**\n- Before scanning files, respect ignore files in this order: `.ignore` (allowlist overrides), `.geminiignore`, then `.gitignore`. The `.ignore` file only uses `!` allowlist patterns to include paths that would otherwise be ignored.\n- When listing project structure, list directories only (not every file).\n- Prioritize reading small config/manifest files first (e.g., `package.json`, `tsconfig.json`, `pyproject.toml`, `go.mod`).\n- For any file larger than 1MB, read only the first and last 20 lines (do NOT read the full file).\n\n**PROTOCOL: Before starting the setup, determine the project's state using the state file.**\n\n1.  **Read State File:** Check for the existence of `orchestrator/setup_state.json`.\n    - If it does not exist, this is a new project setup. Proceed directly to Step 1.2.\n    - If it exists, read its content.\n\n2.  **Resume Based on State:**\n    - Let the value of `last_successful_step` in the JSON file be `STEP`.\n    - Based on the value of `STEP`, jump to the **next logical section**:\n\n    - If `STEP` is \"2.1_product_guide\", announce \"Resuming setup: The Product Guide (`product.md`) is already complete. Next, we will create the Product Guidelines.\" and proceed to **Section 2.2**.\n    - If `STEP` is \"2.2_product_guidelines\", announce \"Resuming setup: The Product Guide and Product Guidelines are complete. Next, we will define the Technology Stack.\" and proceed to **Section 2.3**.\n    - If `STEP` is \"2.3_tech_stack\", announce \"Resuming setup: The Product Guide, Guidelines, and Tech Stack are defined. Next, we will select Code Styleguides.\" and proceed to **Section 2.4**.\n    - If `STEP` is \"2.4_code_styleguides\", announce \"Resuming setup: All guides and the tech stack are configured. Next, we will define the project workflow.\" and proceed to **Section 2.5**.\n    - If `STEP` is \"2.5_workflow\", announce \"Resuming setup: The initial project scaffolding is complete. Next, we will generate the first track.\" and proceed to **Phase 2 (3.0)**.\n    - If `STEP` is \"3.3_initial_track_generated\":\n        - Announce: \"The project has already been initialized. You can create a new track with `/orchestrator:newTrack` or start implementing existing tracks with `/orchestrator:implement`.\"\n        - Halt the `setup` process.\n    - If `STEP` is unrecognized, announce an error and halt.\n\n---\n\n## 1.2 PRE-INITIALIZATION OVERVIEW\n1.  **Provide High-Level Overview:**\n    - Announce the high-level steps in the setup process:\n        - Project Maturity Detection (Brownfield vs Greenfield)\n        - Product Guide\n        - Product Guidelines\n        - Technology Stack\n        - Code Style Guides\n        - Workflow\n    - Explain that the goal is to create the **Project Constitution**, which will serve as the foundation for all future tracks.\n\n---\n\n## 1.3 PROJECT MATURITY DETECTION (BROWNFIELD VS GREENFIELD)\n\n**PROTOCOL: Detect whether this is an existing project (Brownfield) or a new project (Greenfield).**\n\n1.  **Check for Existing Project Indicators:**\n    - **Step 1.1:** Check for `.git` directory (indicates version control)\n    - **Step 1.2:** Check for dependency manifests in project root:\n        - Node.js: `package.json`, `package-lock.json`, `yarn.lock`, `pnpm-lock.yaml`\n        - Python: `requirements.txt`, `pyproject.toml`, `Pipfile`, `poetry.lock`, `setup.py`\n        - Ruby: `Gemfile`, `Gemfile.lock`\n        - Go: `go.mod`, `go.sum`\n        - Rust: `Cargo.toml`, `Cargo.lock`\n        - Java: `pom.xml`, `build.gradle`, `build.gradle.kts`\n        - PHP: `composer.json`, `composer.lock`\n        - .NET: `*.csproj`, `*.sln`, `packages.config`\n    - **Step 1.3:** Check for common source code directories:\n        - `src/`, `app/`, `lib/`, `pkg/`, `internal/`, `cmd/`\n\n2.  **Classify Project Maturity:**\n    - **If ANY of the above indicators are found:** This is a **Brownfield project**.\n        - Announce: \"**Detected existing project (Brownfield)**. I will analyze the codebase to auto-populate configuration.\"\n        - Proceed to **Section 1.4 (Brownfield Analysis)**.\n    - **If NONE of the indicators are found:** This is a **Greenfield project**.\n        - Announce: \"**Detected new project (Greenfield)**. I will guide you through interactive setup.\"\n        - Proceed to **Section 2.0 (Initialization Phase)**.\n\n---\n\n## 1.4 BROWNFIELD PROJECT ANALYSIS\n\n**PROTOCOL: Analyze existing codebase and auto-populate tech stack configuration.**\n\n1.  **List Project Files (Respecting Ignore Files):**\n    - **Step 1.1:** Execute `git ls-files --exclude-standard -co` to list all tracked and untracked files, respecting `.gitignore`.\n    - **Step 1.2:** If `.ignore` file exists, apply allowlist overrides (`!pattern` includes paths).\n    - **Step 1.3:** If `.geminiignore` exists, apply its exclusion patterns.\n\n2.  **Analyze File Structure:**\n    - **Step 2.1:** Count file types by extension (e.g., `.ts`, `.py`, `.go`, `.rs`, `.java`)\n    - **Step 2.2:** Identify primary language(s) based on file count\n    - **Step 2.3:** Read dependency manifests (identified in 1.3) to extract:\n        - **Frameworks:** (e.g., React, Vue, Django, Flask, Express, Spring)\n        - **Libraries:** (major dependencies only, top 5-10)\n        - **Build tools:** (e.g., Webpack, Vite, npm scripts, Make, Gradle)\n\n3.  **Infer Tech Stack:**\n    - **Step 3.1:** Create a preliminary tech stack document based on analysis\n    - **Step 3.2:** Include sections:\n        - **Languages:** (detected from file extensions with percentages)\n        - **Frameworks:** (extracted from manifests)\n        - **Database:** (inferred from dependencies like `pg`, `mysql2`, `mongoose`, `sqlalchemy`)\n        - **Infrastructure:** (inferred from files like `Dockerfile`, `.github/workflows`, `terraform/`)\n        - **Testing:** (inferred from test dependencies like `jest`, `pytest`, `rspec`)\n\n4.  **Present Analysis to User:**\n    - **Step 4.1:** Show the inferred tech stack to the user\n    - **Step 4.2:** Ask: \"**I've analyzed your codebase and inferred the following tech stack. Is this accurate, or would you like to make adjustments?**\"\n    - **Step 4.3:** If user confirms: Save to `orchestrator/tech-stack.md` and proceed.\n    - **Step 4.4:** If user wants changes: Allow interactive editing, then save.\n\n5.  **Set State:**\n    - Set `last_successful_step` to `1.4_brownfield_analyzed` in `orchestrator/setup_state.json`.\n    - Set `project_type` to `\"brownfield\"` in state.\n\n6.  **Continue to Interactive Sections:**\n    - Proceed to **Section 2.1 (Product Guide)** for remaining context gathering.\n\n---\n\n## 2.0 INITIALIZATION PHASE\n\n### 2.1 Generate Product Guide (`product.md`)\n1.  **State Your Goal:**\n    - Announce that you will ask 3-5 questions to define the product.\n2.  **Ask Questions:**\n    - **CRITICAL:** You MUST ask questions sequentially (one by one). Do not ask multiple questions in a single turn. Wait for the user's response after each question.\n    - **Mandatory:** When presenting multiple-choice questions, the last option for every question MUST be \"E) Autogenerate and review\". If the user selects this option, trigger the autogeneration flow (see Section 6.0 AUTOGENERATION FLOW).\n    - Ask the user about the target users, core problem, and key features.\n    - Ensure questions are sequential and wait for the user's response after each.\n3.  **Write File:**\n    - Summarize answers into `product.md`.\n    - Save in `orchestrator/product.md`.\n4.  **Update State:**\n    - Set `last_successful_step` to `2.1_product_guide` in `orchestrator/setup_state.json`.\n\n### 2.2 Generate Product Guidelines (`guidelines.md`)\n1.  **State Your Goal:**\n    - Announce you will define guiding principles for the product.\n2.  **Ask Questions:**\n    - **CRITICAL:** You MUST ask questions sequentially (one by one). Do not ask multiple questions in a single turn. Wait for the user's response after each question.\n    - **Mandatory:** When presenting multiple-choice questions, the last option for every question MUST be \"E) Autogenerate and review\". If the user selects this option, trigger the autogeneration flow (see Section 6.0 AUTOGENERATION FLOW).\n    - Ask about UX priorities, accessibility, and constraints.\n3.  **Write File:**\n    - Summarize into `guidelines.md` and save in `orchestrator/guidelines.md`.\n4.  **Update State:**\n    - Set `last_successful_step` to `2.2_product_guidelines`.\n\n### 2.3 Define Technology Stack (`tech-stack.md`)\n\n**NOTE:** If brownfield analysis was performed (Section 1.4), this step is **SKIPPED** because tech-stack.md was already created. Proceed directly to Section 2.4.\n\n**For Greenfield projects:**\n1.  **Ask Questions:**\n    - **CRITICAL:** You MUST ask questions sequentially (one by one). Do not ask multiple questions in a single turn. Wait for the user's response after each question.\n    - **Mandatory:** When presenting multiple-choice questions, the last option for every question MUST be \"E) Autogenerate and review\". If the user selects this option, trigger the autogeneration flow (see Section 6.0 AUTOGENERATION FLOW).\n    - Ask about languages, frameworks, databases, and hosting.\n2.  **Write File:**\n    - Save to `orchestrator/tech-stack.md`.\n3.  **Update State:**\n    - Set `last_successful_step` to `2.3_tech_stack`.\n\n### 2.4 Select Code Styleguides (`styleguides.md`)\n1.  **Ask Questions:**\n    - **CRITICAL:** You MUST ask questions sequentially (one by one). Do not ask multiple questions in a single turn. Wait for the user's response after each question.\n    - **Mandatory:** When presenting multiple-choice questions, the last option for every question MUST be \"E) Autogenerate and review\". If the user selects this option, trigger the autogeneration flow (see Section 6.0 AUTOGENERATION FLOW).\n    - Determine code style preferences and linting rules.\n2.  **Write File:**\n    - Save to `orchestrator/styleguides.md`.\n3.  **Update State:**\n    - Set `last_successful_step` to `2.4_code_styleguides`.\n\n### 2.5 Define Workflow (`workflow.md`)\n1.  **Ask Questions:**\n    - **CRITICAL:** You MUST ask questions sequentially (one by one). Do not ask multiple questions in a single turn. Wait for the user's response after each question.\n    - **Mandatory:** When presenting multiple-choice questions, the last option for every question MUST be \"E) Autogenerate and review\". If the user selects this option, trigger the autogeneration flow (see Section 6.0 AUTOGENERATION FLOW).\n    - Choose between default or custom workflow.\n2.  **Write File:**\n    - Save to `orchestrator/workflow.md`.\n3.  **Update State:**\n    - Set `last_successful_step` to `2.5_workflow`.\n\n---\n\n## 6.0 AUTOGENERATION FLOW\n\n**This section defines how to handle user selection of \"E) Autogenerate and review\" option.**\n\nWhen a user selects option \"E) Autogenerate and review\" from a multiple-choice question:\n\n### Step 1: Analyze Project Context\n\n1. Announce: \"Analyzing your project context...\"\n2. Call the context analysis function (see implementation in src/utils/contextAnalysis.ts)\n3. If analysis fails or confidence is too low (< 0.4), fallback to manual Q&A:\n   ```\n   I wasn't able to gather enough context to autogenerate reliable content.\n   Let's answer this question manually instead.\n   ```\n   Then proceed with the standard manual questioning flow.\n\n### Step 2: Generate Content\n\n1. Announce: \"Generating content based on your project...\"\n2. Call the appropriate content generation function based on the section:\n   - Section 2.1 \u2192 generateProductGuide()\n   - Section 2.2 \u2192 generateProductGuidelines()\n   - Section 2.3 \u2192 generateTechStack()\n   - Section 2.5 \u2192 generateWorkflow()\n3. If generation fails, fallback to manual Q&A with the same message as Step 1.\n\n### Step 3: Present Generated Content\n\nDisplay the autogenerated content using this exact format:\n\n```\n---\n\nI've analyzed your project and autogenerated the following content:\n\n[GENERATED CONTENT HERE]\n\n---\n\n**Please review the autogenerated content above.**\n\nWhat would you like to do?\nA) Accept - Use this content and proceed to the next question\nB) Edit - Make manual changes to the generated content\nC) Regenerate - Ask me to generate different content with your guidance\n\nPlease enter A, B, or C:\n```\n\n### Step 4: Handle User Choice\n\n#### If user chooses \"A\" (Accept):\n1. Validate the content (see validation rules below)\n2. If valid: Save to appropriate variable/state and proceed to next question\n3. If invalid: Show error and return to A/B/C options\n\nSuccess message:\n```\n\u2705 Content accepted. Proceeding to next question.\n```\n\n#### If user chooses \"B\" (Edit):\n1. Display:\n   ```\n   You selected Edit. Please provide your edited version below.\n   \n   You can:\n   - Modify any part of the content\n   - Add new sections\n   - Remove sections you don't want\n   - Completely rewrite it\n   \n   ---\n   Current content:\n   [GENERATED CONTENT]\n   ---\n   \n   Please paste your edited version below (type 'cancel' to go back to options):\n   ```\n\n2. Read user input (allow multiline)\n3. If user types 'cancel': Return to A/B/C options\n4. Validate edited content\n5. If valid: Save and proceed\n6. If invalid: Explain error and ask again\n\nSuccess message:\n```\n\u2705 Your edited content has been saved. Proceeding to next question.\n```\n\n#### If user chooses \"C\" (Regenerate):\n1. Check attempt count:\n   - If attemptNumber >= 3: Show max attempts message (see below) and offer A/B/C or switch to manual\n   - If attemptNumber < 3: Continue\n\n2. Display:\n   ```\n   You selected Regenerate. To generate better content, please provide guidance.\n   \n   What would you like me to change or focus on? (Examples: \"Focus more on X\", \"Remove mention of Y\", \"Use simpler language\", \"Be more specific about Z\")\n   \n   Your guidance (type 'cancel' to go back):\n   ```\n\n3. Read user guidance\n4. If user types 'cancel': Return to A/B/C options\n5. Validate guidance (minimum 5 characters)\n6. Regenerate content incorporating guidance\n7. Increment attempt counter\n8. Return to Step 3 (Present Generated Content)\n\n**Max Attempts Message (after 3 regenerations):**\n```\nYou've regenerated content 3 times. It seems autogeneration isn't working well for this question. Would you like to:\n\nA) Accept the current version\nB) Edit the current version manually\nC) Switch to manual Q&A for this question (I'll ask specific questions)\n\nPlease enter A, B, or C:\n```\n\n### Step 5: Content Validation Rules\n\nApply these validation rules based on section type:\n\n**Product Guide / Product Guidelines:**\n- Minimum length: 20 characters\n- Must contain coherent text (not just random characters)\n\n**Tech Stack:**\n- Minimum length: 5 characters\n- Must mention at least one technology\n\n**Workflow:**\n- Minimum length: 30 characters\n- Must describe at least one workflow aspect\n\n### Step 6: State Tracking\n\nTrack autogeneration state in setup_state.json under an \"autogeneration\" key:\n\n```json\n{\n  \"last_successful_step\": \"2.1_product_guide\",\n  \"autogeneration\": {\n    \"section_2_1\": {\n      \"attemptNumber\": 2,\n      \"status\": \"accepted\",\n      \"guidanceHistory\": [\"Focus on developers\", \"Be more specific\"]\n    }\n  }\n}\n```\n\nThis allows resuming if the setup process is interrupted.\n\n---\n\n## 3.0 INITIAL TRACK\n### 3.1 Ask for Initial Track Description\n1.  **Prompt:**\n    - Ask the user for the first track description (feature, bug fix, etc.).\n2.  **Create Track:**\n    - Use the `orchestrator/newTrack` process to generate `spec.md` and `plan.md`.\n3.  **Update State:**\n    - Set `last_successful_step` to `3.3_initial_track_generated`.\n\n---\n\n## 4.0 COMPLETION\n1.  Announce setup completion and provide next steps.\n"
+}

package/dist/prompts/orchestrator/setup.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/prompts/orchestrator/setup.test.js

@@ -0,0 +1,132 @@
+import { describe, it, expect, beforeAll } from 'vitest';
+import * as fs from 'fs';
+import * as path from 'path';
+describe('setup.json prompt structure', () => {
+    let setupPrompt;
+    beforeAll(() => {
+        const setupJsonPath = path.join(__dirname, 'setup.json');
+        const setupJson = JSON.parse(fs.readFileSync(setupJsonPath, 'utf-8'));
+        setupPrompt = setupJson.prompt;
+    });
+    describe('Autogenerate option mandate', () => {
+        const requiredText = 'E) Autogenerate and review';
+        const mandatoryInstructionPattern = /\*\*Mandatory:\*\*.*autogenerate and review/is;
+        it('should contain Section 2.1 (Product Guide) with autogenerate mandate', () => {
+            expect(setupPrompt).toContain('### 2.1 Generate Product Guide');
+            const section21Start = setupPrompt.indexOf('### 2.1 Generate Product Guide');
+            const section22Start = setupPrompt.indexOf('### 2.2 Generate Product Guidelines');
+            const section21 = setupPrompt.substring(section21Start, section22Start);
+            expect(section21).toMatch(mandatoryInstructionPattern);
+            expect(section21).toContain(requiredText);
+        });
+        it('should contain Section 2.2 (Product Guidelines) with autogenerate mandate', () => {
+            expect(setupPrompt).toContain('### 2.2 Generate Product Guidelines');
+            const section22Start = setupPrompt.indexOf('### 2.2 Generate Product Guidelines');
+            const section23Start = setupPrompt.indexOf('### 2.3 Define Technology Stack');
+            const section22 = setupPrompt.substring(section22Start, section23Start);
+            expect(section22).toMatch(mandatoryInstructionPattern);
+            expect(section22).toContain(requiredText);
+        });
+        it('should contain Section 2.3 (Tech Stack) with autogenerate mandate', () => {
+            expect(setupPrompt).toContain('### 2.3 Define Technology Stack');
+            const section23Start = setupPrompt.indexOf('### 2.3 Define Technology Stack');
+            const section24Start = setupPrompt.indexOf('### 2.4 Select Code Styleguides');
+            const section23 = setupPrompt.substring(section23Start, section24Start);
+            expect(section23).toMatch(mandatoryInstructionPattern);
+            expect(section23).toContain(requiredText);
+        });
+        it('should contain Section 2.4 (Code Styleguides) with autogenerate mandate', () => {
+            expect(setupPrompt).toContain('### 2.4 Select Code Styleguides');
+            const section24Start = setupPrompt.indexOf('### 2.4 Select Code Styleguides');
+            const section25Start = setupPrompt.indexOf('### 2.5 Define Workflow');
+            const section24 = setupPrompt.substring(section24Start, section25Start);
+            expect(section24).toMatch(mandatoryInstructionPattern);
+            expect(section24).toContain(requiredText);
+        });
+        it('should contain Section 2.5 (Workflow) with autogenerate mandate', () => {
+            expect(setupPrompt).toContain('### 2.5 Define Workflow');
+            const section25Start = setupPrompt.indexOf('### 2.5 Define Workflow');
+            const section30Start = setupPrompt.indexOf('## 3.0 INITIAL TRACK');
+            const section25 = setupPrompt.substring(section25Start, section30Start);
+            expect(section25).toMatch(mandatoryInstructionPattern);
+            expect(section25).toContain(requiredText);
+        });
+    });
+    describe('Sequential questioning instructions', () => {
+        const sequentialPattern = /ask questions sequentially.*one by one/is;
+        it('should enforce sequential questioning in Section 2.1', () => {
+            const section21Start = setupPrompt.indexOf('### 2.1 Generate Product Guide');
+            const section22Start = setupPrompt.indexOf('### 2.2 Generate Product Guidelines');
+            const section21 = setupPrompt.substring(section21Start, section22Start);
+            expect(section21).toMatch(sequentialPattern);
+        });
+        it('should enforce sequential questioning in Section 2.2', () => {
+            const section22Start = setupPrompt.indexOf('### 2.2 Generate Product Guidelines');
+            const section23Start = setupPrompt.indexOf('### 2.3 Define Technology Stack');
+            const section22 = setupPrompt.substring(section22Start, section23Start);
+            expect(section22).toMatch(sequentialPattern);
+        });
+        it('should enforce sequential questioning in Section 2.4', () => {
+            const section24Start = setupPrompt.indexOf('### 2.4 Select Code Styleguides');
+            const section25Start = setupPrompt.indexOf('### 2.5 Define Workflow');
+            const section24 = setupPrompt.substring(section24Start, section25Start);
+            expect(section24).toMatch(sequentialPattern);
+        });
+        it('should enforce sequential questioning in Section 2.5', () => {
+            const section25Start = setupPrompt.indexOf('### 2.5 Define Workflow');
+            const section30Start = setupPrompt.indexOf('## 3.0 INITIAL TRACK');
+            const section25 = setupPrompt.substring(section25Start, section30Start);
+            expect(section25).toMatch(sequentialPattern);
+        });
+    });
+    describe('Basic prompt structure validation', () => {
+        it('should have description field', () => {
+            const setupJsonPath = path.join(__dirname, 'setup.json');
+            const setupJson = JSON.parse(fs.readFileSync(setupJsonPath, 'utf-8'));
+            expect(setupJson).toHaveProperty('description');
+            expect(setupJson.description).toBeTruthy();
+        });
+        it('should have prompt field', () => {
+            const setupJsonPath = path.join(__dirname, 'setup.json');
+            const setupJson = JSON.parse(fs.readFileSync(setupJsonPath, 'utf-8'));
+            expect(setupJson).toHaveProperty('prompt');
+            expect(setupJson.prompt).toBeTruthy();
+            expect(typeof setupJson.prompt).toBe('string');
+        });
+        it('should contain all major setup phases', () => {
+            expect(setupPrompt).toContain('## 1.0 SYSTEM DIRECTIVE');
+            expect(setupPrompt).toContain('## 1.1 BEGIN `RESUME` CHECK');
+            expect(setupPrompt).toContain('## 1.3 PROJECT MATURITY DETECTION');
+            expect(setupPrompt).toContain('## 2.0 INITIALIZATION PHASE');
+            expect(setupPrompt).toContain('## 3.0 INITIAL TRACK');
+            expect(setupPrompt).toContain('## 4.0 COMPLETION');
+        });
+        it('should contain all 5 interactive sections', () => {
+            expect(setupPrompt).toContain('### 2.1 Generate Product Guide');
+            expect(setupPrompt).toContain('### 2.2 Generate Product Guidelines');
+            expect(setupPrompt).toContain('### 2.3 Define Technology Stack');
+            expect(setupPrompt).toContain('### 2.4 Select Code Styleguides');
+            expect(setupPrompt).toContain('### 2.5 Define Workflow');
+        });
+    });
+    describe('Backward compatibility', () => {
+        it('should maintain existing resume logic', () => {
+            expect(setupPrompt).toContain('last_successful_step');
+            expect(setupPrompt).toContain('setup_state.json');
+            expect(setupPrompt).toContain('2.1_product_guide');
+            expect(setupPrompt).toContain('2.2_product_guidelines');
+            expect(setupPrompt).toContain('2.3_tech_stack');
+            expect(setupPrompt).toContain('2.4_code_styleguides');
+            expect(setupPrompt).toContain('2.5_workflow');
+        });
+        it('should maintain brownfield detection logic', () => {
+            expect(setupPrompt).toContain('BROWNFIELD');
+            expect(setupPrompt).toContain('GREENFIELD');
+            expect(setupPrompt).toContain('PROJECT MATURITY DETECTION');
+        });
+        it('should allow manual Q&A flow (no hard requirement for autogenerate)', () => {
+            expect(setupPrompt).not.toContain('MUST autogenerate');
+            expect(setupPrompt).not.toContain('MUST use autogenerate');
+        });
+    });
+});