RampStack skills in Jira.

Visual demonstration

What this looks like in practice.

# Atlassian remote MCP, called via the agent runtime
mcp.atlassian.create_issue({
  project: "BRAND",
  issuetype: "Epic",
  summary: "Phase 2: Direction",
  customField_phase: "Direction",
  customField_locked: false,
  customField_approver: "brand-owner@example.com"
})

# Repeat per phase, link Stories with Epic Link

# Atlassian official CLI for bulk Confluence content edits
acli login --site rampstack.atlassian.net
acli confluence page create \
  --space BRAND \
  --title "Atlas brief v2" \
  --file ./brief.md

CLI alternative

Atlassian CLI for bulk operations.

The shape

Brief into Jira primitives.

The Epic carries the brief. Stories link to the Epic via Epic Link. Custom fields hold the axis positions. The workflow gains a Direction review step. JQL pulls cross-project work that answers the brief or breaks it.

Templates

Copy these into the project configuration.

# Brief synthesis

[One paragraph in present tense describing what
this combination produces in practice.]

# Axis positions

- Tone: [position] because [one-sentence rationale]
- Aesthetic: [position] because [one-sentence rationale]
- Relationship: [position] because [one-sentence rationale]
- Sensory: [position] because [one-sentence rationale]

(Custom fields above mirror these for queryability.)

# Won't do

- [specific phrasing, structure, or visual move
  this brief excludes]
- [next item]
- [next item]

# Inspiration references

(Use the Web Links section of this Epic for URLs.
Add a one-sentence note per reference about what
specifically resonates.)

# Open questions

- [anything still unresolved that downstream Stories
  will need answered]

# All open Stories under one brief
"Epic Link" = PROJ-123 AND statusCategory != Done
ORDER BY priority DESC, created DESC

# Stories that have not been graded yet
"Epic Link" = PROJ-123
  AND "Direction status" is EMPTY
  AND statusCategory != Done

# Stories that drifted, surfaced for review
"Epic Link" = PROJ-123
  AND "Direction status" = "Drift"

# Cross-project work tagged with one tone position
project in (WEB, APP, MKT)
  AND Tone = "Professional"
  AND statusCategory = "In Progress"

# Stories under the brief that violate the rejection
# list (as flagged by the Direction-status review)
"Epic Link" = PROJ-123
  AND "Direction status" = "Drift"
ORDER BY updated DESC

Story workflow states

Backlog  ->  Refinement  ->  Direction review  ->  Ready
                                    |
                                    +->  Drift  (loop back to
                                                 Refinement)

Transition: Direction review -> Ready
  - Validator: "Direction status" must equal
    "Aligned" OR "Needs review"
  - Post-function: set assignee to the Story owner

Transition: Direction review -> Drift
  - Used when the reviewer judges the Story breaks the
    brief. Story returns to Refinement with a comment
    explaining the gap.

Issue types in the scheme

Epic           - carries the brief, axis fields required
Story          - inherits axis defaults from Epic Link
Bug            - axis fields optional (often N/A)
Task           - axis fields optional
Sub-task       - inherits from parent Story

Screen configuration

Create Issue (Story) screen
  - Summary, Description, Epic Link (required)
  - Tone, Aesthetic, Relationship, Sensory
    (defaulted from Epic Link, editable)
  - Direction status (set during refinement)

Edit Issue (Story) screen
  - Same fields as Create
  - Plus Direction status, editable by reviewers

Composition

Which skills feed the Jira integration.

The brief itself comes from creative-direction. Stories that produce voice copy consume the output of brand-voice. Stories that produce identity work consume brand-identity. Conversion-focused work consumes landing-page-copy. The dependency chain is identical to the agile-creative-direction integration; this page just translates it into Jira's vocabulary.

Frequently asked questions.

Where does a creative-direction brief belong in Jira?

On the Epic. The brief synthesis becomes the Epic description, the four axis positions become custom fields on the Epic, and the rejection list becomes a structured section in the description. Stories link to the Epic via the Epic Link field, which Jira indexes natively, so a single JQL query returns every Story under the Epic answering one brief.

What custom field type works best for axis positions?

Single-select fields, one per axis (Tone, Aesthetic, Relationship, Sensory). Single-select gives you the JQL queryability of structured values without the cardinality problem multi-select introduces. Configure the option list per axis (Professional, Conversational, Playful, Provocative for Tone; the corresponding sets for the other three) and apply the fields to the Epic issue type via the screen scheme.

Can JQL find stories that break the brief's rejection list?

Not directly via JQL alone, since the rejection list is freeform text. Teams handle this with a Single-select Direction-status field on Stories with values like Aligned, Drift, Needs review. A workflow transition or an automation rule sets Direction-status during refinement based on a manual judgment call. JQL then queries that field. The brief is the source of truth; the field is the queryable index of human review against it.

What is the most common Jira-specific failure of this integration?

Custom fields applied to the Epic but not surfaced on the Create Story screen. Stories get filed without axis context, the JQL filters return incomplete results, and the team loses confidence in the integration within a sprint or two. Confirm the screen scheme exposes the axis fields on every relevant create and edit screen, not just on the Epic detail view.