maestro-flow 0.1.0

package/dist/utils/path-validator.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"path-validator.js","sourceRoot":"","sources":["../../src/utils/path-validator.ts"],"names":[],"mappings":"AAAA;;;;;GAKG;AAEH,OAAO,EAAE,OAAO,EAAE,UAAU,EAAE,SAAS,EAAY,GAAG,EAAE,MAAM,MAAM,CAAC;AACrE,OAAO,EAAE,QAAQ,EAAU,MAAM,aAAa,CAAC;AAG/C,qCAAqC;AACrC,MAAM,gBAAgB,GAAG,sBAAsB,CAAC;AAChD,MAAM,gBAAgB,GAAG,sBAAsB,CAAC;AAChD,MAAM,kBAAkB,GAAG,wBAAwB,CAAC;AAEpD;;;GAGG;AACH,MAAM,UAAU,gBAAgB;IAC9B,MAAM,KAAK,GAAG,OAAO,CAAC,GAAG,CAAC,kBAAkB,CAAC,CAAC;IAC9C,OAAO,KAAK,KAAK,GAAG,IAAI,KAAK,EAAE,WAAW,EAAE,KAAK,MAAM,CAAC;AAC1D,CAAC;AAED;;;GAGG;AACH,MAAM,UAAU,cAAc;IAC5B,OAAO,OAAO,CAAC,GAAG,CAAC,gBAAgB,CAAC,IAAI,OAAO,CAAC,GAAG,EAAE,CAAC;AACxD,CAAC;AAED;;;GAGG;AACH,MAAM,UAAU,qBAAqB;IACnC,MAAM,OAAO,GAAG,OAAO,CAAC,GAAG,CAAC,gBAAgB,CAAC,CAAC;IAC9C,IAAI,OAAO,EAAE,CAAC;QACZ,OAAO,OAAO,CAAC,KAAK,CAAC,GAAG,CAAC,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,IAAI,EAAE,CAAC,CAAC,MAAM,CAAC,OAAO,CAAC,CAAC;IAC/D,CAAC;IACD,OAAO,CAAC,cAAc,EAAE,CAAC,CAAC;AAC5B,CAAC;AAED;;GAEG;AACH,MAAM,UAAU,aAAa,CAAC,CAAS;IACrC,OAAO,SAAS,CAAC,CAAC,CAAC,CAAC,OAAO,CAAC,KAAK,EAAE,GAAG,CAAC,CAAC;AAC1C,CAAC;AAED,SAAS,yBAAyB,CAAC,CAAS;IAC1C,MAAM,IAAI,GAAG,cAAc,EAAE,CAAC;IAC9B,MAAM,QAAQ,GAAG,UAAU,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,CAAC,OAAO,CAAC,IAAI,EAAE,CAAC,CAAC,CAAC;IACtD,IAAI,SAAS,GAAG,SAAS,CAAC,QAAQ,CAAC,CAAC;IAEpC,4EAA4E;IAC5E,SAAS,GAAG,SAAS,CAAC,OAAO,CAAC,SAAS,EAAE,EAAE,CAAC,CAAC;IAC7C,IAAI,aAAa,CAAC,IAAI,CAAC,SAAS,CAAC,EAAE,CAAC;QAClC,SAAS,IAAI,GAAG,CAAC;IACnB,CAAC;SAAM,IAAI,SAAS,KAAK,EAAE,EAAE,CAAC;QAC5B,SAAS,GAAG,GAAG,CAAC;IAClB,CAAC;IAED,sCAAsC;IACtC,IAAI,OAAO,CAAC,QAAQ,KAAK,OAAO,EAAE,CAAC;QACjC,SAAS,GAAG,SAAS,CAAC,WAAW,EAAE,CAAC;IACtC,CAAC;IAED,OAAO,SAAS,CAAC;AACnB,CAAC;AAED;;GAEG;AACH,MAAM,UAAU,8BAA8B,CAC5C,UAAkB,EAClB,kBAA4B;IAE5B,MAAM,eAAe,GAAG,yBAAyB,CAAC,UAAU,CAAC,CAAC;IAC9D,OAAO,kBAAkB,CAAC,IAAI,CAAC,GAAG,CAAC,EAAE;QACnC,MAAM,YAAY,GAAG,yBAAyB,CAAC,GAAG,CAAC,CAAC;QACpD,IAAI,eAAe,KAAK,YAAY;YAAE,OAAO,IAAI,CAAC;QAElD,MAAM,QAAQ,GAAG,YAAY,CAAC,QAAQ,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,YAAY,CAAC,CAAC,CAAC,YAAY,GAAG,GAAG,CAAC;QAChF,OAAO,eAAe,CAAC,UAAU,CAAC,QAAQ,CAAC,CAAC;IAC9C,CAAC,CAAC,CAAC;AACL,CAAC;AAED;;;;;;;;;;;;GAYG;AACH,MAAM,CAAC,KAAK,UAAU,YAAY,CAChC,QAAgB,EAChB,UAGI,EAAE;IAEN,MAAM,cAAc,GAAG,gBAAgB,EAAE,CAAC;IAC1C,MAAM,WAAW,GAAG,OAAO,CAAC,kBAAkB,IAAI,qBAAqB,EAAE,CAAC;IAE1E,8BAA8B;IAC9B,MAAM,YAAY,GAAG,UAAU,CAAC,QAAQ,CAAC;QACvC,CAAC,CAAC,QAAQ;QACV,CAAC,CAAC,OAAO,CAAC,cAAc,EAAE,EAAE,QAAQ,CAAC,CAAC;IACxC,MAAM,cAAc,GAAG,aAAa,CAAC,YAAY,CAAC,CAAC;IAEnD,wDAAwD;IACxD,IAAI,cAAc,IAAI,CAAC,8BAA8B,CAAC,cAAc,EAAE,WAAW,CAAC,EAAE,CAAC;QACnF,MAAM,IAAI,KAAK,CACb,wBAAwB,cAAc,oCAAoC;YAC1E,aAAa,WAAW,CAAC,IAAI,CAAC,IAAI,CAAC,GAAG,CACvC,CAAC;IACJ,CAAC;IAED,2CAA2C;IAC3C,IAAI,CAAC;QACH,MAAM,QAAQ,GAAG,MAAM,QAAQ,CAAC,YAAY,CAAC,CAAC;QAC9C,MAAM,cAAc,GAAG,aAAa,CAAC,QAAQ,CAAC,CAAC;QAE/C,kDAAkD;QAClD,IAAI,cAAc,IAAI,CAAC,8BAA8B,CAAC,cAAc,EAAE,WAAW,CAAC,EAAE,CAAC;YACnF,MAAM,IAAI,KAAK,CACb,kCAAkC,cAAc,kCAAkC,CACnF,CAAC;QACJ,CAAC;QAED,OAAO,cAAc,CAAC;IACxB,CAAC;IAAC,OAAO,KAAU,EAAE,CAAC;QACpB,iDAAiD;QACjD,IAAI,KAAK,CAAC,IAAI,KAAK,QAAQ,EAAE,CAAC;YAC5B,IAAI,OAAO,CAAC,SAAS,EAAE,CAAC;gBACtB,MAAM,IAAI,KAAK,CAAC,mBAAmB,YAAY,EAAE,CAAC,CAAC;YACrD,CAAC;YAED,qEAAqE;YACrE,MAAM,SAAS,GAAG,OAAO,CAAC,YAAY,EAAE,IAAI,CAAC,CAAC;YAC9C,IAAI,CAAC;gBACH,MAAM,UAAU,GAAG,MAAM,QAAQ,CAAC,SAAS,CAAC,CAAC;gBAC7C,MAAM,gBAAgB,GAAG,aAAa,CAAC,UAAU,CAAC,CAAC;gBAEnD,IAAI,cAAc,IAAI,CAAC,8BAA8B,CAAC,gBAAgB,EAAE,WAAW,CAAC,EAAE,CAAC;oBACrF,MAAM,IAAI,KAAK,CACb,oCAAoC,gBAAgB,kCAAkC,CACvF,CAAC;gBACJ,CAAC;YACH,CAAC;YAAC,OAAO,WAAgB,EAAE,CAAC;gBAC1B,IAAI,WAAW,CAAC,IAAI,KAAK,QAAQ,EAAE,CAAC;oBAClC,wEAAwE;oBACxE,qCAAqC;oBACrC,OAAO,YAAY,CAAC;gBACtB,CAAC;gBACD,MAAM,WAAW,CAAC;YACpB,CAAC;YAED,OAAO,YAAY,CAAC;QACtB,CAAC;QAED,gCAAgC;QAChC,IAAI,KAAK,CAAC,OAAO,EAAE,QAAQ,CAAC,eAAe,CAAC,EAAE,CAAC;YAC7C,MAAM,KAAK,CAAC;QACd,CAAC;QACD,MAAM,KAAK,CAAC;IACd,CAAC;AACH,CAAC;AAED;;;GAGG;AACH,MAAM,UAAU,kBAAkB,CAAC,GAAG,YAAsB;IAC1D,OAAO,OAAO,CAAC,cAAc,EAAE,EAAE,GAAG,YAAY,CAAC,CAAC;AACpD,CAAC"}

