How do I install the Multica Pm Artifact Publish skill?

Run npx skillmds@latest add it235/multica-pm-artifact-publish in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Multica Pm Artifact Publish safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Multica Pm Artifact Publish?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Multica Pm Artifact Publish free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Multica Pm Artifact Publish?

it235 (@it235) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Multica Pm Artifact Publish by it235

Name: Multica Pm Artifact Publish
Rating: 4.2 (5 reviews)
Author: it235

Multica Pm Artifact Publish

Land product requirement / PRD artifacts to the requirement knowledge platform (default Confluence). Used by @ProductManager to upload PRD and return a link for downstream design / dev / test consumption. Swappable platform.

it235 Updated Sep 22, 2026

File contents

Artifact · Requirement Sync

Purpose

Land product requirement artifacts to the team's unified requirement platform and let downstream retrieve them via a stable reference.

This skill decouples "platform integration" from "role prompt": the role prompt only says "produce PRD", not which platform. Changing companies (Wiki / Yuque / Feishu / internal KB) means editing only this skill, not the @ProductManager prompt.

Default platform: Confluence

Output: PRD (or MRD / dashboard spec / cross-system spec / acceptance checklist, by type).
Upload: create / update a page in Confluence, keeping G-/FR-/BR-/AC-/KPI-/OP-/RISK- ids and stable headings (see docs/en_US/gates-and-evidence.md AI-readable discipline).
Retrieve: downstream @Architect / @Designer / @FrontendDev / @BackendDev / @Tester read via the page link — the link is the stable reference.

Content spec (platform-independent part)

PRD at least contains (see @ProductManager role instruction): one-line definition, background, goals G- + KPI-, users & permissions, scope, FR-/BR-/AC-, field definitions, empty/error/no-permission states, RISK-/OP-, revision log.

Usage (role side writes only this line)

@ProductManager: "Produce PRD, land it via multica-pm-artifact-publish skill to the team requirement platform, and return the page link."

Swap platform (no role-prompt change)

Replace this skill's "default platform" section with your tool (Yuque / Feishu / Notion / internal Wiki), keeping the "upload + return stable link" interface unchanged.

Why it works

Platforms differ greatly across teams; hard-coding the platform name into the role prompt freezes it. Sinking it into the skill keeps the role's "what to produce" description stable while the platform swaps with the skill.

---name: multica-pm-artifact-publishdescription: Land product requirement / PRD artifacts to the requirement knowledge platform (default Confluence). Used by @ProductManager to upload PRD and return a link for downstream design / dev / test consumption. Swappable platform.---# Artifact · Requirement Sync## PurposeLand product requirement artifacts to the team's unified requirement platform and let downstream retrieve them via a stable reference.> This skill decouples "platform integration" from "role prompt": the role prompt only says "produce PRD", not which platform. Changing companies (Wiki / Yuque / Feishu / internal KB) means editing only this skill, not the @ProductManager prompt.## Default platform: Confluence- Output: PRD (or MRD / dashboard spec / cross-system spec / acceptance checklist, by type).- Upload: create / update a page in Confluence, keeping G-/FR-/BR-/AC-/KPI-/OP-/RISK- ids and stable headings (see `docs/en_US/gates-and-evidence.md` AI-readable discipline).- Retrieve: downstream @Architect / @Designer / @FrontendDev / @BackendDev / @Tester read via the **page link** — the link is the stable reference.## Content spec (platform-independent part)PRD at least contains (see @ProductManager role instruction): one-line definition, background, goals G- + KPI-, users & permissions, scope, FR-/BR-/AC-, field definitions, empty/error/no-permission states, RISK-/OP-, revision log.## Usage (role side writes only this line)> @ProductManager: "Produce PRD, land it via `multica-pm-artifact-publish` skill to the team requirement platform, and return the page link."## Swap platform (no role-prompt change)Replace this skill's "default platform" section with your tool (Yuque / Feishu / Notion / internal Wiki), keeping the "upload + return stable link" interface unchanged.## Why it worksPlatforms differ greatly across teams; hard-coding the platform name into the role prompt freezes it. Sinking it into the skill keeps the role's "what to produce" description stable while the platform swaps with the skill.

Frequently asked questions