create-jira-design-doc

A Jira task needs a design doc when it exhibits substantive complexity, such as cross-domain scope, multiple iterations, or high architectural impact. Evaluating these complexity triggers ensures formal documentation is produced only for significant changes.

To generate a design doc, evaluate the Jira task complexity and trigger the generation workflow to draft the document. The system maps existing Jira artifacts to standardized design doc sections like Overview, Context, Objectives, Design, and Alternatives, then links the draft back to the task.

A standardized design doc structure includes Overview, Context, Objectives, Design, and Alternatives sections. Artifact mapping translates Jira task drafts into these specific sections, constraining outputs to a consistent governance format.

Yes, the design doc governance workflow links the generated draft directly back to the original Jira task. This automated workflow proposes, drafts, and attaches the design doc to streamline project tracking and documentation governance.

Yes, you can evaluate Jira task complexity independently to decide if a design doc is required before drafting. The complexity assessment applies triggers like multi-domain scope and architectural impact to determine if generation is necessary.