3p-update

Synthesize Asana tasks, Jira issues, and Slack messages into Progress/Plans/Problems updates.

1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/al-stev/field-eng-skills --skill 3p-update
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: 3p-update
Source: https://github.com/al-stev/field-eng-skills/tree/main/.claude/skills/3p-update
Command: npx skills add https://github.com/al-stev/field-eng-skills --skill 3p-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provide fast, factual Progress / Plans / Problems summaries so Solutions Engineers can communicate customer status without manual cross-referencing across Asana, Jira, and Slack.

Core Features & Use Cases

  • Cross-source synthesis: Correlates Asana tasks, Jira issues, and Slack signals to populate Progress, Plans, and Problems with concrete citations.
  • Per-customer and portfolio modes: Generate a single-customer 3P or a cross-customer portfolio summary for weekly reports or meeting prep.
  • Publish option: Optionally convert the 3P into simple HTML and publish to Confluence for sharing.
  • Use case: Prepare a one-page SE status update for a customer meeting that cites recently resolved Jira issues, completed Asana tasks, and any Slack escalations.

Quick Start

Run /3p-update CustomerName to generate a concise Progress / Plans / Problems update synthesized from available Asana, Jira, and Slack data.

Frequently Asked Questions about 3p-update

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

FAQPage Schema
How do I generate a 3P status update from Asana, Jira, and Slack data?▼

To generate a 3P status update, run the command with a customer name to synthesize Asana tasks, Jira issues, and Slack messages into a concise Progress, Plans, and Problems summary with concrete citations.

Can I publish 3P status reports directly to Confluence?▼

Yes, you can optionally publish 3P status reports to Confluence. The Skill converts the update into simple HTML and shares it directly, provided Confluence publishing credentials are configured.

Do I need a specific customer registry to synthesize cross-source status updates?▼

Yes, you need a customer registry configured in templates/customers.yaml. You also need active Asana, Jira, and Slack credentials to correlate data and populate the status summary.

What is the best way to prepare a one-page SE status update for a customer meeting?▼

The best way is generating a 3P update that cites recently resolved Jira issues, completed Asana tasks, and Slack escalations. This provides a fast, factual one-page summary without manual cross-referencing.

Why does my 3P update synthesis fail to correlate Slack messages with Jira issues?▼

Synthesis fails if Asana, Jira, or Slack credentials are not properly configured. Ensure all data source dependencies are authenticated and the customer registry in templates/customers.yaml is correctly set up.