monoco_workflow_agent_manager

经理角色的标准化工作流程（Flow Skill）。从收件箱整理到任务分配，定义标准操作流程，确保需求清晰、任务分解合理。

SKILL.md

--- frontmatter

name: monoco_workflow_agent_manager
description: Standardized workflow for Manager role (Flow Skill). Defines standard operating procedures from Inbox organization to task assignment, ensuring clear requirements and reasonable task decomposition.
type: workflow
role: manager
version: 1.0.0

Manager Flow

Standardized workflow for Manager role, ensuring the "Inbox → Clarify → Decompose → Assign" process.

Workflow State Machine

mermaid

stateDiagram-v2
    [*] --> Inbox: New requirements/ideas
    
    Inbox --> Clarify: Start processing
    Inbox --> Inbox: Park<br/>(low priority)
    
    Clarify --> Decompose: Requirements clear
    Clarify --> Clarify: Need more info<br/>(awaiting feedback)
    
    Decompose --> Assign: Decomposition complete
    Decompose --> Decompose: Too complex<br/>(split into Epic)
    
    Assign --> [*]: Assignment complete

Execution Steps

1. Inbox

•Goal: Collect and temporarily store all incoming requirements, ideas, and tasks
•Input: Memo, user feedback, system alerts, technical debt
•
Checkpoints:
- • Record requirement source and context
- • Initial classification (Feature/Chore/Fix)
- • Assess urgency

2. Clarify (Requirement Clarification)

•Goal: Transform vague requirements into clear descriptions
•Strategy: 5W2H Analysis Method
•
Checkpoints:
- • What: What problem to solve?
- • Why: Why is it important?
- • Who: Who are the stakeholders?
- • When: Expected completion time?
- • Where: Scope of impact?
- • How: Suggested implementation approach?
- • How Much: Workload estimation?

3. Decompose (Task Decomposition)

•Goal: Break down large tasks into independently deliverable subtasks
•Strategy: Vertical Slicing
•
Checkpoints:
- • Identify core value and dependencies
- • Split into independently deliverable Feature/Chore/Fix
- • Set reasonable priorities
- • Create Epic for complex tasks

4. Assign (Task Assignment)

•Goal: Assign tasks to appropriate executors
•
Checkpoints:
- • Assess team capacity and workload
- • Define clear acceptance criteria
- • Set reasonable deadlines
- • Notify relevant members

Decision Branches

Condition	Action
Requirements too vague	Return to Inbox, wait for more information
Task too complex	Create Epic, split into multiple Features
Depends on other tasks	Set dependencies, adjust priorities
Insufficient resources	Adjust scope or defer

Compliance Requirements

•Must: Every task has clear acceptance criteria
•Must: Complex tasks must be split into Epic + Features
•Prohibited: Assigning unclear requirements to Engineer
•Recommended: Use monoco memo to manage temporary ideas