Story Description

Writes a full story description from the ticket context and its answered question sub-tickets.

By default the result replaces the ticket’s Description field and the story is assigned back to the initiator for review. When contentOutput targets Confluence, the description is instead published as a Confluence page, reviewer inline comments on that page are read before writing, and answers are posted back as comment replies.

Parameters

Configured via customParams in the agent JSON or the project .dmtools/config.js.

  • contentOutput — output routing block; see below.

contentOutput

  • contentOutput.targetjira_field (default, current behavior), confluence, or both.
  • contentOutput.field — tracker field for the jira_field/both targets. Default in this agent’s config: Description.
  • contentOutput.operationTypereplace (default) or append.
  • contentOutput.space / contentOutput.parentPageId — where the ticket’s page lives (required for Confluence targets).
  • contentOutput.pageTitleSuffix — appended to the page title.
  • contentOutput.includeInlineComments — fetch the page’s inline comments before the run and publish outputs/confluence_replies.json after it. Default: true.
  • contentOutput.updateTrackerField — for target: confluence, also write the page link into the tracker field. Default: true.
  • contentOutput.assignForReview — assign the ticket back to the initiator and move it to the review status after writing. Default: true.

Human doc: agents/docs/agents/story_description.md

Attributes

AttributeValue
JobTeammate
Configstory_description.json
ContextId
outputTypenone
skipAIProcessingtrue

Prompt snapshot

Full prompt / instruction set: agents/snapshots/story_description.md

Actions

preCliJSAction: preCliContentOutputSetup.js

Pre-CLI Content Output Setup — shared pre-action for content-generating

  • Source: agents/js/preCliContentOutputSetup.js
  • No detected file I/O or side effects.

postJSAction: writeContentOutput.js

Write Content Output — unified post-action for content-generating agents

  • Source: agents/js/writeContentOutput.js
  • Side effects:
    • post Jira comment
  • Parameters (customParams):
    • contentOutput

LLM step

  • outputType: none
  • Prompt snapshot: agents/snapshots/story_description.md

Custom params

  • contentOutput:

    {
      "target": "jira_field",
      "field": "Description",
      "operationType": "replace"
    }

Generated by js/agentDocGenerator.js

View the agent config on GitHub →

Generated from story_description.json in the agents repository and its human doc — edit either and the page follows. Last updated .