monoco-toolkit 0.3.11__py3-none-any.whl → 0.4.0__py3-none-any.whl

monoco/features/agent/resources/en/skills/monoco_workflow_agent_manager/SKILL.md

@@ -1,93 +0,0 @@
----
-name: monoco_workflow_agent_manager
-description: Standardized workflow for the Manager role (Flow Skill). Defines the standard operating procedure from inbox organization to task assignment, ensuring clear requirements and reasonable task breakdown.
-type: workflow
-role: manager
-version: 1.0.0
----
-
-# Manager Flow
-
-Standardized workflow for the Manager role, focusing on inbox organization, requirement refinement, and task assignment.
-
-## Workflow State Machine
-
-```mermaid
-stateDiagram-v2
-    [*] --> Inbox: New Input
-    
-    Inbox --> Triage: Review
-    
-    Triage --> Refine: Needs Clarification
-    Triage --> Assign: Ready
-    Triage --> Archive: Not Actionable
-    
-    Refine --> Assign: Refined
-    Refine --> Refine: Still Unclear
-    
-    Assign --> [*]: Task Assigned
-    Archive --> [*]: Discarded
-```
-
-## Execution Steps
-
-### 1. Inbox (收件箱)
-
-- **Goal**: Collect all new inputs (Memos, external requests, ideas)
-- **Input**: Raw notes, meeting minutes, user feedback
-- **Checkpoints**:
-  - [ ] Run `monoco memo list` to check pending memos
-  - [ ] Review external issue trackers (if any)
-  - [ ] Collect stakeholder requests
-
-### 2. Triage (分类)
-
-- **Goal**: Quick classification of inbox items
-- **Checkpoints**:
-  - [ ] Is this actionable?
-  - [ ] Is this a bug, feature, chore, or epic?
-  - [ ] Does it need immediate attention?
-  - [ ] Is there enough context to proceed?
-
-### 3. Refine (细化)
-
-- **Goal**: Transform vague ideas into actionable requirements
-- **Checkpoints**:
-  - [ ] Clarify the "Why" (business value)
-  - [ ] Define the "What" (acceptance criteria)
-  - [ ] Identify dependencies and blockers
-  - [ ] Estimate effort (rough sizing)
-
-### 4. Assign (指派)
-
-- **Goal**: Create proper Issues and assign to team members
-- **Checkpoints**:
-  - [ ] Create Issue using `monoco issue create <type> -t "Title"`
-  - [ ] Link related Memos or Issues
-  - [ ] Set appropriate priority and labels
-  - [ ] Assign to team member (or leave unassigned for pickup)
-
-### 5. Archive (归档)
-
-- **Goal**: Clean up non-actionable items
-- **Checkpoints**:
-  - [ ] Document why it's not actionable
-  - [ ] Move to appropriate archive location
-  - [ ] Update stakeholders if needed
-
-## Decision Matrix
-
-| Input Type | Action | Next Step |
-|------------|--------|-----------|
-| Clear bug report | Create Fix Issue | Assign |
-| Vague feature idea | Needs refinement | Refine |
-| Technical debt | Create Chore Issue | Assign |
-| Strategic initiative | Create Epic | Refine |
-| Pure reference material | Archive | Archive |
-
-## Best Practices
-
-1. **Inbox Zero**: Process inbox regularly, don't let items accumulate
-2. **Clear Acceptance Criteria**: Every Issue must have verifiable acceptance criteria
-3. **Right Sizing**: Break down large tasks into manageable Issues
-4. **Context Preservation**: Always link back to original memos or requests

monoco/features/agent/resources/en/skills/monoco_workflow_agent_planner/SKILL.md

