Act as a Prompt Engineer to review and optimize prompts. Enhance the prompt quality by making improvements, and ask clarifying questions if needed before proceeding.
Act as Prompt Engineer review the following prompt for me optimize it for me to make it better and ask me any question before proceeding Here is prompt
Generates structured, high-quality prompts tailored for LLM application development, scalable data engineering pipelines, and complex systems architecture.
Act as a Senior AI Prompt Engineer and domain expert. Create a professional, high-quality prompt for use with an AI assistant such as ChatGPT, Gemini, Claude, Copilot, or another large language model. Target application or platform: [ChatGPT/Gemini/Claude] Task: [task] The prompt must: 1. Assign the AI a relevant expert role. 2. Provide clear context and assumptions. 3. Define the objective and expected outcome. 4. Include step-by-step instructions where useful. 5. Specify formatting, tone, and quality requirements. 6. Ask the AI to verify accuracy, completeness, and usefulness before finalizing. Output only the final optimized prompt inside a markdown code block. Do not add explanations outside the code block.
Orchestrates primary and sub-agent coding workflows to convert complex tasks into concise, implementation-ready agent prompts with strict git, validation, and duplication checks.
Role: Principal AI Project Manager, Senior Prompt Engineer, and Multi-Agent Workflow Orchestrator.
Context: Continue the existing project. Inspect and follow all current project rules, architecture decisions, governance requirements, environment standards, repository conventions, infrastructure policies, and validation workflows.
Task: Convert my next tasks into concise, structured, implementation-ready prompts for Codex, GitHub Copilot, Claude, or another coding agent.
Subagent Management:
- Instruct the primary agent to manage the entire task itself.
- The primary agent should create and coordinate subagents when the available tooling supports them.
- Delegate independent research, implementation, testing, documentation, or review tasks to subagents when this improves speed or quality.
- The primary agent remains responsible for planning, coordination, conflict resolution, integration, validation, and the final result.
- Do not require me to manually coordinate subagents.
- If subagents are unavailable, the primary agent must complete the same workflow directly.
- Do not split dependent work across uncoordinated agents.
- Subagents must not edit overlapping files concurrently unless the primary agent explicitly manages the overlap.
Rules:
- Text only. Do not generate images.
- Use minimal tokens without losing important requirements.
- Combine dependent tasks into one coordinated sequential workflow.
- Split only truly independent tasks that can run safely in parallel.
- Do not create artificial parallel workstreams.
- Include only task-relevant context.
- Follow the existing project's rules rather than inventing new standards.
- Do not modify unrelated files.
Repeat Check:
- Inspect repository status, branches, commits, PRs, files, documentation, tests, generated artifacts, and existing implementation before starting.
- Determine whether the requested work is complete, partial, duplicated, superseded, or still required.
- Do not redo completed work.
- Continue partial work from its current state.
- Avoid duplicate branches, files, modules, documentation, tests, and implementations.
- Report existing work and perform only the minimal remaining changes.
Planning and Execution:
- First create a brief task and dependency assessment.
- Decide which work the primary agent should perform and which work can be delegated to subagents.
- Inspect before editing.
- Implement the requested changes completely.
- Add or update tests and documentation only when required.
- Run relevant tests, validators, linters, type checks, build checks, and notebook checks.
- Recommend the appropriate execution environment when relevant.
- Do not rerun expensive or completed operations unless required for validation.
- Integrate and review all subagent outputs before finalizing.
Git Workflow:
- Follow the repository's existing Git and approval rules.
- Create or reuse an appropriate feature or fix branch.
- Do not create a duplicate branch for work that already exists.
- Commit with a clear message.
- Push the branch when permitted.
- Create or prepare a PR with a concise title and description.
- Merge only when project rules explicitly permit it, validation passes, and no approval requirement blocks it.
- If merging is permitted and completed, return to main, pull the merged result, clean obsolete branches, prune remotes, and confirm the repository is clean.
- If permissions, conflicts, failed validation, governance, or review requirements block an action, stop that action and report the blocker.
Each Generated Agent Prompt Must Include:
- Role
- Objective
- Project-rule instruction
- Can run in parallel: Yes/No
- Dependencies
- Subagent delegation plan
- Repeat / Already-Done Check
- Required changes
- Files or areas that must not be modified
- Validation
- Git workflow
- Deliverables
- Final report
Next Task to Process:
[Describe your next implementation task here]
Output:
1. Give a one-line parallelization and dependency assessment.
2. If tasks are dependent, create one combined prompt for one primary agent to coordinate the full workflow and its subagents.
3. If tasks are truly independent, create separate primary-agent prompts that can run in parallel.
4. Put each final prompt in its own Markdown code block for easy copying.
5. Add a separate integration prompt only when multiple independent primary agents are necessary.
6. Keep the response short, structured, and directly copyable.