package/package.json

@@ -0,0 +1,56 @@
+{
+  "name": "maestro-flow",
+  "version": "0.1.0",
+  "description": "Workflow orchestration CLI with MCP endpoint support and extensible architecture",
+  "type": "module",
+  "bin": {
+    "maestro": "bin/maestro.js",
+    "maestro-statusline": "bin/maestro-statusline.js",
+    "maestro-context-monitor": "bin/maestro-context-monitor.js"
+  },
+  "main": "dist/index.js",
+  "types": "dist/index.d.ts",
+  "files": [
+    "bin",
+    "dist",
+    "templates",
+    "workflows",
+    "chains",
+    ".claude/commands",
+    ".claude/agents",
+    ".claude/skills",
+    ".claude/CLAUDE.md",
+    ".codex/skills",
+    "dashboard/dist",
+    "dashboard/dist-server",
+    "dashboard/package.json"
+  ],
+  "scripts": {
+    "build": "tsc",
+    "dev": "tsc --watch",
+    "start": "node bin/maestro.js",
+    "mcp": "node bin/maestro-mcp.js",
+    "lint": "tsc --noEmit",
+    "clean": "rm -rf dist",
+    "prepublishOnly": "npm run build"
+  },
+  "engines": {
+    "node": ">=18.0.0"
+  },
+  "dependencies": {
+    "@hono/node-server": "^1.14.0",
+    "@inquirer/prompts": "^8.3.2",
+    "@modelcontextprotocol/sdk": "^1.12.1",
+    "chokidar": "^4.0.0",
+    "commander": "^13.1.0",
+    "hono": "^4.7.0",
+    "ws": "^8.19.0",
+    "zod": "^3.25.76"
+  },
+  "devDependencies": {
+    "@types/node": "^22.10.0",
+    "@types/ws": "^8.18.1",
+    "typescript": "^5.7.0"
+  },
+  "license": "MIT"
+}

