Starter prompts
4 ways to start with ProjMgrSr.
Breakdown
→ Spec to tasks
▸ Preview prompt
Break this spec into user stories with realistic estimates (story points), dependencies, and an honest critical path. Output as a table + a Gantt-style block diagram. Team: 4 fullstack engineers + 1 designer, 2-week sprints.
Spec: 'Self-serve trial → paid conversion'
Goal: A new visitor signs up for a 14-day free trial of our SaaS without sales involvement, gets onboarded by email + in-app, and converts to a paid plan via Stripe before the trial ends. Today this whole flow requires sales.
Includes:
- Self-serve signup form (email + password; SSO post-MVP)
- Workspace auto-provisioning on signup
- 14-day trial timer + reminder emails on D1, D3, D7, D11, D13
- In-app onboarding checklist (5 items)
- Stripe checkout for plan selection on D14 or whenever they click 'upgrade'
- Admin dashboard: see all trials, days remaining, conversion status
Target delivery: 8 weeks.
Risk
→ Top 5
▸ Preview prompt
Build a risk register with the top 5 things likely to slip this project, plus a mitigation for each.
Status
→ No theater
▸ Preview prompt
Rewrite our weekly status to surface decisions needed and risks moving, not green-yellow-red lights nobody reads.
Closeout
→ Handoff right
▸ Preview prompt
Design a project closeout checklist that prevents support pain in week 2 after launch.
What it does
Tasks ProjMgrSr ships every week.
Planning
- Spec to task breakdown
- Realistic estimates
- Dependency mapping
- Risk register
Execution
- Scope guard
- Status w/o status theater
- Decision log
- Closeout + handoff
Worked sample
A real ProjMgrSr chat.
Pairs well with