Project, work-item, and milestone setup
Create a project with a clear outcome, delivery window, owner, work breakdown, milestones, and a small set of fields that make work comparable across teams.
FREE CLAUDE & CODEX PLUGIN TEMPLATE
Project Management System PRD Template
A real SOT-based Project Management System PRD template connecting project and work-item creation, work, milestone, and progress lookup, assignment, schedule change, and issue handling, schedule, risk, and completion reporting.
View source on GitHub · MIT licensed
USE CASE
Who this template is for
Teams designing an internal operations system for project team member and project manager and pmo
CONTENTS
What the template includes
- Project and work-item creation
- Work, milestone, and progress lookup
- Assignment, schedule change, and issue handling
- Schedule, risk, and completion reporting
VIBESPEC VIEWER
See the plan in VibeSpec
Each screen is generated from the public SOT included with this template.
Open this screen in the live demo 
Open this screen in the live demo 
Open this screen in the live demo 
Open this screen in the live demo PRACTICAL GUIDE
How to use and adapt this Project Management System PRD Template
A project system only creates clarity when the plan, work, decisions, and delivery risk stay connected. This SOT brings projects, work items, milestones, ownership, schedule changes, blockers, and completion reporting into one reviewable operating plan.
What this Project Management System PRD Template actually includes
Work views that preserve delivery context
Let contributors move between a work-item list, board, calendar, and project timeline without losing the parent milestone, current status, due date, dependency, or decision history.
Assignment, schedule change, and blocker handling
Make changes to owners and dates explicit, capture the reason for a blocked item, and route decisions that affect a milestone or committed delivery date to the right owner.
Risk, progress, and completion reporting
Show work due soon, blocked work, milestone confidence, scope change, and completion trends so a project lead can act before a status report becomes a surprise.
Team permissions and delivery-tool boundaries
Separate contributor, project-lead, portfolio, and administrator access; retain decision history; and define where GitHub, Jira, calendar, or chat data is authoritative.
Start in three steps, even without planning experience
1. Review the complete HTML with your team
The download opens in a browser without setup. Compare the PRD, feature specification, screen structure, and user flow with the work your team does today.
2. Name your operating rules
Agree on what counts as a project, milestone, task, blocker, dependency, and done; then decide who may change dates, close work, or approve a scope change.
3. Give the SOT JSON to VibeSpec
Attach the SOT JSON in Claude or Codex with the VibeSpec plugin and describe the change in plain language. VibeSpec keeps requirements, features, screens, and user flows connected.
Adapt this Project Management System for your team
Start with the delivery vocabulary your team uses
Map the template’s project, work item, milestone, status, priority, and risk labels to your existing planning language before importing every possible workflow.
Treat a date change as a decision, not a field edit
Define which schedule changes require a reason, an approver, or an update to dependent work. This prevents a healthy-looking timeline from hiding delivery risk.
Choose one source of truth for each signal
If engineering uses GitHub and the business team uses this system, decide whether status, estimates, and completion are synchronized, linked, or manually confirmed.
Capabilities to add next
Portfolio and capacity planning
Add cross-project priorities, team capacity, staffing assumptions, and scenario comparison without turning the core work-item flow into a portfolio spreadsheet.
Dependency and release management
Create an initiative for dependency maps, release gates, change windows, and go/no-go decisions connected to milestones and risks.
Developer-tool integration
Define the sync direction, field mapping, failure handling, and ownership boundaries before connecting GitHub, Jira, Linear, or calendar events.
Prompts you can use with VibeSpec
Match our delivery method
Adapt this project management plan for our team. Ask whether we use Scrum, Kanban, milestones, or a hybrid approach; then update statuses, roles, planning views, and user flows without losing reporting context.Create a small team MVP
Reduce this project system to projects, work items, owners, due dates, milestones, and blocked-work reporting for a ten-person team. Move portfolio planning and external integrations into separate initiatives.Add release governance
Create a release-governance initiative on top of this project plan. Include release readiness, dependency checks, change approval, a go/no-go decision, and the connection back to project milestones.Project Management System FAQ
Can I use this template without development experience?
Yes. The complete HTML opens in a browser for review and sharing. To adapt the plan, attach the SOT JSON to Claude or Codex with the VibeSpec plugin and describe the change in plain language.
What is included in this planning template?
It includes project and work-item setup, milestones, list and timeline context, assignment and schedule-change handling, blocker and risk management, and reporting for delivery confidence and completion.
What is the difference between the HTML and SOT JSON downloads?
The HTML is a complete planning document for reading and sharing. The SOT JSON is source data that VibeSpec can update while keeping requirements, features, screens, and user flows connected.
How should I add a new capability?
For a discrete capability such as automation, integration, or additional analytics, create and review a separate initiative before changing the product plan broadly.
WORKFLOW
Use it with VibeSpec
- Open the complete HTML file to review or share it immediately.
- Download the SOT JSON and load it in the VibeSpec viewer.
- Adapt the features, screens, and flows for your team.