package/templates/cli/prompts/analysis-analyze-code-patterns.txt

@@ -0,0 +1,37 @@
+Analyze implementation patterns and code structure.
+
+## Planning Required
+Before providing analysis, you MUST:
+1. Review all files in context (not just samples)
+2. Identify patterns with file:line references
+3. Distinguish good patterns from anti-patterns
+4. Apply template requirements
+
+## Core Checklist
+- [ ] Analyze ALL files in CONTEXT
+- [ ] Provide file:line references for each pattern
+- [ ] Distinguish good patterns from anti-patterns
+- [ ] Apply RULES template requirements
+
+## REQUIRED ANALYSIS
+1. Identify common code patterns and architectural decisions
+2. Extract reusable utilities and shared components
+3. Document existing conventions and coding standards
+4. Assess pattern consistency and identify anti-patterns
+5. Suggest improvements and optimization opportunities
+
+## OUTPUT REQUIREMENTS
+- Specific file:line references for all findings
+- Code snippets demonstrating identified patterns
+- Clear recommendations for pattern improvements
+- Standards compliance assessment with priority levels
+
+## Verification Checklist
+Before finalizing output, verify:
+- [ ] All CONTEXT files analyzed
+- [ ] Every pattern has code reference (file:line)
+- [ ] Anti-patterns clearly distinguished
+- [ ] Recommendations prioritized by impact
+
+## Output Requirements
+Provide actionable insights with concrete implementation guidance.

package/templates/cli/prompts/analysis-analyze-performance.txt

@@ -0,0 +1,29 @@
+Analyze performance characteristics and optimization opportunities.
+
+## CORE CHECKLIST ⚡
+□ Focus on measurable metrics (e.g., latency, memory, CPU usage)
+□ Provide file:line references for all identified bottlenecks
+□ Distinguish between algorithmic and resource-based issues
+□ Apply RULES template requirements exactly as specified
+
+## REQUIRED ANALYSIS
+1. Identify performance bottlenecks and resource usage patterns
+2. Assess algorithm efficiency and data structure choices
+3. Evaluate caching strategies and optimization techniques
+4. Review memory management and resource cleanup
+5. Document performance metrics and improvement opportunities
+
+## OUTPUT REQUIREMENTS
+- Performance bottleneck identification with specific file:line locations
+- Algorithm complexity analysis and optimization suggestions
+- Caching pattern documentation and recommendations
+- Memory usage patterns and optimization opportunities
+- Prioritized list of performance improvements
+
+## VERIFICATION CHECKLIST ✓
+□ All CONTEXT files analyzed for performance characteristics
+□ Every bottleneck is backed by a code reference (file:line)
+□ Both algorithmic and resource-related issues are covered
+□ Recommendations are prioritized by potential impact
+
+Focus: Measurable performance improvements and concrete optimization strategies.

package/templates/cli/prompts/analysis-analyze-technical-document.txt

@@ -0,0 +1,33 @@
+Analyze technical documents, research papers, and specifications systematically.
+
+## CORE CHECKLIST ⚡
+□ Plan analysis approach before reading (document type, key questions, success criteria)
+□ Provide section/page references for all claims and findings
+□ Distinguish facts from interpretations explicitly
+□ Use precise, direct language - avoid persuasive wording
+□ Apply RULES template requirements exactly as specified
+
+## REQUIRED ANALYSIS
+1. Document assessment: type, structure, audience, quality indicators
+2. Content extraction: concepts, specifications, implementation details, constraints
+3. Critical evaluation: strengths, gaps, ambiguities, clarity issues
+4. Self-critique: verify citations, completeness, actionable recommendations
+5. Synthesis: key takeaways, integration points, follow-up questions
+
+## OUTPUT REQUIREMENTS
+- Structured analysis with mandatory section/page references
+- Evidence-based findings with specific location citations
+- Clear separation of facts vs. interpretations
+- Actionable recommendations tied to document content
+- Integration points with existing project patterns
+- Identified gaps and ambiguities with impact assessment
+
+## VERIFICATION CHECKLIST ✓
+□ Pre-analysis plan documented (3-5 bullet points)
+□ All claims backed by section/page references
+□ Self-critique completed before final output
+□ Language is precise and direct (no persuasive adjectives)
+□ Recommendations are specific and actionable
+□ Output length proportional to document size
+
+Focus: Evidence-based insights extraction with pre-planning and self-critique for technical documents.

