Help us improve
Share bugs, ideas, or general feedback.
From runesmith-jira
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".
npx claudepluginhub runemarklabs/runesmith --plugin runesmith-jiraHow this skill is triggered — by the user, by Claude, or both
Slash command
/runesmith-jira:new-projectThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Scaffold a new project across Confluence and Jira.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
Scaffold a new project across Confluence and Jira.
Note: project and space creation require Atlassian admin permissions. Without admin rights, this skill detects the missing perms early and falls back to "use existing space + project" mode.
lib/atlassian-rest.mdlib/confluence-format.mdlib/credentials.mdlib/consent.mdlib/tokens.mdlib/comms-check.md - runs firstproject-overview, roadmap, known-issues, architecture-doclib/user-prompts.md - structured-input requirement for any user promptThis skill follows the marketplace-wide user-prompt standard in lib/user-prompts.md. Every user prompt MUST use the host client's structured input UI (single-pick, multi-pick, or text-input form). Never freeform plain-text yes/no questions. The only exception is the consent-trigger gate documented in lib/consent.md, which waits for user-initiated phrases like "make the ticket".
See lib/comms-check.md. Pause for to: user items.
GET /rest/api/3/mypermissions?permissions=ADMINISTER → look for ADMINISTER.havePermission == true.POST /wiki/rest/api/space only after explicit user confirmation.{SPACE_ID} and {PROJECT_KEY}.Use for:
Do not use for:
{LEAD_ACCOUNT_ID} via GET /rest/api/3/user/search?query=<email>com.pyxis.greenhopper.jira:gh-simplified-kanban-classic"Create Jira project {PROJECT_KEY} and Confluence space {SPACE_KEY}?" - wait for trigger phrase.
POST {ATLASSIAN_API_URL}/rest/api/3/project
{
"key": "{PROJECT_KEY}",
"name": "{name}",
"projectTypeKey": "software",
"projectTemplateKey": "com.pyxis.greenhopper.jira:gh-simplified-kanban-classic",
"leadAccountId": "{LEAD_ACCOUNT_ID}",
"description": "{description}"
}
Capture id and key from response.
POST {ATLASSIAN_API_URL}/wiki/rest/api/space
{
"key": "{SPACE_KEY}",
"name": "{name}",
"description": { "plain": { "value": "{description}", "representation": "plain" } }
}
Capture id. (v2 API has no space-create endpoint as of writing.)
For each, call sibling skill workflow with prefilled details and the new {SPACE_ID}:
project-overview → "Project Overview"roadmap → "Roadmap" (Now / Next / Later / Someday scaffold)known-issues → "Known Issues" (empty table)architecture-doc → "Architecture Overview" (empty ADR index)Each page-create inherits the consent state from this workflow's main consent. Do not re-prompt for each.
✓ Project initialized
Jira: {PROJECT_KEY} → {ATLASSIAN_API_URL}/jira/software/projects/{PROJECT_KEY}
Confluence: {SPACE_KEY} → {ATLASSIAN_API_URL}/wiki/spaces/{SPACE_KEY}
Pages: Project Overview, Roadmap, Known Issues, Architecture Overview
accountIdJira 403: "Need Jira admin to create projects. Switch to existing-project mode?"
Jira 400 - key in use: "Project key {PROJECT_KEY} already exists. Pick another."
Confluence 403 on space create: Same as above for Confluence admin.
Lead lookup empty: "No user found for that email. Use a different email or set ATLASSIAN_DEFAULT_ASSIGNEE_ACCOUNT_ID."
Partial failure (Jira created, Confluence failed): Report what succeeded, prompt to retry Confluence or roll back Jira manually.