88 lines
1.8 KiB
Plaintext
88 lines
1.8 KiB
Plaintext
|
---
|
||
|
|
@agent {
|
||
|
|
role: project manager and task planner,
|
||
|
|
llm: claude-3-5-sonnet-20241022,
|
||
|
|
temperature: 0.5
|
||
|
|
}
|
||
|
|
|
||
|
|
@input project_goal: String
|
||
|
|
@input deadline?: String
|
||
|
|
@input team_size?: String
|
||
|
|
|
||
|
|
@shell "ls -la" as current_directory
|
||
|
|
@shell "git status --short" as git_status
|
||
|
|
|
||
|
|
@validate output {
|
||
|
|
must_contain: ["## Tasks", "## Dependencies", "## Risks"],
|
||
|
|
format: markdown,
|
||
|
|
min_length: 800
|
||
|
|
}
|
||
|
|
---
|
||
|
|
|
||
|
|
# Project Planning Assistant
|
||
|
|
|
||
|
|
## Goal
|
||
|
|
{{project_goal}}
|
||
|
|
|
||
|
|
{{#if deadline}}
|
||
|
|
## Deadline
|
||
|
|
{{deadline}}
|
||
|
|
{{/if}}
|
||
|
|
|
||
|
|
{{#if team_size}}
|
||
|
|
## Team Size
|
||
|
|
{{team_size}} developers
|
||
|
|
{{/if}}
|
||
|
|
|
||
|
|
## Current Project State
|
||
|
|
|
||
|
|
**Directory Structure:**
|
||
|
|
{{current_directory}}
|
||
|
|
|
||
|
|
**Git Status:**
|
||
|
|
{{git_status}}
|
||
|
|
|
||
|
|
---
|
||
|
|
|
||
|
|
## Instructions
|
||
|
|
|
||
|
|
Create a detailed project plan that includes:
|
||
|
|
|
||
|
|
### 1. Task Breakdown
|
||
|
|
Break down the goal into specific, actionable tasks:
|
||
|
|
- [ ] Task 1 (Complexity: simple/moderate/complex)
|
||
|
|
- [ ] Task 2
|
||
|
|
- etc.
|
||
|
|
|
||
|
|
### 2. Dependencies
|
||
|
|
Identify task dependencies:
|
||
|
|
- Task A must complete before Task B can start
|
||
|
|
- Tasks C and D can run in parallel
|
||
|
|
|
||
|
|
### 3. Complexity Assessment
|
||
|
|
For each task, estimate complexity (NOT time):
|
||
|
|
- **trivial** - Straightforward, well-understood
|
||
|
|
- **simple** - Clear but requires some thought
|
||
|
|
- **moderate** - Multiple components, some uncertainty
|
||
|
|
- **complex** - Significant design decisions needed
|
||
|
|
- **very_complex** - High uncertainty, research required
|
||
|
|
|
||
|
|
### 4. Success Criteria
|
||
|
|
Define clear acceptance criteria for each major task.
|
||
|
|
|
||
|
|
### 5. Risks & Mitigation
|
||
|
|
Identify potential blockers and mitigation strategies:
|
||
|
|
- What could go wrong?
|
||
|
|
- How to prevent it?
|
||
|
|
- Fallback plans
|
||
|
|
|
||
|
|
### 6. Implementation Order
|
||
|
|
Recommend the sequence to tackle tasks based on:
|
||
|
|
- Dependencies
|
||
|
|
- Risk reduction (do risky things first)
|
||
|
|
- Value delivery (what provides immediate benefit)
|
||
|
|
|
||
|
|
**IMPORTANT:** Do NOT include time estimates. Focus on what needs to be done and why.
|
||
|
|
|
||
|
|
Generate the plan now.
|