Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From ai-pm-assistant
Creates a structured decision log from project changes, scope revisions, or PM decisions. Extracts area, original plan, revised plan, reason, and impacts into a table.
npx claudepluginhub erica-j-01/ai-pmHow this skill is triggered — by the user, by Claude, or both
Slash command
/ai-pm-assistant:decision-log <decision context, change description, or prior skill output><decision context, change description, or prior skill output>This skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
$ARGUMENTS
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Explores codebases via GitNexus: discover repos, query execution flows, trace processes, inspect symbol callers/callees, and review architecture.
Share bugs, ideas, or general feedback.
$ARGUMENTS
If no input is provided above, ask: "Describe the decision or change - what was originally planned, what changed, and why? Include who proposed the change if known."
From the input, identify every decision or plan change that needs logging. For each one, extract:
[TBC] if not yet confirmedIf a field cannot be determined from the input, write [TBC].
Project: [Extract from input, or write "Not specified"] Date: [Today's date] Prepared by: [PM or role if known]
| Area | Original Plan | Revised Plan | Reason | Change Proposed By | Delivery Impact | Technical Impact | Product Owner Impact | Cost Impact | Change Status | Change Approved By |
|---|---|---|---|---|---|---|---|---|---|---|
| [Area] | [What was planned] | [What changed to] | [Why] | [Who] | [Timeline/milestone effect] | [Tech effect] | [PO/roadmap effect] | [Budget effect] | Proposed / Under Review / Approved / Rejected | [Who approved] |
One row per decision. Add rows as needed.
Ask the user where they want it saved:
"Where would you like me to save this? I can save it locally or push it directly to any platform you have connected via MCP."
Local
- Local file - saved to
clients/CLIENT/project-artefacts/YYYY-MM-DD-decision-log.mdConnected platforms (via MCP) 2. Confluence - published as a new page (I'll ask for your domain, space, and parent page) 3. Google Drive - saved as a new Doc (I'll ask for the folder) 4. Notion - created as a new page (I'll ask for your workspace and parent page) 5. Jira - added as a comment or description on a relevant issue (I'll ask for the issue key)
No save 6. Clipboard only - leave it here for you to copy manually
Do not save or publish anything until the user confirms the destination.