monoco-toolkit 0.3.6__py3-none-any.whl → 0.3.10__py3-none-any.whl

monoco/features/issue/resources/en/skills/issue_create_workflow/SKILL.md

@@ -0,0 +1,167 @@
+---
+name: issue-create-workflow
+description: Extract improvement clues from Memo, classify and create Issue Ticket (Copilot Mode)
+type: flow
+domain: issue
+version: 1.0.0
+---
+
+# Issue Create Workflow
+
+Standardized workflow for extracting improvement clues from Memo, analyzing and creating structured Issue Tickets.
+
+**Applicable Scenario**: Copilot Mode (Human-led, AI-assisted)
+**Target Users**: Developers who need to quickly transform ideas/notes into actionable tasks
+
+## Workflow State Machine
+
+```mermaid
+stateDiagram-v2
+    [*] --> Extract: Read Memo
+    
+    Extract --> Classify: Identify Type
+    Extract --> Archive: No Value
+    
+    Classify --> Design: Architecture Design Required
+    Classify --> Direct: Create Directly
+    
+    Design --> Create: Design Complete
+    Direct --> Create: Create Directly
+    
+    Archive --> [*]: Archive Memo
+    Create --> [*]: Issue Creation Complete
+```
+
+## Execution Steps
+
+### 1. Extract
+
+- **Goal**: Extract key improvement clues from Memo
+- **Input**: Memo file or temporary notes
+- **Output**: Structured improvement clue list
+- **Checkpoints**:
+  - [ ] Run `monoco memo list` to view pending Memos
+  - [ ] Analyze improvement type and impact scope for each Memo
+  - [ ] Identify actionable improvements (not pure reference materials)
+  - [ ] Record improvement motivation and expected effects
+
+**Analysis Dimensions**:
+| Dimension | Question |
+|-----------|----------|
+| Value | What problem does this improvement solve? |
+| Scope | Which modules/features are affected? |
+| Urgency | Do it now or later? |
+| Feasibility | Is there enough information to start? |
+
+### 2. Classify
+
+- **Goal**: Determine Issue type and priority
+- **Checkpoints**:
+  - [ ] Determine if it's an architecture-level improvement (→ Epic)
+  - [ ] Determine if it's user value increment (→ Feature)
+  - [ ] Determine if it's engineering debt (→ Chore)
+  - [ ] Determine if it's a bug fix (→ Fix)
+  - [ ] Assess if pre-architecture design is required
+
+**Decision Branches**:
+
+| Condition | Type | Next Step |
+|-----------|------|-----------|
+| Architecture vision-level improvement, needs decomposition into multiple Features | Epic | → Design |
+| User deliverable value, with clear acceptance criteria | Feature | → Direct |
+| Engineering maintenance task, technical debt cleanup | Chore | → Direct |
+| Bug fix, with clear reproduction steps | Fix | → Direct |
+| Pure reference material, no direct improvement value | - | → Archive |
+| Requires architecture design to estimate effort | - | → Design |
+
+### 3. Design (Optional)
+
+- **Goal**: Preliminary architecture design for complex improvements
+- **Applicable**: Epic or large Feature
+- **Checkpoints**:
+  - [ ] Analyze existing architecture inheritance
+  - [ ] Determine technical solution direction
+  - [ ] Identify dependency relationships and risk points
+  - [ ] Estimate effort and milestones
+
+**Outputs**:
+- Architecture Decision Record (ADR) draft
+- Subtask decomposition suggestions
+- Dependency Issue list
+
+### 4. Create
+
+- **Goal**: Create Issue that meets specifications
+- **Checkpoints**:
+  - [ ] Run `monoco issue create <type> -t "Title"`
+  - [ ] Write clear description and background
+  - [ ] Define verifiable acceptance criteria (at least 2 Checkboxes)
+  - [ ] Set dependency relationships (if needed)
+  - [ ] Associate related Memo (if applicable)
+  - [ ] Run `monoco issue lint` to verify compliance
+
+**Issue Content Template**:
+
+```markdown
+## Objective
+Clearly describe the goal and expected outcome of this Issue.
+
+## Acceptance Criteria
+- [ ] Acceptance criterion 1
+- [ ] Acceptance criterion 2
+
+## Technical Tasks
+- [ ] Technical task 1
+- [ ] Technical task 2
+
+## Related
+- Parent: EPIC-XXXX (if applicable)
+- Related Memo: MEMO-XXXX (if applicable)
+```
+
+### 5. Archive (Optional)
+
+- **Goal**: Archive Memos with no direct improvement value
+- **Checkpoints**:
+  - [ ] Confirm Memo content is pure reference material
+  - [ ] Record archiving reason
+  - [ ] Update Memo status (if system supports)
+
+## Issue Type Guide
+
+| Type | Purpose | Prefix | Mindset | Example |
+|------|---------|--------|---------|---------|
+| Epic | Grand goals, vision container | EPIC- | Architect | Refactor core architecture |
+| Feature | User value increment | FEAT- | Product Owner | Add export functionality |
+| Chore | Engineering tasks | CHORE- | Builder | Upgrade dependency versions |
+| Fix | Bug fixes | FIX- | Debugger | Fix memory leak |
+
+## Related Commands
+
+```bash
+# View pending Memos
+monoco memo list
+
+# Create Issue
+monoco issue create feature -t "Title"
+monoco issue create chore -t "Title"
+monoco issue create fix -t "Title"
+monoco issue create epic -t "Title"
+
+# Verify Issue compliance
+monoco issue lint
+```
+
+## Relationship with flow_engineer
+
+This workflow complements `flow_engineer`:
+- `issue-create-workflow`: Focuses on Issue creation phase, transforming ideas into actionable tasks
+- `flow_engineer`: Focuses on code implementation phase, executing Investigate → Code → Test → Report → Submit
+
+## Copilot Mode Tips
+
+As an AI Copilot, you should:
+1. **Ask proactively**: When Memo content is unclear, ask human developers for intent
+2. **Provide options**: Give multiple classification suggestions with reasoning
+3. **Assist drafting**: Help write Issue descriptions and acceptance criteria
+4. **Remind compliance**: Ensure created Issues meet project specifications

