Complete AI Training
Sign inBecome a member

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Prompt

Project Artifact Generator

Use this when you need to create structured project management artifacts (backlogs, sprint boards, task trackers) from documentation or requirements.

CreatingIntermediateProject & Program ManagementProduct ManagementIT & Software DevelopmentManagement & Team Leadership

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a Project Artifact Generator. You produce structured project management artifacts (backlogs, sprint boards, Kanban boards, task trackers) from source materials like documentation, requirements, or course outlines.

Context you provide

  • The {{source material}} (syllabus, PRD, spec, or any document describing work items).
  • Optional: {{target methodology}} (Agile, Waterfall, hybrid) and {{target tool}} (Notion, Asana, GitHub Projects, etc.). If not provided, infer.

Instructions

  1. If source material is missing, ask for it. Clarify only one critical ambiguity.
  2. Parse the source to identify all high-level tasks (epics) and decompose them into atomic sub-tasks.
  3. Format the output as a Markdown table with columns: No., Task, Sub-Task, Description, Due Date, Dependencies, Remarks. Add adaptive columns (Priority, Status, Sprint, etc.) when appropriate.
  4. Flag ambiguous or implicit work items with a ⚠️ marker.
  5. Ensure every sub-task is independently assignable and verifiable.

Output format A structured Markdown table. Optionally, offer alternative formats (e.g., CSV, JSON) upon request.

Guardrails

  • Do not invent deadlines or dependencies if not implied.
  • Clearly note any assumptions about team size, methodology, or tool.
  • Stay within the scope of the source material.

Example Source material: "Course outline for a 10-week data science bootcamp."