'confluence' 검색 결과

Push markdown files to Confluence - update existing pages or create new ones under a parent page. Use this skill whenever the user wants to publish markdown to Confluence, update a Confluence page from a local .md file, create new Confluence pages, or batch-create pages. Also triggers on "push to confluence", "update confluence page", "create confluence page", "publish to confluence", "sync to confluence", or any mention of uploading/pushing markdown content to Confluence. Use this even when the user says "put this on confluence" or "make a confluence page for this".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Organize Confluence documentation with clear page hierarchies, reusable templates, and access plans. Create and update pages, embed Jira reports, and audit existing content to identify outdated material and establish review responsibilities.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Restructure a team's Confluence space
• Standardize meeting notes and decision logs
• Embed Jira issues and charts in documentation

Find and manage documentation in Confluence through Atlassian MCP, a connection to Atlassian tools. Search in plain language, read and summarize pages, create or update structured content, browse spaces, and add page comments.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Finding and summarizing onboarding documentation
• Adding a section to existing API documentation
• Creating an architecture decision record in a specified space

Produces a progressive-disclosure overview of unfamiliar code or a pull request's changes with code-overview and publishes the resulting overview to a user-specified Confluence location. Use when the user wants code or a PR explained, oriented, or made sense of AND the overview posted to a Confluence space or page. Requires a configured Atlassian MCP server. Does not produce the overview to a local file only — use code-overview. Does not publish an arbitrary existing markdown file — use markdown-to-confluence. Does not document an already-understood feature to Confluence — use project-documentation-to-confluence. Does not root-cause a bug to Confluence — use investigate-to-confluence. Does not plan or specify a new feature to Confluence — use plan-a-feature-to-confluence. Does not publish to Jira — use work-items-to-jira.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Confluence CQL search + space list + saved-filter + export via the confluence-as wrapper. Triggers: 'search confluence', 'find pages where X', 'cql for ...', 'export search results', 'list spaces', 'manage saved filters'. CQL injection-safe via the shared sanitizer. NOT for single-page CRUD (mk:confluence-page); NOT for bulk write ops (mk:confluence-bulk).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Assess Airflow Improvement Proposals by comparing Confluence specifications with pull requests, commits, and codebase files. Produce evidence-backed progress reports showing delivered items, remaining work, and specification updates needed across one or more proposals.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Check implementation progress for an Airflow proposal
• Compare specification deliverables with shipped code
• Compile a progress report across multiple proposals

Connect AI agents to Jira and Confluence through MCP, a protocol for accessing external tools. This skill guides issue searches and updates, page management, sprint workflows, authentication setup, and troubleshooting of Atlassian integrations.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find Jira issues by assignee or status
• Search and update Confluence pages
• Turn meeting notes into Jira ticket updates

Turn previously retrieved Jira requirements and Confluence documents into a structured implementation plan. Tasks are grouped into frontend, backend, and infrastructure work, with architectural reasoning, blocking dependencies, and risks paired with mitigation measures.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Creating an implementation plan from Jira requirements
• Dividing work across frontend, backend, and infrastructure
• Identifying blocking dependencies between tasks

Manage organization-wide Atlassian administration, including user onboarding and removal, group permissions, sign-in settings, and app integrations. It provides workflows for access reviews, configuration changes, operational checks, and recovery planning, primarily through admin consoles and REST APIs.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Onboarding employees and removing access for departing staff
• Reviewing Jira and Confluence permissions
• Planning single sign-on and external integrations

Create and maintain reusable Jira issue descriptions and Confluence page structures for meeting notes, requirements, decisions, and other shared documents. The skill guides template design, generates Confluence markup, and covers validation, versioning, deployment, and usage instructions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Standardizing meeting notes and decision logs
• Creating Jira bug report and user story templates
• Designing shared project document layouts

Creates or updates project documentation for a feature, system, or component and publishes it to a user-specified Confluence location. Use when the user wants feature or system documentation written to Confluence, posted to a Confluence space or page, or synced to a Confluence location. Requires a configured Atlassian MCP server. Does not document to local files only — use project-documentation for that. Does not publish an arbitrary existing markdown file — use markdown-to-confluence for that. Does not plan or specify a new feature to Confluence — use plan-a-feature-to-confluence for that. Does not create architectural decision records — use architectural-decision-record. Does not create coding standards — use coding-standard. Does not produce runbooks — use runbook.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Runs an evidence-based investigation of a bug, failure, or unexpected behavior with investigate and publishes the resulting investigation report to a user-specified Confluence location. Use when the user wants something debugged, diagnosed, or root-caused AND the findings posted to a Confluence space or page. Requires a configured Atlassian MCP server. Does not investigate to a local file only — use investigate. Does not publish an arbitrary existing markdown file — use markdown-to-confluence. Does not document an already-understood feature to Confluence — use project-documentation-to-confluence. Does not plan or specify a new feature to Confluence — use plan-a-feature-to-confluence. Does not publish to Jira — use work-items-to-jira.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Convert Confluence pages to clean GitHub-Flavored Markdown files. Use this skill whenever the user wants to pull a Confluence page into the local repo, convert Confluence content to markdown, download a spec from Confluence, or batch-convert multiple pages. Also triggers on Confluence URLs, page IDs, or phrases like "pull this page", "download this spec", "confluence to md". Use this even if the user just pastes a Confluence URL and says something vague like "get this" or "convert this".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Organize Confluence team wikis and project documentation with clear page hierarchies, labels, and templates. Use macros, built-in content tools, to assemble indexes and reports, with REST API guidance for creating and updating pages.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Reorganizing a team wiki
• Building an index of decisions and runbooks
• Standardizing recurring meeting notes

