Draft test plans from Jira tickets and push cases to Zephyr

QA engineer Alicia Gonçalves runs Claude Code skills inside her Obsidian vault that pull a Jira ticket's context and Confluence references, write a test plan from her templates, and publish cases to Zephyr.

Done with

Claude Code

Apps touched

Jira

ReportedSep 28, 2026

What they did

Gonçalves, a QA engineer writing on the He4rt community blog, keeps her notes in Obsidian as Markdown so AI tools can read them. She wrote three Claude Code skills. One takes a Jira ticket ID, fetches the ticket, searches the Confluence spaces named in her CLAUDE.md for reference material, and writes a test plan note using her own templates for technical tasks and for business discovery work. A second uses the Atlassian MCP to find every ticket flagged as needing a test plan and adds it to a Markdown file that drives an Obsidian Kanban board. A third pushes the planned test cases into Zephyr, her test management tool. Because no plugin existed, she also built two small Obsidian plugins: one opens a terminal in the vault for Claude Code, the other lists and runs her skills.

How it went

She says the flow is now her routine for epics and for technical tasks such as database migrations, consumers and APIs. She gives no numbers on time saved. Reviewing the generated plans is still manual: she collects feedback from her team on scenarios, test data and clarity, and keeps editing the templates based on what the reviews catch. The plugins are not in the Obsidian community store and are not in a final version.

Worth knowing

The post is in Portuguese; an English version is on the AWS Community Builders blog. The skills depend on an Atlassian MCP connection and on the Confluence spaces being listed in CLAUDE.md, and the setup assumes you already keep your templates as Markdown. The author treats the output as a draft the team reviews, not a finished plan.

Try it yourself withTry it withClaude Code

6 parts to fill in

Here is Jira ticket [ID]. Fetch it through [the Atlassian MCP], then look for related documentation in [the Confluence spaces listed in CLAUDE.md]. Using [my test plan template file], write a test plan as a new Markdown note in [my vault folder] covering scope, risks and mitigations, test layers, scenarios and test data. Mark any scenario you are unsure about with a question for me. Show me the plan and stop; only after I approve should you publish the cases to [Zephyr or my test management tool].

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.