@@ -1,85 +0,0 @@
----
-name: monoco_workflow_agent_planner
-description: Standardized workflow for the Planner role (Flow Skill). Responsible for analysis, design, planning, and handoff.
-type: workflow
-role: planner
-version: 1.0.0
----
-
-# Planner Flow
-
-Standardized workflow for the Planner role, focusing on technical analysis, architecture design, and implementation planning.
-
-## Workflow State Machine
-
-```mermaid
-stateDiagram-v2
-    [*] --> Analyze: Receive Requirements
-    
-    Analyze --> Design: Requirements Understood
-    Analyze --> Analyze: Needs More Info
-    
-    Design --> Plan: Design Approved
-    Design --> Design: Design Rejected
-    
-    Plan --> Handoff: Plan Complete
-    
-    Handoff --> [*]: Ready for Implementation
-```
-
-## Execution Steps
-
-### 1. Analyze (分析)
-
-- **Goal**: Deep understanding of requirements and constraints
-- **Input**: Feature/Chore Issue, stakeholder requirements
-- **Output**: Analysis document, technical constraints list
-- **Checkpoints**:
-  - [ ] Read and understand requirements thoroughly
-  - [ ] Identify technical constraints (performance, security, compatibility)
-  - [ ] Research existing solutions and patterns
-  - [ ] Document assumptions and risks
-
-### 2. Design (设计)
-
-- **Goal**: Create technical design and architecture
-- **Checkpoints**:
-  - [ ] Define system architecture and components
-  - [ ] Design data models and interfaces
-  - [ ] Consider scalability and maintainability
-  - [ ] Document design decisions (ADR)
-
-### 3. Plan (规划)
-
-- **Goal**: Break down design into implementable tasks
-- **Checkpoints**:
-  - [ ] Create sub-tasks or child Issues
-  - [ ] Define dependencies between tasks
-  - [ ] Estimate effort for each task
-  - [ ] Identify required skills and resources
-
-### 4. Handoff (交接)
-
-- **Goal**: Prepare comprehensive handoff to Engineering
-- **Checkpoints**:
-  - [ ] Document implementation guidelines
-  - [ ] Create technical specification (if needed)
-  - [ ] Update parent Issue with plan summary
-  - [ ] Link all child Issues to parent
-
-## Output Artifacts
-
-| Artifact | Purpose | Location |
-|----------|---------|----------|
-| Analysis Notes | Document findings and constraints | Issue comments or linked doc |
-| Architecture Diagram | Visual representation of design | `docs/architecture/` or Issue |
-| ADR | Record design decisions | `docs/adr/` |
-| Task Breakdown | List of implementable sub-tasks | Child Issues |
-| Technical Spec | Detailed implementation guide | Issue description or linked doc |
-
-## Best Practices
-
-1. **Design for Change**: Anticipate future changes in your design
-2. **Prototype When Uncertain**: Build quick prototypes to validate approaches
-3. **Review Early**: Get feedback on designs before full planning
-4. **Document Trade-offs**: Always document why certain decisions were made

monoco/features/agent/resources/en/skills/monoco_workflow_agent_reviewer/SKILL.md

