---
name: project-task-list-syllabus-creator
description: "Breaks a project into phases with tasks, owners, durations and milestones, formatted as a wiki-ready project plan. Use when a project needs breaking into phases with owners, durations, milestones and tasks for a project wiki. Do not use for a dependency-aware task list with effort estimates or a mind-map outline. Related topics: productivity, work, project."
---

# Project Task List Syllabus Creator

Breaks a project into phases with tasks, owners, durations and milestones, formatted as a wiki-ready project plan.

## When to use

Use this skill when a project needs breaking into phases with owners, durations, milestones and tasks for a project wiki. Do not use it for a dependency-aware task list with effort estimates or a mind-map outline.

## Workflow

1. Ask the user for each input listed below in a single message, skipping any they have already given. Where options are listed, offer them, but accept other answers too.
2. Split the timeline into the stated number of phases that sum to the whole.
3. Tie each phase to a milestone that delivers part of the key deliverables.
4. Assign one accountable owner per phase from the chosen roles.
5. List concrete tasks under each phase.
6. Confirm every deliverable is covered and note the review points.

## Inputs

- **Project name** (free text, e.g. "The project title")
- **Overall timeline** (choose one: 1 month, 3 months, 6 months, 12 months)
- **Number of phases** (number from 1 to 5)
- **Key deliverables** (longer free text)
- **Team roles** (choose any: Analyst, Designer, Developer, Tester, Manager, Stakeholder)
- **Review frequency** (choose one: Weekly, Bi-weekly, Monthly)

## Output

Markdown with a project heading, a Project Phases table with Phase, Duration, Owner and Milestone, and a task bullet list under each phase.

## Prompt template

Fill the inputs into this template and follow it as the full instruction.

### Project Task List Syllabus Creator

Write the phase plan for a project, ready to paste into a wiki.

- Project name: {{Project name}}
- Overall timeline: {{Overall timeline}}
- Number of phases: {{Number of phases}}
- Key deliverables: {{Key deliverables}}
- Team roles: {{Team roles}}
- Review frequency: {{Review frequency}}

Divide the timeline into the stated number of phases, each ending in a milestone that matches a deliverable. Give each phase a duration, a single accountable owner from the chosen roles, and a list of concrete tasks. Make sure every deliverable appears in a phase and that the durations add up to the overall timeline. Say in each phase when the review at the chosen frequency takes place and who attends.

Return markdown with a level-1 heading of the project name, a table titled Project Phases with columns Phase, Duration, Owner, Milestone, and a bullet list of tasks beneath each phase.

## Pitfalls

- Phase durations that do not add up to the timeline.
- Assigning a stakeholder as the owner of build tasks.
- A deliverable that appears in no phase.
