Use this skill when the user says "project manager", "pm", "where are we", "what's in progress", "what should I work on next", "let's work on this project", "project status", "open issues", "what's next", "issue tracker", "track this work", "playground from this spec", "interactive spec preview", or asks about Linear issues, GitHub issues, GitHub PRs, or any issue tracking for the current project. Also use proactively when the user describes work that doesn't appear to be tracked, when starting new work on main/master, when branch naming suggests untracked work, or when the user has a spec they're about to file as a Linear initiative or GitHub project. Routes to focused skills (pm-status, pm-issues, pm-branches, pm-pivot, pm-report, pm-scripts, pm-spec, pm-setup) based on the task.
This listing is imported from SkillsMP metadata and should be treated as untrusted until upstream source review is completed.
Install skill "project-manager" with this command: npx skills add nthplusio/skillsmp-nthplusio-nthplusio-project-manager
This source entry does not include full markdown content beyond metadata.
This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.
Related by shared tags or category signals.
Use this skill when creating a git branch for a Linear or GitHub issue, writing a PR description, opening a pull request, or linking a PR to its tracked issue. Trigger phrases "create a branch", "new branch for this issue", "branch for
Use this skill when creating, updating, or closing an issue in Linear or GitHub; when the user describes untracked work that should be tracked; when drafting issue content; or when the user says "create an issue", "log this in Linear", "add this to Linear", "open a github issue", "file an issue", "create issue
Use this skill when the user changes direction mid-feature, describes a significant scope change, says the approach isn't working, wants to abandon the current approach, or says "we need to rethink this", "let's change direction", "this isn't right", "pivot", "different approach". Also use when the user's current work no longer matches the active tracked issue (Linear or GitHub).
Use this skill when the user asks for a "daily report", "weekly report", "status report", "project report", "send the standup update", "generate a status PDF", "what changed today", "what changed this week", "send a daily update", or any project status summary that should be persisted as a document or sent as email. Produces Markdown, HTML, and/or PDF status reports for the active project showing in-progress work, day-over-day changes, week-over-week changes, and up-next items. Output format is selectable (pdf, html, or both) at runtime. Optional handoff to resend-cli for delivery.