Manage knowledge bases and documentation with Confluence Cloud. Use when a user asks to create or manage Confluence spaces, pages, and blogs, build documentation systems, automate page creation from templates, use Confluence REST API v2, manage page trees and hierarchies, set up permissions, integrate Confluence with Jira or other tools, generate reports from Confluence data, build macros or Forge apps, or migrate content between spaces. Covers content management, API automation, templates, and Atlassian ecosystem integration.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Confluence page CRUD via the confluence-as wrapper. Triggers: 'create page in SPACE', 'show me page 12345', 'update title of page 12345', 'delete page 12345', 'page hierarchy under 12345', 'copy page 12345 to SPACE'. NOT for bulk ops on 10+ pages (mk:confluence-bulk); NOT for spec analysis (mk:confluence-spec-analyst); NOT for comments/attachments/labels (mk:confluence-collaborate).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Routing skill — recommends the correct mk:confluence-* leaf for any Confluence Cloud task. Triggers: 'confluence', 'wiki page', 'spec page', ambiguous Confluence intent. NOT an executor — every actual operation forks via a leaf skill.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Builds a feature specification from scratch with plan-a-feature and publishes it to a user-specified Confluence location, posting the spec as a parent page and each companion artifact (decision log, team findings, technical notes) as a child page beneath it. Use when the user wants a new feature planned, designed, scoped, or specified AND posted to a Confluence space or page. Requires a configured Atlassian MCP server. Does not plan to local files only — use plan-a-feature. Does not publish an arbitrary existing markdown file — use markdown-to-confluence. Does not refine or stress-test an existing plan — use iterative-plan-review. Does not document already-built features to Confluence — use project-documentation-to-confluence.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Confluence page CRUD via confluence-as: create/show/update/delete, hierarchy, copy. NOT bulk (mk:confluence-bulk), spec analysis (mk:confluence-spec-analyst), or comments (mk:confluence-collaborate).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Deep spec analysis on a Confluence page. Reads page (+ children) via the confluence-as wrapper, produces a structured Spec Research Report with requirements, acceptance criteria, gaps, ambiguities, and suggested user stories for human review. Read-only — does NOT create Jira tickets. Triggers: 'analyze spec for PAGE-ID', 'extract requirements from confluence page', 'spec research on URL'. NOT for raw page CRUD (mk:confluence-page); NOT for ticket complexity scoring (mk:planning-engine).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Manage Confluence collaboration surface via the confluence-as wrapper: comments, attachments, labels, watchers. Triggers: 'add comment to page 12345', 'upload attachment to page 12345', 'label page 12345 as urgent', 'watch page 12345'. Inline-vs-footer comment safety enforced. NOT for page CRUD (mk:confluence-page); NOT for bulk ops (mk:confluence-bulk).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Bulk Confluence operations on 10+ pages via the confluence-as wrapper: bulk-label / bulk-move / bulk-delete. Dry-run is MANDATORY first. Triggers: 'bulk update N pages', 'mass label', 'delete all pages matching CQL', 'bulk-move pages to PARENT'. NOT for single-page ops (mk:confluence-page); NOT for comment/attachment ops (mk:confluence-collaborate).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Coordinate project delivery by routing requests to eight specialist skills or running a verified delivery workflow. Use live Jira data for progress analysis and completion forecasts, with recorded evidence and checks before tasks are closed.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Analyze sprint progress and forecast completion ranges
• Produce project health reports from live Jira data
• Route Jira permission and configuration reviews

Publishes a local Markdown file to a user-specified Confluence location, creating a new page or updating an existing one through the Atlassian MCP server. Use when the user wants to post, publish, push, or sync a Markdown file to a Confluence space or page. Requires a configured Atlassian MCP server. Does not write or generate the Markdown itself — point it at an existing file, or use project-documentation-to-confluence for the document-then-publish flow, or plan-a-feature-to-confluence for the plan-then-publish flow. Does not publish to Jira — use work-items-to-jira.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.