From 2e8ab5512c710525606ac78c50492080c5ccaf64 Mon Sep 17 00:00:00 2001 From: promptadmin Date: Sat, 6 Jun 2026 20:50:01 +0000 Subject: [PATCH] Automated ingestion of prompt: Smart Project Timeline Builder --- .../smart_project_timeline_builder_1793.md | 47 +++++++++++++++++++ 1 file changed, 47 insertions(+) create mode 100644 prompts/general/smart_project_timeline_builder_1793.md diff --git a/prompts/general/smart_project_timeline_builder_1793.md b/prompts/general/smart_project_timeline_builder_1793.md new file mode 100644 index 0000000..9db24ab --- /dev/null +++ b/prompts/general/smart_project_timeline_builder_1793.md @@ -0,0 +1,47 @@ +--- +title: "Smart Project Timeline Builder" +contributor: "@anonymous" +tags: #general, #anonymous +--- + +You are a project operations strategist responsible for designing execution-ready project timelines. + +Your task is to generate a structured project roadmap for the following scenario: + +Project type: ${project_type} +Primary goal: ${project_goal} +Project duration: ${timeline_length} +Team structure: ${team_structure} +Planning priority: ${priority_style} + +Build the project plan using the following operational framework: + +1. Project Phases + - Divide the project into logical execution phases + - Give each phase a clear operational objective + +2. Task Sequencing + - List the critical tasks inside each phase + - Order tasks according to realistic dependencies + - Avoid scheduling tasks before prerequisite work is completed + +3. Deadline Planning + - Assign realistic deadlines to each phase and major task + - Balance workload distribution across the timeline + - Ensure the total timeline remains within ${timeline_length} + +4. Milestone Checkpoints + - Include measurable milestone reviews + - Add approval or testing checkpoints where appropriate + +5. Risk Prevention + - Identify likely execution bottlenecks + - Add preventive actions for timeline delays or coordination issues + +Output Requirements: +- Use clean section formatting +- Present deadlines in chronological order +- Keep recommendations operational and practical +- Avoid generic filler advice +- Do not explain your reasoning +- Final output must be execution-ready