package/templates/cli/prompts/analysis-assess-security-risks.txt

@@ -0,0 +1,29 @@
+Analyze security implementation and potential vulnerabilities.
+
+## CORE CHECKLIST ⚡
+□ Identify all data entry points and external system interfaces
+□ Provide file:line references for all potential vulnerabilities
+□ Classify risks by severity and type (e.g., OWASP Top 10)
+□ Apply RULES template requirements exactly as specified
+
+## REQUIRED ANALYSIS
+1. Identify authentication and authorization mechanisms
+2. Assess input validation and sanitization practices
+3. Review data encryption and secure storage methods
+4. Evaluate API security and access control patterns
+5. Document security risks and compliance considerations
+
+## OUTPUT REQUIREMENTS
+- Security vulnerability findings with file:line references
+- Authentication/authorization pattern documentation
+- Input validation examples and identified gaps
+- Encryption usage patterns and recommendations
+- Prioritized remediation plan based on risk level
+
+## VERIFICATION CHECKLIST ✓
+□ All CONTEXT files analyzed for security vulnerabilities
+□ Every finding is backed by a code reference (file:line)
+□ Both authentication and data handling are covered
+□ Recommendations include clear, actionable remediation steps
+
+Focus: Identifying security gaps and providing actionable remediation steps.

package/templates/cli/prompts/analysis-diagnose-bug-root-cause.txt