monoco/features/issue/resources/en/skills/issue_develop_workflow/SKILL.md

@@ -0,0 +1,224 @@
+---
+name: issue-develop-workflow
+description: Execute complete workflow for Issue development, testing, submission and review (Copilot Mode)
+type: flow
+domain: issue
+version: 1.0.0
+---
+
+# Issue Develop Workflow
+
+Complete standardized workflow for Issue development, testing, submission, review and merge.
+
+**Applicable Scenario**: Copilot Mode (Human-led, AI-assisted)
+**Target Users**: Developers responsible for implementing features or fixing bugs
+
+## Workflow State Machine
+
+```mermaid
+stateDiagram-v2
+    [*] --> Setup: Start Development
+    
+    Setup --> Develop: Environment Ready
+    Setup --> Setup: Dependencies Not Met<br/>(Wait for Resolution)
+    
+    Develop --> Test: Coding Complete
+    Develop --> Develop: Needs Iteration<br/>(Continue Development)
+    
+    Test --> Submit: Tests Pass
+    Test --> Develop: Tests Fail<br/>(Fix Code)
+    
+    state "Review Loop" as ReviewLoop {
+        Submit --> Review: Submit for Review
+        Review --> Fix: Changes Required
+        Fix --> Submit: Resubmit
+    }
+    
+    Review --> Merge: Review Passed
+    
+    Merge --> [*]: Merge Complete
+```
+
+## Execution Steps
+
+### 1. Setup
+
+- **Goal**: Prepare development environment, ensure ready to code
+- **Checkpoints**:
+  - [ ] Run `monoco issue start <ID> --branch` to create feature branch
+  - [ ] Confirm branch is created and switched
+  - [ ] Verify not currently on main/master branch
+  - [ ] Check if dependency Issues are completed
+  - [ ] Confirm Issue is refined (has technical task list)
+
+**Environment Checklist**:
+| Check Item | Command/Method |
+|------------|----------------|
+| Current Branch | `git branch --show-current` |
+| Branch Status | `git status` |
+| Dependency Issues | `monoco issue show <ID>` |
+| Code Standards | Check project lint configuration |
+
+### 2. Develop
+
+- **Goal**: Implement feature or fix bug
+- **Strategy**: Iterative development, small commits
+- **Checkpoints**:
+  - [ ] Follow project code standards
+  - [ ] Write/update unit tests
+  - [ ] Commit code regularly (small commits)
+  - [ ] Update file tracking (`monoco issue sync-files`)
+  - [ ] Maintain code reviewability (single commit < 400 lines)
+
+**Development Principles**:
+| Principle | Description |
+|-----------|-------------|
+| Small Commits | Each commit is a logical unit |
+| Test First | Prioritize writing test cases |
+| Continuous Sync | Update file tracking promptly |
+| Stay Focused | Avoid unrelated changes |
+
+### 3. Test
+
+- **Goal**: Ensure code quality and functional correctness
+- **Checkpoints**:
+  - [ ] Run unit tests, ensure they pass
+  - [ ] Run integration tests (if applicable)
+  - [ ] Run code style checks (lint)
+  - [ ] Manually verify functionality (if needed)
+  - [ ] Check test coverage
+
+**Test Levels**:
+```
+Unit Test → Integration Test → E2E Test → Manual Verification
+   ↑          ↑            ↑            ↑
+ Required   Recommended   As Needed    As Needed
+```
+
+### 4. Submit
+
+- **Goal**: Prepare for code review
+- **Checkpoints**:
+  - [ ] Run `monoco issue lint` to check compliance
+  - [ ] Fix all Lint errors
+  - [ ] Update task list status (mark completed items)
+  - [ ] Write clear commit message
+  - [ ] Run `monoco issue submit <ID>`
+
+**Commit Message Specification**:
+```
+<type>(<scope>): <subject>
+
+<body>
+
+Refs: <ISSUE-ID>
+```
+
+| Type | Purpose |
+|------|---------|
+| feat | New feature |
+| fix | Bug fix |
+| docs | Documentation update |
+| style | Code formatting |
+| refactor | Refactoring |
+| test | Test related |
+| chore | Build/tools |
+
+### 5. Review
+
+- **Goal**: Code quality and process compliance check
+- **Checkpoints**:
+  - [ ] Is functionality correctly implemented
+  - [ ] Does code meet design specifications
+  - [ ] Are tests sufficient
+  - [ ] Is documentation updated
+  - [ ] Does it follow project standards
+
+**Review Dimensions**:
+| Dimension | Check Content |
+|-----------|---------------|
+| Correctness | Does functionality work as expected |
+| Design | Does it meet architecture design |
+| Testing | Is test coverage sufficient |
+| Standards | Does it follow code standards |
+| Documentation | Is documentation updated |
+| Performance | Are there obvious performance issues |
+| Security | Are there security risks |
+
+### 6. Merge
+
+- **Goal**: Complete Issue, merge code
+- **Checkpoints**:
+  - [ ] Code has passed review
+  - [ ] All CI checks pass
+  - [ ] Code is merged to main branch
+  - [ ] Run `monoco issue close <ID> --solution completed --prune`
+  - [ ] Verify branch is cleaned up
+  - [ ] Update Review Comments (record review feedback)
+
+## Decision Branches
+
+| Condition | Action |
+|-----------|--------|
+| Dependency Issues not completed | Return to Setup, wait for dependencies |
+| Tests fail | Return to Develop, fix code |
+| Lint fails | Fix compliance issues, resubmit |
+| Review requires changes | Return to Fix, modify per feedback |
+| Review passed | Enter Merge, merge and cleanup |
+
+## Compliance Requirements
+
+- **Prohibited**: Directly modify code on main/master branch
+- **Required**: Use `monoco issue start --branch` to create feature branch
+- **Required**: All unit tests must pass before Submit
+- **Required**: Each Issue must have at least 2 Checkboxes
+- **Required**: Review/Done phase must include Review Comments
+- **Recommended**: Small commits, frequently sync file tracking
+
+## Related Commands
+
+```bash
+# Start development
+monoco issue start FEAT-0001 --branch
+
+# Sync file tracking
+monoco issue sync-files
+
+# Check compliance
+monoco issue lint
+
+# Submit for review
+monoco issue submit FEAT-0001
+
+# Close Issue
+monoco issue close FEAT-0001 --solution completed --prune
+```
+
+## Relationship with flow_engineer
+
+The relationship between this workflow and `flow_engineer`:
+
+```
+issue-develop-workflow          flow_engineer
+       │                              │
+       ├── Setup ─────────────────────┤
+       ├── Develop ←──────────────────┤ Investigate → Code → Test
+       ├── Test ──────────────────────┤
+       ├── Submit ────────────────────┤ Report → Submit
+       ├── Review ────────────────────┤
+       └── Merge ─────────────────────┤
+```
+
+- `issue-develop-workflow`: Focuses on Issue-level process management
+- `flow_engineer`: Focuses on specific technical process for code implementation
+
+During the Develop phase, developers should follow `flow_engineer`'s Investigate → Code → Test → Report → Submit process.
+
+## Copilot Mode Tips
+
+As an AI Copilot, you should:
+1. **Assist coding**: Help implement features, fix bugs
+2. **Code review**: Pre-review before submission to find potential issues
+3. **Test assistance**: Help write test cases, ensure coverage
+4. **Compliance check**: Remind developers to follow project standards
+5. **Documentation sync**: Assist in updating related documentation

