Step 3: Create Jira Tickets for the Stories

Push your stories into Jira and link them to an epic.

What you're doing in this step

Get traceability set up before development starts. Doing tickets in bulk now beats creating them one-at-a-time over the next two weeks.

Recommended prompts

Use one of these to do the work in your IDE

Open the template to read it in full. Click Copy prompt to grab it (with your stack values pre-filled where they apply) — then paste into Claude Code, Cursor, or wherever you build.

Primary recommendation 5 min setup

Jira Ticket Manager Skill

Claude Code skill for creating, updating, and querying Jira tickets via the Jira MCP server.

claude-codemcp

View skill

Skill· Skill 10 min setup, 30s per story

Jira Push (Bulk Stories + Test Cases)

Skill for bulk-pushing elaborated stories and their test cases into Jira as Story + sub-task hierarchies. Always dry-runs first; never overwrites silently.

Use this when: You have a folder of elaborated stories + test cases and want to bulk-push them as Story + sub-task hierarchies

claude-codemcpjira

View skill

Recommended MCP configs

Wire these tools into Claude Code first

MCP servers give Claude Code direct access to external systems (Jira, browsers, databases). Configure once.

MCP config· MCP config 5 min setup

Jira MCP for Evoke

Pre-configured Jira MCP server for Claude Code with Evoke's standard project setup.

claude-codemcp

View config

When you're done

Verify these in your own work before moving on

This is a checklist for you to mentally tick off in your repo and IDE — the site doesn't track it, you do.

Epic created with PRD link in description
Every story is its own ticket linked to the epic
Tickets have acceptance criteria copied into the description
Initial estimates set (rough is fine — you'll refine)

Common pitfalls

What goes wrong at this step

Skipping the epic — it's free traceability
Hardcoding labels that drift from the team's convention — check what the team already uses

← Previous step