SkillMD SkillMD
light-dark-mode
Profile My skills Saved Collections Edit profile Submit a skill

← all plugins

Han Atlassian

by @testdouble · plugin · 6 skills

Atlassian-facing extensions to the Han suite. Adds markdown-to-confluence, which publishes a local Markdown file to a user-specified Confluence page; project-documentation-to-confluence, which runs the han-documentation project-documentation skill and then publishes the result there; investigate-to-confluence, which runs the core investigate skill and publishes the resulting investigation report t

Install the whole plugin (CLI)
npx skillmds add testdouble/work-items-to-jira npx skillmds add testdouble/markdown-to-confluence npx skillmds add testdouble/investigate-to-confluence npx skillmds add testdouble/code-overview-to-confluence npx skillmds add testdouble/plan-a-feature-to-confluence npx skillmds add testdouble/project-documentation-to-confluence
⬇ Download

Skills in this plugin

  1. ▌
    work-items-to-jira · testdouble bundle
    Break a work-items.md file (produced by /plan-work-items) into independently-grabbable Jira tickets, one per slice, in a single Jira project. Use when you want to turn a work-items file into Jira tickets, publish work items as Jira issues, or create implementation tickets that can be worked on and tracked in Jira. Requires a configured Atlassian MCP server. Does not produce the work-items file itself — use plan-work-items to break a plan into work items first. Does not post to GitHub — use work-items-to-issues for GitHub issues.
    218
    repo stars
  2. ▌
    markdown-to-confluence · testdouble
    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.
    218
    repo stars
  3. ▌
    investigate-to-confluence · testdouble
    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.
    218
    repo stars
  4. ▌
    code-overview-to-confluence · testdouble
    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.
    218
    repo stars
  5. ▌
    plan-a-feature-to-confluence · testdouble
    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.
    218
    repo stars
  6. ▌
    project-documentation-to-confluence · testdouble
    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.
    218
    repo stars