---

name: specification-to-jira-backlog description: "Convert an approved specification into a reviewed batch of Jira backlog issues."

Specification to Jira Backlog

Convert an approved specification into a reviewed batch of Jira backlog issues.

Required Aident Actions

• <action-tag>composio:jira_tools:jira_get_create_metadata_issue_type_fields</action-tag> (required inputs: projectIdOrKey, issueTypeId): Tool to retrieve field metadata for a specific issue type in a project. Use this to discover required fields, allowed values, and field configurations before creating issues of a specific type.
• <action-tag>composio:jira_tools:jira_bulk_create_issue</action-tag> (required inputs: issues): Creates multiple Jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.

Use Aident Loadout to read the current Action schema before constructing inputs. Check the required integration connection in Aident Vault. If an ActAction · Get Create Metadata Issue Type Fieldscost or risk, and wait for explicit user confirmation before execution.

Workflow

1. Confirm the requested outcome, source material, destination, audience, constraints, and acceptance criteria.
2. Apply the source-derived guidance below to cAction · Bulk Create Issue
3. Select only the Aident Actions whose documented effect directly advances the requested outcome. Do not invoke every listed Action by default.
4. Inspect the current schema and prepare the minimum valid input for each selected Action.
5. Preflight each selected Action. Execute it only after any required confirmation, in dependency order, and carry returned IDs or asset URLs into later steps.
6. Verify the returned IDs, URLs, statuses, or artifacts against the acceptance criteria. Report partial completion precisely and do not repeat paid or mutating calls blindly.

Source-Derived Guidance

• Require the approved specification content in the request; this workflow does not fetch a Confluence page.
• Derive epics and vertical implementation slices while preserving traceability to the source.
• Resolve required project fields, review the whole batch, then create no more than 50 issues per call.

Execution Boundaries

• Treat upstream provider-specific commands as background knowledge only. Execute the workflow through the exact Aident Actions above.
• Never request raw credentials in chat. Use Aident Vault connection flows for required accounts.
• Preserve user-provided wording, brand constraints, rights restrictions, and target identifiers. Do not invent authorization.
• Read current state before a mutation, state the exact target, and include a rollback or recovery step in the result.
• Stop when a required integration is disconnected, preflight rejects the input, the target is ambiguous, or the user declines a required confirmation.

Output

Return the execution plan, selected Action names, confirmed targets, Aident result identifiers or asset URLs, verification evidence, and any remaining blocked step.

Attribution

This Skill adapts the reviewed upstream workflow. See UPSTREAM.md for the pinned source and LICENSE.txt for the preserved license.