ai-project-planning

Help the user manage their project — capture raw transcripts and brain dumps, show what's in motion and what's next, plan the coming sprint, and reconcile local plans against external sources of truth. Fire on (capture) "here's my brain dump", "voice transcript", "dump this into notes", or any long unstructured first-person paste that reads like a spoken transcript; (status) "what's the plan", "what's next", "catch me up", "where are we on X", "what's the status"; (sprint) "what should I do next", "plan my sprint", "what's on deck this week", "what should I focus on"; (reconciliation) "sync plans", "what's drifted", "what should graduate", "is the local plan still aligned with Jira/Confluence". Trigger even when the user does not name the mode — the skill picks the right mode from the ask and reads the project's AGENTS.md to figure out which planning sources apply (Jira, Confluence, a local plans/ folder, Slack-as-context, or some combination).

Onboard an existing project to the project-planning plugin's conventions — survey what's already there (notes, plans, AGENTS.md, commit history hints of Jira/Confluence/Slack usage), then propose and apply a structured plan of changes (folders to create, files to move, AGENTS.md content to add, planning sources to declare, plugin skills to enable). Use this skill whenever the user says "bootstrap this project", "set up project planning here", "make this project work with the planning plugin", "onboard this repo to project planning", "get this project ready for the planning skills", "wire this up to project planning", or anything along the lines of "land me in a new repo and make it usable by these skills". Trigger even when the user does not name the skill explicitly — if they're asking how to get a fresh project into shape so the other skills will work, this is the right home. Always shows the plan-of-changes for confirmation before writing anything; never silently edits.

Analyze recent project activity against the project's documentation and propose updates — clarifications, recurring questions that deserve a permanent home, decisions made in chat that the docs don't yet reflect, and gaps between code and the technical docs that describe it. Use this skill whenever the user says "update the docs", "what's missing from the docs", "review last week's discussion for doc updates", "what should we have written down", "are our docs in sync with the code", "any doc gaps from recent PRs", or otherwise asks for a documentation hygiene pass driven by what's been happening recently. Trigger even when the user does not name the skill — if they're asking what should be captured in the docs based on what's happened recently in chat or in the code, this is the right home. The skill reads the project's AGENTS.md to discover what activity sources to scan, where docs live, and how docs get updated; it then proposes updates the user can act on. Read-only by default; any write or hand-off only h