document-ticket

Post a deliverables URL comment to a specified Jira ticket.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ryanallen/product-studio --skill document-ticket
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: document-ticket
Source: https://github.com/ryanallen/product-studio/tree/main/.claude/skills/document-ticket
Command: npx skills add https://github.com/ryanallen/product-studio --skill document-ticket

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of updating Jira tickets with links to project deliverables, ensuring stakeholders have easy access to the latest project outputs.

Core Features & Use Cases

  • Automated Commenting: Posts a standardized comment containing the deliverables URL directly onto a specified Jira ticket.
  • Centralized Information: Keeps project documentation and deliverables linked within the project management tool.
  • Use Case: After a development sprint, the deliverables are deployed. This Skill can automatically update the corresponding Jira epic or story ticket with the link to the deployed version.

Quick Start

Post a comment on ticket PROJ-123 with the deliverables link.

Frequently Asked Questions about document-ticket

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate posting deliverables links to Jira tickets?

Automating deliverables links to Jira tickets involves posting a standardized comment containing the project URL directly onto a specified issue. This Skill retrieves the base URL from a local paths.md file, appends the project path, and updates the Jira ticket automatically.

What is the best way to update Jira epics with deployed project documentation?

Updating Jira epics with deployed project documentation is done by posting a comment containing a direct deliverables URL. This provides stakeholders centralized access to completed work and project outputs directly within the project management tool.

Do I need a local paths.md file to post project URLs to Jira?

A local paths.md file is required to post project URLs to Jira. The Skill retrieves the base deliverables URL from this file and appends the specific project path to form the complete link before adding the comment to the Jira ticket.

Can I use this Skill to link completed sprint deliverables in Jira issue tracking?

You can use this Skill to link completed sprint deliverables in Jira issue tracking. After a development sprint deploys outputs, it automatically posts the direct access link to the deployed version as a comment on the corresponding Jira epic or story ticket.

How does the Skill construct the deliverables URL for Jira comments?

The deliverables URL for Jira comments is constructed by retrieving a base URL from a local paths.md file. The Skill then appends the specific project path to this base URL to form the complete link added to the Jira issue tracking ticket.

When should I not use automated commenting for Jira project status updates?

Automated commenting for Jira project status updates should not be used when a local paths.md file containing the base deliverables URL is unavailable. Without this dependency, the Skill cannot construct or post the required deliverables links to the specified Jira ticket.