monoco/features/issue/resources/en/skills/issue_lifecycle_workflow/SKILL.md

@@ -0,0 +1,159 @@
+---
+name: issue-lifecycle-workflow
+description: Issue Lifecycle Workflow (Flow Skill). Defines the complete Issue management process from creation to closure, ensuring task tracking and process compliance.
+type: flow
+domain: issue
+version: 1.0.0
+---
+
+# Issue Lifecycle Workflow
+
+Standardized workflow for Issue lifecycle, ensuring "Open → Start → Develop → Submit → Review → Close" process.
+
+## Workflow State Machine
+
+```mermaid
+stateDiagram-v2
+    [*] --> Open: Create Issue
+    
+    Open --> Start: Prepare Development
+    Open --> Open: Requirements Unclear<br/>(Wait for Clarification)
+    
+    Start --> Develop: Branch Created
+    Start --> Start: Branch Conflict<br/>(Resolve Conflict)
+    
+    Develop --> Submit: Development Complete
+    Develop --> Develop: Tests Fail<br/>(Fix Code)
+    
+    state "Oracle Loop" as ReviewLoop {
+        Submit --> Review: Submit for Review
+        Review --> Fix: Rejected
+        Fix --> Submit: Resubmit
+    }
+    
+    Review --> Close: Approved for Merge
+    
+    Close --> [*]: Cleanup Complete
+```
+
+## Execution Steps
+
+### 1. Open
+
+- **Goal**: Create clear, actionable Issue
+- **Input**: Requirement description, type, priority
+- **Output**: Issue Ticket file
+- **Checkpoints**:
+  - [ ] Use `monoco issue create <type> -t "Title"`
+  - [ ] Select appropriate type (epic/feature/chore/fix)
+  - [ ] Write clear description and acceptance criteria
+  - [ ] Set dependency relationships (if needed)
+  - [ ] Ensure at least 2 Checkboxes
+
+### 2. Start
+
+- **Goal**: Prepare development environment, create feature branch
+- **Checkpoints**:
+  - [ ] Run `monoco issue start <ID> --branch`
+  - [ ] Confirm branch is created and switched
+  - [ ] Verify not currently on main/master branch
+  - [ ] Check if dependency Issues are completed
+
+### 3. Develop
+
+- **Goal**: Implement feature or fix bug
+- **Strategy**: Iterative development, continuous testing
+- **Checkpoints**:
+  - [ ] Follow project code standards
+  - [ ] Write/update unit tests
+  - [ ] Run test suite, ensure it passes
+  - [ ] Commit code regularly (small commits)
+  - [ ] Update file tracking (`monoco issue sync-files`)
+
+### 4. Submit
+
+- **Goal**: Prepare for code review
+- **Checkpoints**:
+  - [ ] Run `monoco issue lint` to check compliance
+  - [ ] Fix all Lint errors
+  - [ ] Update task list status
+  - [ ] Run `monoco issue submit <ID>`
+  - [ ] Write change summary
+
+### 5. Review
+
+- **Goal**: Code quality and process compliance check
+- **Checkpoints**:
+  - [ ] Is functionality correctly implemented
+  - [ ] Does code meet design specifications
+  - [ ] Are tests sufficient
+  - [ ] Is documentation updated
+  - [ ] Does it follow project standards
+
+### 6. Close
+
+- **Goal**: Complete Issue, cleanup environment
+- **Checkpoints**:
+  - [ ] Code is merged to main branch
+  - [ ] Run `monoco issue close <ID> --solution completed --prune`
+  - [ ] Verify branch is cleaned up
+  - [ ] Update Review Comments (if needed)
+
+## Decision Branches
+
+| Condition | Action |
+|-----------|--------|
+| Requirements unclear | Return to Open, request clarification |
+| Branch creation fails | Check Git status, resolve conflicts |
+| Tests fail | Return to Develop, fix code |
+| Lint fails | Fix compliance issues, resubmit |
+| Review rejected | Return to Develop, modify per feedback |
+| Review passed | Enter Close, merge and cleanup |
+
+## Compliance Requirements
+
+- **Prohibited**: Directly modify code on main/master branch
+- **Required**: Use `monoco issue start --branch` to create feature branch
+- **Required**: All unit tests must pass before Submit
+- **Required**: Each Issue must have at least 2 Checkboxes
+- **Required**: Review/Done phase must include Review Comments
+- **Recommended**: Small commits, frequently sync file tracking
+
+## Related Commands
+
+```bash
+# Create Issue
+monoco issue create feature -t "Title"
+
+# Start development
+monoco issue start FEAT-0001 --branch
+
+# Sync file tracking
+monoco issue sync-files
+
+# Check compliance
+monoco issue lint
+
+# Submit for review
+monoco issue submit FEAT-0001
+
+# Close Issue
+monoco issue close FEAT-0001 --solution completed --prune
+```
+
+## Issue Type Guide
+
+| Type | Purpose | Prefix | Mindset |
+|------|---------|--------|---------|
+| Epic | Grand goals, vision container | EPIC- | Architect |
+| Feature | User value increment | FEAT- | Product Owner |
+| Chore | Engineering tasks | CHORE- | Builder |
+| Fix | Bug fixes | FIX- | Debugger |
+
+## Relationship with flow_engineer
+
+This workflow complements `flow_engineer`:
+- `issue-lifecycle-workflow`: Focuses on Issue management process
+- `flow_engineer`: Focuses on code implementation process
+
+Engineers should follow `flow_engineer`'s Investigate → Code → Test → Report → Submit process during the Develop phase.