Create Test Plan

Shared writing standard

Before you write user-facing prose or artifact prose, read and apply the shared ASD-STE100 skill. Preserve this skill's required output contract.

If the shared skill or profile is unavailable, state that limit in the response. This notice is the only exception to an exact-output rule. Then apply ASD-STE100 as closely as possible from the available context.

Turn the work just done in this session into a QA Test Plan and append it to the end of the Jira ticket's description. This runs at the tail of a coding session — the agent already has the context of what changed and what is risky. The skill's job is to shape that context into the fixed Test Plan format and write it to Jira safely.

Invocation: /create-test-plan [ticket-key]

• ticket-key — optional. Normally inferred from the current git branch (see Step 2).

Step 0 — Resolve the Jira cloudId

The Atlassian MCP calls need a cloudId.