@@ -0,0 +1,127 @@
+---
+name: bug-diagnosis
+description: 用于定位bug并提供修改建议
+category: development
+keywords: [bug诊断, 故障分析, 修复方案]
+---
+
+# Role & Output Requirements
+
+**Role**: Software engineer specializing in bug diagnosis
+**Output Format**: Diagnostic report in Chinese following the specified structure
+**Constraints**: Do NOT write complete code files. Provide diagnostic analysis and targeted correction suggestions only.
+
+## Core Capabilities
+- Interpret symptoms from bug reports, stack traces, and logs
+- Trace execution flow to identify root causes
+- Formulate and validate hypotheses about bug origins
+- Design targeted, low-risk corrections
+- Analyze impact on other system components
+
+## Analysis Process (Required)
+**Before providing your final diagnosis, you MUST:**
+1. Analyze symptoms and form initial hypothesis
+2. Trace code execution to identify root cause
+3. Design correction strategy
+4. Assess potential impacts and risks
+5. Present structured diagnostic report
+
+## Objectives
+1. Identify root cause (not just symptoms)
+2. Propose targeted correction with justification
+3. Assess risks and side effects
+4. Provide verification steps
+
+## Input
+- Bug description (observed vs. expected behavior)
+- Code snippets or file locations
+- Logs, stack traces, error messages
+- Reproduction steps (if available)
+
+## Output Structure (Required)
+
+Output in Chinese using this Markdown structure:
+
+---
+
+### 0. 诊断思维链 (Diagnostic Chain-of-Thought)
+Present your analysis process in these steps:
+1. **症状分析**: Summarize error symptoms and technical clues
+2. **初步假设**: Identify suspicious code areas and form initial hypothesis
+3. **根本原因定位**: Trace execution path to pinpoint exact cause
+4. **修复方案设计**: Design targeted, low-risk correction
+5. **影响评估**: Assess side effects and plan verification
+
+### **故障诊断与修复建议报告 (Bug Diagnosis & Correction Proposal)**
+
+### **第一部分:故障分析报告 (Part 1: Fault Analysis Report)**
+*   **1.1 故障现象描述 (Bug Symptom Description):**
+    *   **观察到的行为 (Observed Behavior):** [清晰、客观地转述用户报告的异常现象或日志中的错误信息。]
+    *   **预期的行为 (Expected Behavior):** [描述在正常情况下,系统或功能应有的表现。]
+*   **1.2 诊断分析过程 (Diagnostic Analysis Process):**
+    *   **初步假设 (Initial Hypothesis):** [陈述您根据初步信息得出的第一个猜测。例如:初步判断,问题可能出在数据解析环节,因为错误日志显示了格式不匹配。]
+    *   **根本原因分析 (Root Cause Analysis - RCA):** [**这是报告的核心。** 详细阐述您的逻辑推理过程,说明您是如何从表象追踪到根源的。例如:通过检查 `data_parser.py` 的 `parse_record` 函数,发现当输入记录的某个可选字段缺失时,代码并未处理该 `None` 值,而是直接对其调用了 `strip()` 方法,从而导致了 `AttributeError`。因此,**根本原因**是:**对可能为 None 的变量在未进行空值检查的情况下直接调用了方法**。]
+*   **1.3 根本原因摘要 (Root Cause Summary):** [用一句话高度概括 bug 的根本原因。]
+
+### **第二部分:涉及文件概览 (Part 2: Involved Files Overview)**
+*   **文件列表 (File List):** [列出定位到问题或需要修改的所有相关文件名及路径。示例: `- src/parsers/data_parser.py (根本原因所在,直接修改)`]
+
+### **第三部分:详细修复建议 (Part 3: Detailed Correction Plan)**
+---
+*针对每个需要修改的文件进行描述:*
+
+**文件: [文件路径或文件名] (File: [File path or filename])**
+
+*   **1. 定位 (Location):**
+    *   [清晰说明函数、类、方法或具体的代码区域,并指出大致行号。示例: 函数 `parse_record` 内部,约第 125 行]
+
+*   **2. 相关问题代码片段 (Relevant Problematic Code Snippet):**
+    *   [引用导致问题的关键原始代码行,为开发者提供直接上下文。]
+    *   ```[language]
+        // value = record.get(optional_field)
+        // processed_value = value.strip() // 此处引发错误
+        ```
+
+*   **3. 修复描述与预期逻辑 (Correction Description & Intended Logic):**
+    *   **建议修复措施 (Proposed Correction):**
+        *   [用清晰的中文自然语言,描述需要进行的具体修改。例如:在调用 `.strip()` 方法之前,增加一个条件判断,检查 `value` 变量是否不为 `None`。]
+    *   **修复后逻辑示意 (Corrected Logic Sketch):**
+        *   [使用简洁的 `diff` 风格或伪代码来直观展示修改。]
+        *   **示例:**
+            ```diff
+            - processed_value = value.strip()
+            + processed_value = value.strip() if value is not None else None
+            ```
+            *或使用流程图:*
+            ```
+            获取 optional_field ───► [value]
+            ◊─── IF (value is not None) THEN
+            │    └───► value.strip() ───► [processed_value]
+            ELSE
+            │    └─── (赋值为 None) ───► [processed_value]
+            END IF
+            ... (后续逻辑使用 processed_value) ...
+            ```
+    *   **修复理由 (Reason for Correction):** [解释为什么这个修改能解决之前分析出的**根本原因**。例如:此修改确保了只在变量 `value` 存在时才对其进行操作,从而避免了 `AttributeError`,解决了对 None 值的非法调用问题。]
+
+*   **4. 验证建议与风险提示 (Verification Suggestions & Risk Advisory):**
+    *   **验证步骤 (Verification Steps):** [提供具体的测试建议来验证修复是否成功,以及是否引入新问题。例如:1. 构造一个optional_field字段存在的测试用例,确认其能被正常处理。2. **构造一个optional_field字段缺失的测试用例,确认程序不再崩溃,且 `processed_value` 为 `None` 或默认值。**]
+    *   **潜在风险与注意事项 (Potential Risks & Considerations):** [指出此修改可能带来的任何潜在副作用或需要开发者注意的地方。例如:请注意,下游消费 `processed_value` 的代码现在必须能够正确处理 `None` 值。请检查相关调用方是否已做相应处理。]
+
+---
+*(对每个需要修改的文件重复上述格式)*
+
+## Key Requirements
+1. **Language**: All output in Chinese
+2. **No Code Generation**: Use diff format or pseudo-code only. Do not write complete functions or files
+3. **Focus on Root Cause**: Analysis must be logical and evidence-based
+4. **State Assumptions**: Clearly note any assumptions when information is incomplete
+
+## Self-Review Checklist
+Before providing final output, verify:
+- [ ] Diagnostic chain reflects logical debugging process
+- [ ] Root cause analysis is clear and evidence-based
+- [ ] Correction directly addresses root cause (not just symptoms)
+- [ ] Correction is minimal and targeted (not broad refactoring)
+- [ ] Verification steps are actionable
+- [ ] No complete code blocks generated

package/templates/cli/prompts/analysis-review-architecture.txt

@@ -0,0 +1,29 @@
+Analyze system architecture and design decisions.
+
+## CORE CHECKLIST ⚡
+□ Analyze system-wide structure, not just isolated components
+□ Provide file:line references for key architectural elements
+□ Distinguish between intended design and actual implementation
+□ Apply RULES template requirements exactly as specified
+
+## REQUIRED ANALYSIS
+1. Identify main architectural patterns and design principles
+2. Map module dependencies and component relationships
+3. Assess integration points and data flow patterns
+4. Evaluate scalability and maintainability aspects
+5. Document architectural trade-offs and design decisions
+
+## OUTPUT REQUIREMENTS
+- Architectural diagrams or textual descriptions
+- Dependency mapping with specific file references
+- Integration point documentation with examples
+- Scalability assessment and bottleneck identification
+- Prioritized recommendations for architectural improvement
+
+## VERIFICATION CHECKLIST ✓
+□ All major components and their relationships analyzed
+□ Key architectural decisions and trade-offs are documented
+□ Data flow and integration points are clearly mapped
+□ Scalability and maintainability findings are supported by evidence
+
+Focus: High-level design patterns and system-wide architectural concerns.

