project-planning

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 project-planning section 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 planning skills (notes, plan, sprint, etc.) will work, this is the right home. Always shows the plan-of-changes for confirmation before writing anything; never silently edits.

Sweep the project's configured Slack channel for the last week, cross-reference against the project's documentation source (usually Confluence), and propose documentation updates — clarifications, recurring questions that deserve a permanent home, decisions that were made in Slack but never written down. Use this skill whenever the user says "update the docs", "what's missing from the docs", "review last week's Slack for doc updates", "what should we have written down", "sweep Slack for doc updates", "what doc updates do we need", "anything to land in Confluence from Slack", or otherwise asks for a recurring documentation hygiene pass against recent team discussion. 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 in chat, this is the right home. Read-only by default; offers to stage a doc edit (or a draft message to the owning team) only after explicit confirmation.

Capture raw voice transcripts and brain dumps into a project's notes/ folder verbatim. Use this skill whenever the user says things like "here's my brain dump", "voice transcript", "dump notes", "capture this", "drop this into notes", or pastes a visibly long, unstructured, first-person block of text that reads like a spoken transcript (rambling sentences, repeated thoughts, no headings, conversational filler). Trigger even when the user does not explicitly say "notes" — if the input looks like a raw transcript, this skill is the right home for it.

Show what the plan is for the current project — what's in motion, what's next, what's blocked — by reading whichever planning sources the project uses (Jira, Confluence, a local plans/ folder, Slack-as-context, or some combination). Use this skill whenever the user asks "what's the plan", "what's next", "where are we on X", "show me the plans", "what's the plan for <area>", "catch me up on this project", "what's the status", or anything that asks for a synthesized view of the project's direction. Also use this skill in reconciliation mode when the user asks "sync plans", "reconcile with Jira", "reconcile the docs", "what's drifted", "what should graduate", "is the local plan still aligned with Jira", or anything that asks to compare local plans/ against external sources of truth. Trigger even when the user does not name a specific source — figuring out which sources apply is the skill's job. The skill reads the project's AGENTS.md to discover which sources are configured and then loads only the matching reference documents in plugin/skills/plan/.

Review a GitHub pull request against the project's own documentation — both directions. Fetch the diff from the GitHub repo(s) named in the project's AGENTS.md, cross-reference the change against the documented conventions (Confluence pages, local docs, plan files declared in AGENTS.md), and produce two outputs in one pass: (a) a PR review surfacing where the diff diverges from documented conventions, and (b) doc-update suggestions for patterns or decisions in the diff that aren't reflected in the docs yet. Use this skill whenever the user asks "review this PR", "review PR #123", "is this PR aligned with our docs", "check this PR against the spec", "what's wrong with this PR", "does this PR match our conventions", "check the open PRs for doc drift", "sweep open PRs", or pastes a GitHub PR URL and asks for feedback. Trigger even when the user doesn't name the skill — if they're handing you a PR and asking what it means against the project's documented direction, this is the right home. Read-only by default; any PR comment or doc edit requires explicit confirmation. Local checkout is out of scope in v1 — diffs come from the GitHub API.