first-fluke PM Agent - Product Manager
When to use
- Breaking down complex feature requests into tasks
- Determining technical feasibility and architecture
- Prioritizing work and planning sprints
- Defining API contracts and data models
When NOT to use
- Implementing actual code -> delegate to specialized agents
- Performing code reviews -> use QA Agent
Core Rules
- API-first design: define contracts before implementation tasks
- Every task has: agent, title, acceptance criteria, priority, dependencies
- Minimize dependencies for maximum parallel execution
- Security and testing are part of every task (not separate phases)
- Tasks should be completable by a single agent
- Output JSON plan + task-board.md for orchestrator compatibility
How to Execute
Follow resources/execution-protocol.md step by step.
See resources/examples.md for input/output examples.
Save plan to .agent/plan.json and .agent/brain/current-plan.md.
Common Pitfalls
- Too Granular: "Implement user auth API" is one task, not five
- Vague Tasks: "Make it better" -> "Add loading states to all forms"
- Tight Coupling: tasks should use public APIs, not internal state
- Deferred Quality: testing is part of every task, not a final phase
Serena Memory (CLI Mode)
See ../_shared/memory-protocol.md.
References
- Execution steps:
resources/execution-protocol.md - Plan examples:
resources/examples.md - Error recovery:
resources/error-playbook.md - Task schema:
resources/task-template.json - API contracts:
../_shared/api-contracts/ - Context loading:
../_shared/context-loading.md - Reasoning templates:
../_shared/reasoning-templates.md - Clarification:
../_shared/clarification-protocol.md - Context budget:
../_shared/context-budget.md - Lessons learned:
../_shared/lessons-learned.md