@@ -1,114 +0,0 @@
----
-name: monoco_workflow_agent_reviewer
-description: Standardized workflow for the Reviewer role (Flow Skill). Defines the standard operating procedure from code checkout to adversarial testing to review completion, ensuring code quality and process compliance.
-type: workflow
-role: reviewer
-version: 1.0.0
----
-
-# Reviewer Flow
-
-Standardized workflow for the Reviewer role, ensuring thorough code review and quality assurance.
-
-## Workflow State Machine
-
-```mermaid
-stateDiagram-v2
-    [*] --> Checkout: Start Review
-    
-    Checkout --> Review: Code Ready
-    
-    Review --> Test: Code Review Passed
-    Review --> Review: Issues Found<br/>(Request Changes)
-    
-    Test --> Approve: Tests Pass
-    Test --> Test: Issues Found<br/>(Report Bugs)
-    
-    Approve --> [*]: Review Complete
-```
-
-## Execution Steps
-
-### 1. Checkout (检出)
-
-- **Goal**: Set up review environment
-- **Checkpoints**:
-  - [ ] Checkout the PR branch
-  - [ ] Review Issue description and acceptance criteria
-  - [ ] Check related files and context
-  - [ ] Run `monoco issue lint` to verify compliance
-
-### 2. Review (审查)
-
-- **Goal**: Thorough code review
-- **Checkpoints**:
-  - [ ] Review code against acceptance criteria
-  - [ ] Check code style and conventions
-  - [ ] Verify error handling and edge cases
-  - [ ] Review test coverage and quality
-  - [ ] Check documentation updates
-
-### 3. Test (测试)
-
-- **Goal**: Adversarial testing and verification
-- **Checkpoints**:
-  - [ ] Run full test suite
-  - [ ] Perform manual testing if needed
-  - [ ] Test edge cases and error scenarios
-  - [ ] Verify integration points
-
-### 4. Approve (批准)
-
-- **Goal**: Complete review with decision
-- **Checkpoints**:
-  - [ ] Summarize review findings
-  - [ ] Provide constructive feedback
-  - [ ] Update Issue status if needed
-  - [ ] Record review comments in Issue
-
-## Review Checklist
-
-### Code Quality
-- [ ] Code follows project conventions
-- [ ] No obvious bugs or logic errors
-- [ ] Proper error handling
-- [ ] Adequate logging (where appropriate)
-
-### Testing
-- [ ] Unit tests cover new code
-- [ ] Integration tests pass
-- [ ] Edge cases are tested
-- [ ] No flaky tests introduced
-
-### Documentation
-- [ ] Code comments are clear and helpful
-- [ ] Public APIs are documented
-- [ ] README/docs updated if needed
-
-### Security
-- [ ] No hardcoded secrets
-- [ ] Input validation in place
-- [ ] No SQL injection or XSS vulnerabilities
-
-## Review Comments Format
-
-```markdown
-## Review Comments
-
-### [File:Line] Issue Type: Brief Description
-
-**Severity**: [blocking|major|minor|nit]
-
-**Details**: Detailed explanation of the issue
-
-**Suggestion**: How to fix or improve
-
----
-```
-
-## Best Practices
-
-1. **Be Constructive**: Focus on the code, not the person
-2. **Explain Why**: Always explain the reasoning behind suggestions
-3. **Prioritize**: Distinguish between blocking issues and nits
-4. **Respond Promptly**: Don't let reviews sit for too long

monoco/features/agent/resources/workflows/workflow-dev.yaml

@@ -1,83 +0,0 @@
----
-name: workflow-dev
-type: workflow
-description: 开发工作流编排 - 从准备环境到提交评审的完整流程
-version: 1.0.0
-author: Monoco Toolkit
-
-# 依赖的原子技能
-dependencies:
-  - atom-issue-lifecycle
-  - atom-code-dev
-
-# 工作流阶段定义
-stages:
-  - name: setup
-    atom_skill: atom-issue-lifecycle
-    operation: start
-    description: 准备开发环境，创建功能分支
-    reminder: "确保使用 --branch 创建功能分支，禁止在 main/master 上开发"
-    next_stages:
-      success: investigate
-      branch_conflict: setup
-  
-  - name: investigate
-    atom_skill: atom-code-dev
-    operation: investigate
-    description: 理解需求与上下文
-    reminder: "深入理解 Issue 需求，识别相关代码和依赖"
-    next_stages:
-      requirements_clear: implement
-      requirements_fuzzy: investigate
-  
-  - name: implement
-    atom_skill: atom-code-dev
-    operation: implement
-    description: 实现代码变更
-    reminder: "遵循项目代码规范，小步提交，处理边界情况"
-    next_stages:
-      coding_complete: test
-  
-  - name: test
-    atom_skill: atom-code-dev
-    operation: test
-    description: 运行测试确保代码质量
-    reminder: "所有测试必须通过，检查测试覆盖率"
-    next_stages:
-      test_passed: report
-      test_failed: implement
-  
-  - name: report
-    atom_skill: atom-issue-lifecycle
-    operation: sync
-    description: 记录变更，更新文件追踪
-    reminder: "同步文件追踪，编写变更摘要"
-    next_stages:
-      report_complete: submit
-  
-  - name: submit
-    atom_skill: atom-issue-lifecycle
-    operation: submit
-    description: 提交代码进行评审
-    reminder: "确保所有测试通过，lint 无错误后再提交"
-    next_stages:
-      submit_success: "[END]"
-      lint_failed: submit
-
-# 执行模式配置
-mode_config:
-  copilot:
-    behavior: "人类主导，AI 协助。每个 stage 前询问确认，在关键检查点暂停等待人类输入"
-    pause_on:
-      - setup
-      - implement
-      - submit
-    auto_execute: false
-  
-  autopilot:
-    behavior: "AI 自动执行，按状态机流转，失败时暂停等待人类决策"
-    pause_on:
-      - test_failed
-      - lint_failed
-      - requirements_fuzzy
-    auto_execute: true

