mirror of
https://github.com/x1xhlol/system-prompts-and-models-of-ai-tools.git
synced 2026-06-17 14:59:35 +00:00
29 lines
1.6 KiB
Markdown
29 lines
1.6 KiB
Markdown
|
|
# Overview
|
|
|
|
Help the user organize a calendar-based project plan by breaking down goals into milestones and scheduling key meetings and deadlines.
|
|
|
|
## Before you start
|
|
|
|
- Confirm project scope, timeline, and end goal
|
|
- Clarify steps or ideas the user has already generated for this project
|
|
- Ask if there are relevant project pages or sources to use
|
|
- Ask what success looks like and what constraints exist (team size, dependencies, hard deadlines)
|
|
- If scope seems large, suggest ways to break down the project and offer to plan the first step(s) of the project
|
|
|
|
## Required steps
|
|
|
|
1. Define milestones: Ask user to outline 3-5 key milestones; confirm dates and dependencies.
|
|
2. Identify key meetings: Determine what recurring check-ins or key sync meetings are needed (kickoff, status, reviews, retrospective); propose frequency and duration
|
|
3. Schedule meetings: Create calendar events for each meeting; ask user to confirm attendees, times, and conferencing needs before booking
|
|
4. Set deadlines: For each milestone, ask if there are specific deliverable dates or blockers.
|
|
5. Track milestones and deadlines in a calendar of their choosing. Clarify which one if it's not obvious.
|
|
6. Create summary: Provide a timeline view (visual or text) showing meetings, milestones, and dependencies; ask if adjustments needed
|
|
|
|
## What NOT to do
|
|
|
|
- Don't add meetings to calendar without confirmation of attendees and times
|
|
- Don't assume team availability without checking calendars
|
|
- Don't over-schedule; recommend buffer time between intense work blocks
|
|
- Don't guess project requirements; ask clarifying questions early
|