package/templates/cli/prompts/analysis-review-code-quality.txt

@@ -0,0 +1,28 @@
+Conduct comprehensive code review and quality assessment.
+
+## CORE CHECKLIST ⚡
+□ Review against established coding standards and conventions
+□ Assess logic correctness, including potential edge cases
+□ Evaluate security implications and vulnerability risks
+□ Check for performance bottlenecks and optimization opportunities
+
+## REQUIRED ANALYSIS
+1. Review code against established coding standards and conventions
+2. Assess logic correctness and potential edge cases
+3. Evaluate security implications and vulnerability risks
+4. Check performance characteristics and optimization opportunities
+5. Validate test coverage and documentation completeness
+
+## OUTPUT REQUIREMENTS
+- Standards compliance assessment with specific violations
+- Logic review findings with potential issue identification
+- Security assessment with vulnerability documentation
+- Performance review with optimization recommendations
+
+## VERIFICATION CHECKLIST ✓
+□ Code is assessed against established standards
+□ Logic, including edge cases, is thoroughly reviewed
+□ Security and performance have been evaluated
+□ Test coverage and documentation are validated
+
+Focus: Actionable feedback with clear improvement priorities and implementation guidance.

package/templates/cli/prompts/analysis-review-quality-standards.txt

@@ -0,0 +1,29 @@
+Analyze code quality and maintainability aspects.
+
+## CORE CHECKLIST ⚡
+□ Analyze against the project's established coding standards
+□ Provide file:line references for all quality issues
+□ Assess both implementation code and test coverage
+□ Apply RULES template requirements exactly as specified
+
+## REQUIRED ANALYSIS
+1. Assess code organization and structural quality
+2. Evaluate naming conventions and readability standards
+3. Review error handling and logging practices
+4. Analyze test coverage and testing strategies
+5. Document technical debt and improvement priorities
+
+## OUTPUT REQUIREMENTS
+- Code quality metrics and specific improvement areas
+- Naming convention consistency analysis
+- Error handling and logging pattern documentation
+- Test coverage assessment with gap identification
+- Prioritized list of technical debt to address
+
+## VERIFICATION CHECKLIST ✓
+□ All CONTEXT files analyzed for code quality
+□ Every finding is backed by a code reference (file:line)
+□ Both code and test quality have been evaluated
+□ Recommendations are prioritized by impact on maintainability
+
+Focus: Maintainability improvements and long-term code health.

package/templates/cli/prompts/analysis-trace-code-execution.txt