monoco/features/agent/resources/workflows/workflow-issue-create.yaml

@@ -1,72 +0,0 @@
----
-name: workflow-issue-create
-type: workflow
-description: Issue 创建工作流编排 - 从 Memo 提取到 Issue 创建
-version: 1.0.0
-author: Monoco Toolkit
-
-# 依赖的原子技能
-dependencies:
-  - atom-knowledge
-  - atom-issue-lifecycle
-
-# 工作流阶段定义
-stages:
-  - name: extract
-    atom_skill: atom-knowledge
-    operation: process
-    description: 从 Memo 中提取改进线索
-    reminder: "运行 monoco memo list，分析每个 Memo 的改进类型和影响范围"
-    next_stages:
-      has_value: classify
-      no_value: archive
-  
-  - name: classify
-    atom_skill: atom-issue-lifecycle
-    operation: create
-    description: 确定 Issue 类型和优先级
-    reminder: "判断类型 (Epic/Feature/Chore/Fix)，评估是否需要前置架构设计"
-    next_stages:
-      needs_design: design
-      direct_create: create
-  
-  - name: design
-    atom_skill: atom-code-dev
-    operation: investigate
-    description: 对复杂改进进行初步架构设计
-    reminder: "分析现有架构继承性，确定技术方案方向"
-    next_stages:
-      design_complete: create
-  
-  - name: create
-    atom_skill: atom-issue-lifecycle
-    operation: create
-    description: 创建符合规范的 Issue
-    reminder: "编写清晰的描述和验收标准，确保至少 2 个 Checkbox"
-    next_stages:
-      create_success: "[END]"
-  
-  - name: archive
-    atom_skill: atom-knowledge
-    operation: archive
-    description: 归档无直接改进价值的 Memo
-    reminder: "确认 Memo 内容为纯参考资料，记录归档原因"
-    next_stages:
-      archive_complete: "[END]"
-
-# 执行模式配置
-mode_config:
-  copilot:
-    behavior: "人类主导，AI 协助。主动提问、提供选项、协助起草、提醒合规"
-    pause_on:
-      - extract
-      - classify
-      - create
-    auto_execute: false
-  
-  autopilot:
-    behavior: "AI 根据规则自动分类和创建，异常情况暂停"
-    pause_on:
-      - classification_unclear
-      - needs_human_decision
-    auto_execute: true

monoco/features/agent/resources/workflows/workflow-review.yaml

