Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By RunemarkLabs
[RuneSmith] Jira ticket and project workflows: create tickets (Task/Story/Bug/Epic) with proper ADF formatting, report bugs with linked Confluence docs, scaffold new Jira projects, and read board status. All operations run against current Atlassian Cloud REST endpoints (no deprecated paths) with explicit consent gates before any push.
npx claudepluginhub runemarklabs/runesmith --plugin runesmith-jiraReport a bug - document it, publish to Confluence, create a Jira ticket.
Scaffold a new project in Confluence and Jira.
Get a quick project status from Jira.
Create, format, and push Jira ticket drafts for any issue type (Task, Story, Bug, Epic).
Report a bug - document it, publish to Confluence, create a Jira ticket. Use when the user says "there's a bug", "something broke", "this isn't working", "found an issue", "report a bug", or describes unexpected behavior. Also triggers on "file a bug", "bug report", or "this is broken".
Scaffold a new project in Confluence and Jira. Use when the user says "new project", "set up a project", "create a project", "scaffold", or wants to initialize Confluence and Jira for a new codebase. Also triggers on "start a new repo", "project setup", or "initialize project".
Get a quick project status from Jira. Use when the user says "what's the status", "where are we", "what's in progress", "what's in the backlog", "project update", "show me the board", or asks about current work state. Also triggers on "any blockers", "what's next", or "sprint status".
Create, format, and push Jira ticket drafts for any issue type (Task, Story, Bug, Epic). Includes JSON format specification, field guidance per issue type, and the push-to-Jira workflow. Trigger on "create a ticket", "make a Jira ticket", "write a ticket for this", "draft a ticket", "create a task for", "make the ticket".
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.
Comprehensive C4 architecture documentation workflow with bottom-up code analysis, component synthesis, container mapping, and context diagram generation
Battle-tested Claude Code plugin for engineering teams — 60 agents, 232 skills, 75 legacy command shims, production-ready hooks, and selective install workflows evolved through continuous real-world use
Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Comprehensive startup business analysis with market sizing (TAM/SAM/SOM), financial modeling, team planning, and strategic research
[RuneSmith] Workspace structure manager. Single source of truth for the canonical layout (_INBOX drop zone, plans/active with per-plan tickets/refs, notes, drafts, research, source-docs, archive/superseded, archive/tickets-pushed). /reallocate migrates from any prior shape (auto-snapshots) and pins folder-conventions into CLAUDE.md so future sessions stay coherent. /inbox classifies dropped files and routes them to their canonical homes on consent.
[RuneSmith] Builds the {PROJECT}.cc/ Claude Code monorepo head at your workspace root and installs the project-boundary guardrail that constrains Claude Code sessions to their launch project. /bootstrap-cc writes the CC head (CLAUDE.md, .claude/ scaffolding, comms folder, marker files) and project-level settings; /guardrail installs the user-level permission rules and PreToolUse hook that block cross-project filesystem reads. Idempotent — safe to re-run.
[RuneSmith] Populates an AI Operations Confluence space from six template pages (Quick Start, Full Integration, Architecture, Best Practices, FAQ, Reference). All canonical tokens ({COMPANY}, {SITE}, {SPACE_KEY}, {PROJECT_KEY}, etc.) are substituted at publish time so the same templates work for any tenant. Space must already exist in Confluence — skill is a one-shot populator.
[RuneSmith] Confluence page authoring with proper storage XHTML conversion. Skills cover feature specs, architecture decision records (ADRs), project overview landing pages, append-only decisions logs, known issues trackers, roadmap pages, and session logs. Drafts in markdown locally, converts and publishes on user consent. Optionally pulls plans/active/ as prefill source.
[RuneSmith] Foundation plugin. Manages credentials (Atlassian, GitHub, plugin sources), installs and syncs plugins from the marketplace, and runs chat-first /plan sessions before any writes happen. Install this first — every other RuneSmith plugin depends on its credential and plugin-management primitives.
Claude plugin marketplace for planning, Atlassian (Jira + Confluence) integration, Claude Code workspace bootstrap, AI Operations documentation, and development tooling. Generic and single-tenant configurable per project - every tenant detail comes from user input or .credentials at runtime.
Built and maintained by Runemark Labs. Apache-2.0 licensed.
Eight plugins, ~30 skills total, ~30 commands. Install only what you need.
| Plugin | Skills | Purpose |
|---|---|---|
runesmith-core | plan, install, sync, setup | Foundation. Credentials, plugin management, chat-first planning. Required base. |
runesmith-workspace | reallocate, inbox | Workspace folder structure: _INBOX/ drop zone, plans/active/, plans/archive/, snapshots. |
runesmith-cc | bootstrap-cc, guardrail | Build the {PROJECT}.cc/ Claude Code monorepo head with comms folder; create or clone repos via PAT. Install the user-level project-boundary guardrail that constrains CC sessions to their launch project. |
runesmith-jira | ticket, bug-report, project-status, new-project | Jira tickets and project basics with current Cloud REST endpoints. |
runesmith-confluence | feature-doc, architecture-doc, project-overview, decisions-log, known-issues, roadmap, session-log | Confluence pages with storage XHTML conversion. |
runesmith-sprint | enable, disable, start-sprint, sprint-status, check-comms, plan-to-tickets | Sprint workflow + Cowork↔Claude Code interconnect via comms protocol. |
runesmith-aiops | bootstrap-aiops | Populate an AI Operations Confluence space from six template pages. |
runesmith-devtools | help, plugin-builder, tech-debt, skill-updater | Developer helpers for the marketplace itself. |
comms/, Claude Code executes. No Atlassian dependency./runesmith-sprint:enable and /runesmith-sprint:disable./plugin marketplace add runemarklabs/runesmith
/plugin install runesmith-core@runesmith
/plugin install runesmith-workspace@runesmith
/plugin install runesmith-cc@runesmith
/plugin install runesmith-jira@runesmith
/plugin install runesmith-confluence@runesmith
/plugin install runesmith-sprint@runesmith
/plugin install runesmith-aiops@runesmith
/plugin install runesmith-devtools@runesmith
After install, run /runesmith-core:setup to configure credentials. See INSTALL.md for full options.
.plugin files (Cowork desktop).plugin zips are not committed to this repo - they're generated on demand. Build them first:
python scripts/build.py # cross-platform; recommended on Windows
# or:
bash scripts/build.sh # Unix/Mac
This produces runesmith-*.plugin files in ./dist/ (gitignored). Drag those into the Cowork plugin sidebar to install.
Custom output directory:
python scripts/build.py path/to/output/
Every write skill follows the same gate:
to: user items first..credentials and project values./drafts/, /plans/active/, or chat.No write happens without the trigger. No skill talks to deprecated endpoints. No body is markdown.
Cowork ↔ Claude Code communicate via files in {PROJECT}.cc/comms/. CC writes ambiguity, blockers, or user-action requests to comms/open/; Cowork triages on /runesmith-sprint:check-comms or any planning interaction (check-on-entry pattern). User is reached only through Cowork - CC never asks the user directly.