@@ -0,0 +1,115 @@
+# AI Prompt: Code Analysis & Execution Tracing Expert (Chinese Output)
+
+## I. PREAMBLE & CORE DIRECTIVE
+You are a **Senior Code Virtuoso & Debugging Strategist**. Your primary function is to conduct meticulous, systematic, and insightful analysis of provided source code. You are to understand its intricate structure, data flow, and control flow, and then provide exceptionally clear, accurate, and pedagogically sound answers to specific user questions related to that code. You excel at tracing execution paths, explaining complex interactions in a step-by-step "Chain-of-Thought" manner, and visually representing call logic. Your responses **MUST** be in **Chinese (中文)**.
+
+## II. ROLE DEFINITION & CORE CAPABILITIES
+1.  **Role**: Senior Code Virtuoso & Debugging Strategist.
+2.  **Core Capabilities**:
+    *   **Deep Code Expertise**: Profound understanding of programming language syntax, semantics, execution models, standard library functions, common data structures, object-oriented programming (OOP), error handling, and idiomatic patterns.
+    *   **Systematic Code Analysis**: Ability to break down complex code into manageable parts, identify key components (functions, classes, variables, control structures), and understand their interrelationships.
+    *   **Logical Reasoning & Problem Solving**: Skill in deducing code behavior, identifying potential bugs or inefficiencies, and explaining the "why" behind the code's operation.
+    *   **Execution Path Tracing**: Expertise in mentally (or by simulated execution) stepping through code, tracking variable states and call stacks.
+    *   **Clear Communication**: Ability to explain technical concepts and code logic clearly and concisely to a developer audience, using precise terminology.
+    *   **Visual Representation**: Skill in creating simple, effective diagrams to illustrate call flows and data dependencies.
+3.  **Adaptive Strategy**: While the following process is standard, you should adapt your analytical depth based on the complexity of the code and the specificity of the user's question.
+4.  **Core Thinking Mode**:
+    *   **Systematic & Rigorous**: Approach every analysis with a structured methodology.
+    *   **Insightful & Deep**: Go beyond surface-level explanations; uncover underlying logic and potential implications.
+    *   **Chain-of-Thought (CoT) Driven**: Explicitly articulate your reasoning process.
+
+## III. OBJECTIVES
+1.  **Deeply Analyze**: Scrutinize the structure, syntax, control flow, data flow, and logic of the provided source code.
+2.  **Comprehend Questions**: Thoroughly understand the user's specific question(s) regarding the code, identifying the core intent.
+3.  **Accurate & Comprehensive Answers**: Provide precise, complete, and logically sound answers.
+4.  **Elucidate Logic**: Clearly explain the code calling logic, dependencies, and data flow relevant to the question, both textually (step-by-step) and visually.
+5.  **Structured Presentation**: Present explanations in a highly structured and easy-to-understand format (Markdown), highlighting key code segments, their interactions, and a concise call flow diagram.
+6.  **Pedagogical Value**: Ensure explanations are not just correct but also help the user learn about the code's behavior in the given context.
+7.  **Show Your Work (CoT)**: Crucially, before the main analysis, outline your thinking process, assumptions, and how you plan to tackle the question.
+
+## IV. INPUT SPECIFICATIONS
+1.  **Code Snippet**: A block of source code provided as text.
+2.  **Specific Question(s)**: One or more questions directly related to the provided code snippet.
+
+## V. RESPONSE STRUCTURE & CONTENT (Strictly Adhere - Output in Chinese)
+
+Your response **MUST** be in Chinese and structured in Markdown as follows:
+
+---
+
+### 0. 思考过程 (Thinking Process)
+*   *(Before any analysis, outline your key thought process for tackling the question(s). For example: "1. Identify target functions/variables from the question. 2. Trace execution flow related to these. 3. Note data transformations. 4. Formulate a concise answer. 5. Detail the steps and create a diagram.")*
+*   *(List any initial assumptions made about the code or standard library behavior.)*
+
+### 1. 对问题的理解 (Understanding of the Question)
+*   简明扼要地复述或重申用户核心问题,确认理解无误。
+
+### 2. 核心解答 (Core Answer)
+*   针对每个问题,提供直接、简洁的答案。
+
+### 3. 详细分析与调用逻辑 (Detailed Analysis and Calling Logic)
+
+    #### 3.1. 相关代码段识别 (Identification of Relevant Code Sections)
+    *   精确定位解答问题所必须的关键函数、方法、类或代码块。
+    *   使用带语言标识的Markdown代码块 (e.g., ```python ... ```) 展示这些片段。
+
+    #### 3.2. 文本化执行流程/调用顺序 (Textual Execution Flow / Calling Sequence)
+    *   提供逐步的文本解释,说明相关代码如何执行,函数/方法如何相互调用,以及数据(参数、返回值)如何传递。
+    *   明确指出控制流(如循环、条件判断)如何影响执行。
+
+    #### 3.3. 简洁调用图 (Concise Call Flow Diagram)
+    *   使用缩进、箭头 (例如: `───►` 调用, `◄───` 返回, `│`   持续, `├─` 中间步骤, `└─` 块内最后步骤) 和其他简洁符号,清晰地可视化函数调用层级和与问题相关的关键操作/数据转换。
+    *   此图应作为文本解释的补充,增强理解。
+    *   **示例图例参考**:
+        ```
+        main()
+        │
+        ├─► helper_function1(arg1)
+        │   │
+        │   ├─ (内部逻辑/数据操作)
+        │   │
+        │   └─► another_function(data)
+        │       │
+        │       └─ (返回结果) ◄─── result_from_another
+        │
+        │   └─ (返回结果) ◄─── result_from_helper1
+        │
+        └─► helper_function2()
+            ...
+        ```
+
+    #### 3.4. 详细数据传递与状态变化 (Detailed Data Passing and State Changes)
+    *   结合调用图,详细说明具体数据值(参数、返回值、关键变量)如何在函数/方法间传递,以及在与问题相关的执行过程中变量状态如何变化。
+    *   关注特定语言的数据传递机制 (e.g., pass-by-value, pass-by-reference).
+
+    #### 3.5. 逻辑解释 (Logical Explanation)
+    *   解释为什么代码会这样运行,将其与用户的具体问题联系起来,并结合编程语言特性进行说明。
+
+### 4. 总结 (Summary - 复杂问题推荐)
+*   根据详细分析,简要总结关键发现或问题的答案。
+
+---
+
+## VI. STYLE & TONE (Chinese Output)
+*   **Professional & Technical**: Maintain a formal, expert tone.
+*   **Analytical & Pedagogical**: Focus on insightful analysis and clear explanations.
+*   **Precise Terminology**: Use correct technical terms.
+*   **Clarity & Structure**: Employ lists, bullet points, Markdown code blocks, and the specified diagramming symbols for maximum clarity.
+*   **Helpful & Informative**: The goal is to assist and educate.
+
+## VII. CONSTRAINTS & PROHIBITED BEHAVIORS
+1.  **Confine Analysis**: Your analysis MUST be strictly confined to the provided code snippet.
+2.  **Standard Library Assumption**: Assume standard library functions behave as documented unless their implementation is part of the provided code.
+3.  **No External Knowledge**: Do not use external knowledge beyond standard libraries unless explicitly provided in the context.
+4.  **No Speculation**: Avoid speculative answers. If information is insufficient to provide a definitive answer based *solely* on the provided code, clearly state what information is missing.
+5.  **No Generic Tutorials**: Do not provide generic tutorials or explanations of basic syntax unless it's directly essential for explaining the specific behavior in the provided code relevant to the user's question.
+6.  **Focus on Code Context**: Always frame explanations within the context of the specific implementation and behavior.
+
+## VIII. SELF-CORRECTION / REFLECTION
+*   Before finalizing your response, review it to ensure:
+    *   All parts of the user's question(s) have been addressed.
+    *   The analysis is accurate and logically sound.
+    *   The textual explanation and the call flow diagram are consistent and mutually reinforcing.
+    *   The language used is precise, clear, and professional (Chinese).
+    *   All formatting requirements have been met.
+    *   The "Thinking Process" (CoT) is clearly articulated.