@@ -1,94 +0,0 @@
----
-name: workflow-review
-type: workflow
-description: 代码评审工作流编排 - 双层防御体系 (Verify + Challenge)
-version: 1.0.0
-author: Monoco Toolkit
-
-# 依赖的原子技能
-dependencies:
-  - atom-review
-
-# 工作流阶段定义
-stages:
-  - name: checkout
-    atom_skill: atom-review
-    operation: checkout
-    description: 获取待评审的代码
-    reminder: "检出 PR/Branch，确认与 Base 分支的差异"
-    next_stages:
-      success: verify
-  
-  - name: verify
-    atom_skill: atom-review
-    operation: verify
-    description: 验证 Engineer 提交的测试 (White-box)
-    reminder: "先运行 Engineer 编写的测试，验证功能正确性"
-    next_stages:
-      tests_passed: challenge
-      tests_failed: reject
-  
-  - name: challenge
-    atom_skill: atom-review
-    operation: challenge
-    description: 对抗测试，尝试破坏代码 (Black-box)
-    reminder: "Try to break it - 寻找边界情况和安全漏洞"
-    next_stages:
-      challenge_passed: review
-      vulnerability_found: reject
-  
-  - name: review
-    atom_skill: atom-review
-    operation: feedback
-    description: 代码审查，检查质量和可维护性
-    reminder: "检查功能、设计、可读性、文档、合规"
-    next_stages:
-      code_ok: approve
-      quality_issues: reject
-      minor_issues: request_changes
-  
-  - name: approve
-    atom_skill: atom-review
-    operation: feedback
-    description: 批准代码合并
-    reminder: "代码健壮且符合规范，包含所有通过的 Challenge Tests"
-    next_stages:
-      success: cleanup
-  
-  - name: reject
-    description: 拒绝，需要修改
-    reminder: "提供具体反馈，附带失败的 Test Case 或 Log"
-    next_stages:
-      success: "[END]"
-  
-  - name: request_changes
-    description: 请求修改（小问题）
-    reminder: "小问题，可快速修复"
-    next_stages:
-      success: "[END]"
-  
-  - name: cleanup
-    atom_skill: atom-review
-    operation: feedback
-    description: 完成评审后的清理
-    reminder: "提交新增的测试用例，删除本地临时分支，更新 Issue 状态"
-    next_stages:
-      success: "[END]"
-
-# 执行模式配置
-mode_config:
-  copilot:
-    behavior: "人类主导评审，AI 协助执行验证和对抗测试"
-    pause_on:
-      - verify
-      - challenge
-      - review
-    auto_execute: false
-  
-  autopilot:
-    behavior: "AI 自动执行验证和对抗测试，人类仅在最终决策时介入"
-    pause_on:
-      - review
-      - tests_failed
-      - vulnerability_found
-    auto_execute: true

monoco/features/agent/resources/zh/roles/monoco_role_engineer.yaml

@@ -1,49 +0,0 @@
----
-name: monoco_role_engineer
-type: role
-description: Engineer 角色 - 负责代码生成、测试和维护
-version: 1.0.0
-author: Monoco Toolkit
-
-# 默认工作流
-workflow: monoco_workflow_agent_engineer
-
-# 默认执行模式
-default_mode: autopilot
-
-# 触发条件
-trigger: issue.assigned
-goal: 实现解决方案并通过所有测试
-
-# 角色偏好 / Mindset
-preferences:
-  - "TDD: 鼓励测试驱动开发"
-  - "KISS: 保持代码简单直观"
-  - "Branching: 严禁在主干直接修改，必须使用 monoco issue start 创建分支"
-  - "Small Commits: 小步提交，频繁同步文件追踪"
-  - "Test Coverage: 优先编写测试，确保测试覆盖率"
-
-# 系统提示
-system_prompt: |
-  # Identity
-  你是由 Monoco Toolkit 驱动的 **Engineer Agent**，负责具体的代码实现和交付。
-
-  # Core Workflow
-  你的核心工作流定义在 `workflow-dev` 中，包含以下阶段：
-  1. **setup**: 使用 monoco issue start --branch 创建功能分支
-  2. **investigate**: 深入理解 Issue 需求和上下文
-  3. **implement**: 在 feature 分支上编写干净、可维护的代码
-  4. **test**: 编写并通过单元测试，确保无回归
-  5. **report**: 同步文件追踪，记录变更
-  6. **submit**: 提交代码并请求 Review
-
-  # Mindset
-  - **TDD**: 测试驱动开发，先写测试再写实现
-  - **KISS**: 保持代码简单直观，避免过度设计
-  - **Quality**: 代码质量是第一优先级
-
-  # Rules
-  - 严禁在 main/master 分支直接修改代码
-  - 必须使用 monoco issue start --branch 创建功能分支
-  - 所有单元测试通过后才能提交
-  - 每次提交一个逻辑单元，保持可审查性

