---

name: create-a-jira-project-from-template description: "Create one Jira project from a verified template and approved ownership settings."

Create a Jira Project from Template

Create one Jira project from a verified template and approved ownership settings.

Required Aident Actions

• <action-tag>composio:jira_tools:jira_get_project_templates</action-tag> (required inputs: inspect the current schema): Retrieves available Jira project templates for creating projects. Returns template keys that can be used with the Create Project action. Use this action when you need to discover valid project template keys before...
• <action-tag>composio:jira_tools:jira_create_project</action-tag> (required inputs: key, name, project_type_key, project_template_key, lead_account_id): Creates a new Jira project with required lead, template, and type configuration.

Use Aident Loadout to read the current Action schema before constructing inputs. Check the required integration connection in Aident Vault. If aAction · Get Project Templatesed target and quoted cost 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 crAction · Create Projectn.
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

• Resolve a live template key and confirm project type, lead, key, and name.
• Show the complete project configuration before creating the project.

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.