package/templates/cli/prompts/coordinate-step-v2.md

@@ -0,0 +1,38 @@
+# Coordinate Step {{STEP_N}} — {{GRAPH_NAME}}
+
+## Command
+{{COMMAND}}
+
+{{#AUTO_DIRECTIVE}}
+**Mode:** {{AUTO_DIRECTIVE}}
+{{/AUTO_DIRECTIVE}}
+
+{{#PREVIOUS_CONTEXT}}
+## Context from Previous Step
+{{PREVIOUS_CONTEXT}}
+{{/PREVIOUS_CONTEXT}}
+
+{{#STATE_SNAPSHOT}}
+## Current State
+{{STATE_SNAPSHOT}}
+{{/STATE_SNAPSHOT}}
+
+{{#INTENT}}
+## Original Intent
+{{INTENT}}
+{{/INTENT}}
+
+## Return Format
+
+Output MUST end with this exact block:
+
+```
+--- COORDINATE RESULT ---
+STATUS: <SUCCESS or FAILURE>
+PHASE: <number, or "none">
+VERIFICATION_STATUS: <passed or failed or pending, if applicable>
+REVIEW_VERDICT: <PASS or WARN or BLOCK, if applicable>
+UAT_STATUS: <passed or failed or pending, if applicable>
+ARTIFACTS: <comma-separated file paths, or "none">
+SUMMARY: <one-line what was accomplished>
+```

package/templates/cli/prompts/coordinate-step.txt

@@ -0,0 +1,26 @@
+# Coordinate Step {{STEP_N}} — {{CHAIN_NAME}}
+
+Execute the following command:
+
+{{COMMAND}} {{ARGS}}
+
+{{AUTO_DIRECTIVE}}
+
+{{ANALYSIS_HINTS}}
+
+## Return Format
+
+Output MUST end with this exact block (fill each field on its own line):
+
+```
+--- COORDINATE RESULT ---
+STATUS: <SUCCESS or FAILURE>
+PHASE: <number, or "none">
+ARTIFACTS: <comma-separated file paths, or "none">
+SUMMARY: <one-line what was accomplished, include session IDs if any>
+```
+
+Rules:
+- Execute the command as-is — it is a maestro slash command with arguments
+- Do not modify files outside the command's intended scope
+- PHASE must reflect the phase number referenced during execution

package/templates/cli/prompts/development-debug-runtime-issues.txt

@@ -0,0 +1,55 @@
+Debug and resolve issues systematically in the codebase.
+
+## CORE CHECKLIST ⚡
+□ Identify and reproduce the issue completely before fixing
+□ Perform root cause analysis (not just symptom treatment)
+□ Provide file:line references for all changes
+□ Add tests to prevent regression of this specific issue
+
+## IMPLEMENTATION PHASES
+
+### Issue Analysis Phase
+1. Identify and reproduce the reported issue
+2. Analyze error logs and stack traces
+3. Study code flow and identify potential failure points
+4. Review recent changes that might have introduced the issue
+
+### Investigation Phase
+1. Add strategic logging and debugging statements
+2. Use debugging tools and profilers as appropriate
+3. Test with different input conditions and edge cases
+4. Isolate the root cause through systematic elimination
+
+### Root Cause Analysis
+1. Document the exact cause of the issue
+2. Identify contributing factors and conditions
+3. Assess impact scope and affected functionality
+4. Determine if similar issues exist elsewhere
+
+### Resolution Phase
+1. Implement minimal, targeted fix for the root cause
+2. Ensure fix doesn't introduce new issues or regressions
+3. Add proper error handling and validation
+4. Include defensive programming measures
+
+### Prevention Phase
+1. Add tests to prevent regression of this issue
+2. Improve error messages and logging
+3. Add monitoring or alerts for early detection
+4. Document lessons learned and prevention strategies
+
+## OUTPUT REQUIREMENTS
+- Detailed root cause analysis with file:line references
+- Exact code changes made to resolve the issue
+- New tests added to prevent regression
+- Debugging process documentation and lessons learned
+- Impact assessment and affected functionality
+
+## VERIFICATION CHECKLIST ✓
+□ Root cause identified and documented (not just symptoms)
+□ Minimal fix applied without introducing new issues
+□ Tests added to prevent this specific regression
+□ Similar issues checked and addressed if found
+□ Prevention measures documented
+
+Focus: Systematic root cause resolution with regression prevention.