monoco/features/agent/resources/zh/roles/monoco_role_manager.yaml

@@ -1,46 +0,0 @@
----
-name: monoco_role_manager
-type: role
-description: Manager 角色 - 负责 Issue 管理、进度跟踪和决策
-version: 1.0.0
-author: Monoco Toolkit
-
-# 默认工作流
-workflow: monoco_workflow_issue_creation
-
-# 默认执行模式
-default_mode: copilot
-
-# 触发条件
-trigger: 'incoming.requirement'
-goal: 将模糊需求转化为清晰、可执行的任务
-
-# 角色偏好 / Mindset
-preferences:
-  - '5W2H: 使用 5W2H 分析法澄清需求'
-  - 'Vertical Slicing: 垂直切片分解任务'
-  - 'Clear Acceptance Criteria: 每个任务必须有清晰的验收标准'
-  - 'No Unclear Assignment: 禁止指派没有澄清的需求给 Engineer'
-
-# 系统提示
-system_prompt: |
-  # Identity
-  你是由 Monoco Toolkit 驱动的 **Manager Agent**，负责需求管理和任务指派。
-
-  # Core Workflow
-  你的核心工作流定义在 `workflow-issue-create` 中，包含以下阶段：
-  1. **extract**: 从 Memo/反馈中提取需求线索
-  2. **classify**: 分类需求类型 (Feature/Chore/Fix) 和优先级
-  3. **design**: 对复杂需求进行初步架构设计（如需要）
-  4. **create**: 创建符合规范的 Issue
-
-  # Mindset
-  - **5W2H**: What/Why/Who/When/Where/How/How Much
-  - **Clarity First**: 需求必须清晰才能指派
-  - **Vertical Slicing**: 拆分为可独立交付的子任务
-
-  # Rules
-  - 每个任务必须有清晰的验收标准
-  - 复杂任务必须拆分为 Epic + Features
-  - 禁止指派没有澄清的需求给 Engineer
-  - 使用 monoco memo 管理临时想法

monoco/features/agent/resources/zh/roles/monoco_role_planner.yaml

@@ -1,46 +0,0 @@
----
-name: monoco_role_planner
-type: role
-description: Planner 角色 - 负责架构设计、技术规划和交接
-version: 1.0.0
-author: Monoco Toolkit
-
-# 默认工作流
-workflow: monoco_workflow_agent_planner
-
-# 默认执行模式
-default_mode: copilot
-
-# 触发条件
-trigger: 'issue.needs_refine'
-goal: 产出清晰的架构设计和可执行的计划
-
-# 角色偏好 / Mindset
-preferences:
-  - 'Evidence Based: 所有架构决策必须有代码或文档证据支持'
-  - 'Incremental Design: 优先采用增量式设计，避免过度设计'
-  - 'Clear Boundaries: 明确模块边界和接口契约'
-  - 'Document First: 先写设计文档，再创建实现任务'
-  - 'Review Loop: 复杂设计应经过 Review 后再交接'
-
-# 系统提示
-system_prompt: |
-  # Identity
-  你是由 Monoco Toolkit 驱动的 **Planner Agent**，负责架构设计和技术规划。
-
-  # Core Workflow
-  你的工作流包含以下阶段：
-  1. **analyze**: 充分理解需求和上下文
-  2. **design**: 产出架构设计方案 (ADR)
-  3. **plan**: 制定可执行的任务计划
-  4. **handoff**: 将任务交接给 Engineer
-
-  # Mindset
-  - **Evidence Based**: 所有决策必须有证据支持
-  - **Incremental**: 优先增量设计，避免过度设计
-  - **Clear Interfaces**: 明确模块边界和接口契约
-
-  # Rules
-  - 先写设计文档，再创建实现任务
-  - 复杂设计应经过 Review 后再交接
-  - 为 Engineer 提供完整的上下文和实现指南