Modèles de flux pour MCP : routines à copier-coller pour équipes courantes

Ready-to-use workflow templates for engineering, product, support, sales, and ops teams. Each template includes trigger conditions, copy-paste prompts, expected outputs, and safety guardrails.

How to Use These Templates

Each template is a complete workflow you can copy and customize:

Template Components

Trigger: When to use this workflow
Prompts: Copy-paste ready prompts for your AI assistant
Expected Outputs: What you should see
Guardrails: Safety rules to follow

Engineering Team Templates

Template 1: Sprint Planning

Sprint Planning Workflow

Trigger: Start of new sprint, need to break down goals into tasks

"Create a sprint plan from these goals: [list sprint goals]. For each goal: 1. Create tasks in Corcava with clear titles and descriptions 2. Add acceptance criteria as comments 3. Assign owners based on expertise 4. Set due dates aligned with sprint timeline 5. Show me a preview of all tasks before creating 6. Only create after I type 'APPROVE SPRINT PLAN'"

Expected Output: List of tasks with titles, descriptions, owners, due dates (preview before creation)

Guardrails: Always preview before creating, require approval token, verify task details

Template 2: Code Review Follow-up

Code Review Workflow

Trigger: After code review, need to create follow-up tasks

"From this code review feedback: [paste feedback] 1. Extract action items 2. Create tasks in Corcava for each action item 3. Link tasks to original PR/task 4. Assign to appropriate developers 5. Set due dates (1-2 days for small fixes) 6. Show preview before creating 7. Wait for approval before creating tasks"

Expected Output: List of follow-up tasks with links to original work

Guardrails: Preview all tasks, verify assignments, confirm due dates are reasonable

Product Team Templates

Template 3: Feature Spec to Tasks

Feature Breakdown Workflow

Trigger: New feature spec ready, need to break into implementation tasks

"Break down this feature spec into tasks: [paste spec] 1. Create tasks for each major component (frontend, backend, API, tests) 2. Add acceptance criteria from spec 3. Identify dependencies between tasks 4. Assign to appropriate team members 5. Set realistic due dates 6. Show me the task breakdown before creating 7. Only create after I approve"

Expected Output: Structured task breakdown with dependencies and assignments

Guardrails: Verify all components covered, check dependencies, confirm assignments

Template 4: User Feedback to Backlog

Feedback Processing Workflow

Trigger: User feedback collected, need to prioritize and create backlog items

"Process this user feedback: [paste feedback] 1. Identify feature requests and bugs 2. Create tasks in Corcava for each item 3. Prioritize based on impact and effort 4. Add context from feedback 5. Tag with appropriate labels 6. Show me prioritized list before creating 7. Create only after approval"

Expected Output: Prioritized backlog items with context from feedback

Guardrails: Verify priorities, check for duplicates, confirm context is accurate

Support Team Templates

Template 5: Ticket Triage

Ticket Triage Workflow

Trigger: New support tickets, need to triage and assign

"Triage these support tickets: [list tickets] 1. Categorize by severity (critical, high, medium, low) 2. Identify if bug or feature request 3. Create tasks in Corcava for bugs 4. Assign to appropriate team 5. Set SLA-based due dates 6. Add ticket reference in task description 7. Show me triage results before creating tasks"

Expected Output: Categorized tickets with tasks created for bugs

Guardrails: Verify severity classification, check assignments, confirm SLA dates

Template 6: Weekly Support Summary

Support Reporting Workflow

Trigger: End of week, need to generate support metrics

"Generate weekly support summary from Corcava: 1. Count tickets by status (open, in progress, resolved) 2. Calculate average resolution time 3. Identify top issues 4. List unresolved critical tickets 5. Format as executive summary 6. Don't update any tasks—just generate report"

Expected Output: Weekly metrics summary with key insights

Guardrails: Read-only operation, verify metrics accuracy

Sales Team Templates

Template 7: Sales Call Follow-up

Sales Follow-up Workflow

Trigger: After sales call, need to create follow-up tasks

"From this sales call: [paste call notes] 1. Extract action items (send proposal, schedule demo, follow up) 2. Create tasks in Corcava for each action 3. Assign to sales rep 4. Set follow-up dates (1-3 days) 5. Add call context in task description 6. Link to account/opportunity 7. Show preview before creating"

Expected Output: Follow-up tasks with dates and context

Guardrails: Verify action items, confirm dates, check assignments

Template 8: Pipeline Review

Pipeline Analysis Workflow

Trigger: Weekly/monthly pipeline review

"Analyze sales pipeline from Corcava tasks: 1. Group tasks by stage (prospecting, qualified, proposal, closing) 2. Calculate conversion rates 3. Identify stuck opportunities 4. Flag overdue follow-ups 5. Generate pipeline report 6. Read-only—don't update tasks"

Expected Output: Pipeline analysis with conversion metrics

Guardrails: Read-only, verify calculations

Operations Team Templates

Template 9: Incident Response

Incident Management Workflow

Trigger: Production incident, need to track response

"Create incident response tasks: [incident details] 1. Create task for immediate response 2. Create task for root cause analysis 3. Create task for postmortem 4. Assign to on-call engineer 5. Set urgent due dates 6. Add incident context 7. Show preview before creating"

Expected Output: Incident tracking tasks with assignments

Guardrails: Verify urgency, confirm assignments, check dates

Template 10: Weekly Ops Review

Ops Reporting Workflow

Trigger: End of week, need ops status report

"Generate weekly ops report from Corcava: 1. List completed ops tasks 2. Identify open incidents 3. Calculate uptime metrics 4. List upcoming maintenance 5. Flag overdue tasks 6. Format as ops status report 7. Read-only operation"

Expected Output: Weekly ops status with metrics and action items

Guardrails: Read-only, verify metrics

Customizing Templates

Template Customization Tips

Replace placeholders: Update [bracketed] values with your actual data
Adjust dates: Modify due date logic to match your team's timeline
Customize assignments: Change assignment logic based on your team structure
Add team-specific steps: Include additional steps relevant to your workflow
Modify guardrails: Adjust safety rules based on your team's needs

Best Practices

Using Workflow Templates

Start with read-only: Test templates with read operations first
Always preview: Review outputs before approving writes
Customize gradually: Use templates as-is first, then customize
Document changes: Keep notes on how you've customized templates
Share with team: Distribute successful templates to your team

Use Ready-Made Workflow Templates

Copy and customize these templates for your team's workflows

50 Prompt Pack →Use Cases