CI/CD artifact-orchestration skill (placeholder shell): after G2 PASS and code push, call the underlying CI/CD platform skill to trigger dev/sit builds, write back to the Issue, and return the deploy URL. Parameters auto-discovered from the CI API; the orchestration layer never hardcodes parameter names. Concrete…
Platform-layer skill (placeholder shell): read/write capability for Confluence / Wiki-class systems — pull existing pages for Agents to consume, land PRD / design artifacts and return a stable page link. Decoupled from the Issue system; called by artifact-orchestration skills. Concrete platform URLs / spaces / parent…
Platform-layer skill (placeholder shell): read/write capability for CI/CD systems (Jenkins-class) — trigger parameterized builds, poll status, fetch console logs. Parameters are auto-discovered; never hardcode. Credentials injected via runtime env. Concrete CI URL / Job list in config.yaml, never in role prompts.
Platform-layer skill (placeholder shell): read/write capability for Issue-tracking systems (JIRA-class) — Issue query, upstream-Wiki-link parsing, Story creation, transition, scheduling, description write-back, notification. Decoupled from the Wiki platform; called by artifact-orchestration skills. Concrete URLs /…
Gatekeeping function: objectively check whether an artifact satisfies the acceptance criteria. Triggered by the Leader to rerun at gate points (G1/G2/G3); members can also use it for self-check. Used for design review / implementation acceptance / test-report review.
Skill library management—batch import/export and bind SKILL.md to the Multica skill library; operates on the templates/ /skills directory. The preferred mount for @Leader.
Frontend artifact sync—push the frontend deliverable set (page/component/state/style) and run-url to Multica frontend-artifact (product-requirement mapping); the preferred mount for @FrontendDev.
Tester T1/T2/T3 orchestration and gatekeeping—sub-skill routing, assembling materials from Issue comments, and BLOCKED interruption list. Integrates acceptance-verifier-squad; the preferred mount for @Tester.
T1 test design—AC↔design traceability, case templates and coverage self-check, Confluence master copy, XMind/JIRA after passphrase, Apifox scenarios and e2e planning. Integrates ac-design-trace + test-case-generator-squad.
T3 API automation—only after G2.5 PASS; run Apifox scenarios by contract, join overall verdict with UI side. Requires env + Apifox three IDs complete; no local mock as substitute.
T3 UI automation—only after G2.5 PASS; run pytest+Playwright 1:1 by MULTICA §2 e2e path and T1 cases; join overall verdict with API side. No local mock.
Land technical design artifacts to the code repo or knowledge platform (default Git repo / Confluence). Used by @Architect to upload technical design for downstream implementation and test consumption. Swappable platform.
★not rated 212▲
+17 1mo agoA45 tokens
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: