confluence-documentation-patterns
Guide for creating and managing technical documentation in Confluence with Jira integration.
Boost efficiency with task automation and organizers.
Guide for creating and managing technical documentation in Confluence with Jira integration.
Create and edit JSON Canvas files (.canvas) with nodes, edges, groups, and connections. Use when working with .canvas files, creating visual canvases, mind maps, flowcharts, or when the user mentions Canvas files in Obsidian.
Quick reference for the Guidr GitHub Projects workflow. Learn status transitions (Todo → In Progress → Done), linking commits/PRs to tickets, and best practices for tracking work through development.
Contribute proactively to collaborative workflows.
JIRA issue operations: create, read, update, delete. ALWAYS use this skill when user wants to: (1) create new bugs/tasks/stories, (2) show/view/display/get/see/retrieve/check issue details or information, (3) look up issues, (4) update issue fields, (5) delete issues. Especially trigger when user says 'show me', 'get', 'view', 'details of', 'look at', or references 'the bug/issue/task we just created'.
Extract Power BI PBIR visuals into reusable templates. Use when users want to save an existing visual configuration as a template, standardize visual formats across projects, or add new visual types to the template library.
This skill should be used when managing the file-based todo tracking system in the .claude/todos/ directory. It provides workflows for creating todos, managing status and dependencies, conducting triage, and integrating with slash commands and code review processes.
Manages development tasks with integrated JJ workspaces, WebUI, and link management. Use when creating tasks, adding TODOs, working through task lists, managing references, or when the user mentions 'track' CLI, task management, or workspaces.
Create and maintain Architecture Decision Records (ADRs) in Confluence. Use when documenting technical decisions, architecture choices, technology selections, or when user mentions ADR, architecture decisions, technical choices, or design decisions.
Manage Confluence spaces for project documentation. Create, list, and delete spaces with templates. Use when setting up project documentation structure or managing Confluence content areas.
Generate user-story-organized task lists from implementation plans. Use when plan exists and user is ready for implementation, mentions "create tasks", "break down work", or asks "what tasks are needed" to implement the feature.
Create, update, and manage GitHub issues using MCP tools. Use this skill when users want to create bug reports, feature requests, or task issues, update existing issues, add labels/assignees/milestones, or manage issue workflows. Triggers on requests like "create an issue", "file a bug", "request a feature", "update issue X", or any GitHub issue management task.
Convert PRDs to tasks.json format for autonomous execution. Use when you have an existing PRD in spec/ and need to break it into executable tasks. Triggers on: convert prd to tasks, taskify this prd, create tasks from prd, generate tasks.json.
PROACTIVELY analyze completed Beads issues to identify patterns, tech debt, and gaps. Suggests new OpenSpec proposals based on discovered work. Use after closing issues or when user asks "what should we work on next?"
Task structure template and guidelines for tracking implementation work in tasks.md. Use when creating or updating tasks
This skill should be used when the user asks "what document type should I create", "create a bug ticket", "create a feature request", "should this be a task or initiative", "when to use an ADR", "track this bug", "log this tech debt", or needs help choosing between vision, strategy, initiative, task, backlog item, or ADR document types.
Audit de conformité d'une database Notion entière. Calcule le % de pages conformes, identifie les pages orphelines. Use when auditing databases or planning template migrations.
Work with Ticks issue tracker and Ticker AI agent runner. Use when managing tasks or issues with tk commands, running AI agents on epics, creating ticks from a SPEC.md, or working in a repo with a .tick directory. Triggers on phrases like create ticks, tk, run ticker, epic, close the task, plan this, break this down.
Automatically update sprint task status in JSON files and PROGRESS.md. Use when starting a sprint task (mark in-progress), completing a task (mark completed), or encountering blockers (mark blocked).
Interactive Intent approval. Review sections and mark status (locked/reviewed/draft). Use /intent-review <path> to review a specific file, or /intent-review to review Intent in current directory.
Tickly 작업 시작/재개할 때 현재 상태를 5줄로 고정 요약한다. "Tickly 상태 요약", "오늘 뭐부터?", "진행상황 정리" 같은 요청에 사용한다.