Record all significant decisions made during the project in a central, searchable log.
/plugin marketplace add marcel-Ngan/ai-dev-team/plugin install marcel-ngan-ai-dev-team@marcel-Ngan/ai-dev-teamThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Record all significant decisions made during the project in a central, searchable log.
| Tool | Purpose |
|---|---|
Atlassian:createConfluencePage | Create decision log page (if not exists) |
Atlassian:updateConfluencePage | Add new decisions to existing log |
Atlassian:getConfluencePage | Read current decision log |
Atlassian:searchConfluenceUsingCql | Find decision log page |
{
"cloudId": "{{confluence.cloudId}}",
"spaceId": "{{confluence.spaceId}}",
"spaceKey": "{{confluence.spaceKey}}"
}
# Decision Log - {{project.name}}
This page tracks all significant decisions made during the project.
---
## 2025-01-06 - [Decision Title]
**Decision:** [What was decided]
**Made By:** [Stakeholder / Agent name]
**Context:** [Why this decision was needed]
**Alternatives Considered:**
- [Option A] - [Why not chosen]
- [Option B] - [Why not chosen]
**Impact:** [What this affects]
**Related:**
- Jira: [PROJECT-XX]
- Confluence: [Link to spec]
---
## 2025-01-05 - [Previous Decision]
...
When adding a new decision:
## {{date}} - {{title}}
**Decision:** {{decision}}
**Made By:** {{decisionMaker}}
**Context:** {{context}}
**Alternatives Considered:**
{{#each alternatives}}
- {{option}} - {{reason}}
{{/each}}
**Impact:** {{impact}}
**Related:**
- Jira: {{jiraTicket}}
// First, find or create the decision log page
const searchResult = await Atlassian:searchConfluenceUsingCql({
cloudId: "{{confluence.cloudId}}",
cql: "space = '{{confluence.spaceKey}}' AND title = 'Decision Log'"
});
// If exists, update it; if not, create it
if (searchResult.results.length > 0) {
// Get current content and append
const page = await Atlassian:getConfluencePage({
cloudId: "{{confluence.cloudId}}",
pageId: searchResult.results[0].id
});
const newEntry = `
## 2025-01-06 - Dark Mode Implementation Approach
**Decision:** Use CSS custom properties with prefers-color-scheme media query
**Made By:** Marcel (Stakeholder)
**Context:** Needed to decide on technical approach for dark mode feature
**Alternatives Considered:**
- Separate CSS files - More maintenance overhead
- JavaScript toggle only - Doesn't respect system preference
**Impact:** Affects all UI components, styling architecture
**Related:**
- Jira: MDDEV-123
- Confluence: [Dark Mode Technical Spec]
---
`;
await Atlassian:updateConfluencePage({
cloudId: "{{confluence.cloudId}}",
pageId: page.id,
body: newEntry + page.body
});
}
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.