Aggregate Jira, Slack, Asana, and product updates into a structured meeting agenda.
npx skills add https://github.com/al-stev/field-eng-skills --skill cadence-prep
Please help me install this Agent Skill. Skill: cadence-prep Source: https://github.com/al-stev/field-eng-skills/tree/main/.claude/skills/cadence-prep Command: npx skills add https://github.com/al-stev/field-eng-skills --skill cadence-prep
Prepare customer cadence and QBR meetings without manual cross-tool copy-pasting by aggregating Jira issues, Slack threads, Asana actions, RAID items, and product updates into a single structured agenda ready for review and publishing.
Run the cadence-prep skill for a customer by invoking the cadence-prep command with the customer name and optional --dry-run or --html flags.
High-intent search queries and answers about installing and using this skill.
Build a structured cadence meeting agenda by aggregating Jira issues, Slack threads, Asana actions, and product updates into a single markdown document. The tool automatically collects open and resolved tickets, notable Slack threads, and RAID items, then populates a templated agenda with sections for What's New, Actions, and Product Updates.
The best way to prepare a QBR agenda without manual cross-tool copy-pasting is to automate data collection from Jira, Slack, and Asana. This approach gathers all open and recently resolved tickets along with notable threads into a structured, meeting-ready markdown file with proper source links.
Yes, you can publish cadence agendas directly to Confluence. The tool produces templated markdown output and optionally publishes it to Confluence, while also supporting styled HTML export for screen-sharing and saving dated local files to preserve carry-forward context for future meetings.
You only need read-only Jira and Slack credentials to generate a cadence agenda. Asana and Confluence credentials are optional, and the tool uses graceful fallbacks to annotate any missing data sources for manual follow-up if Asana is not connected.
The cadence agenda preserves immutable previous meeting files and automatically extracts carry-forward items from previous docs. By saving dated local markdown files, it ensures that past context is carried forward into the new agenda without mutating or overwriting prior records.
Yes, you can preview a cadence agenda before publishing by using the dry-run flag. This generates the complete templated agenda with all aggregated Jira and Slack data for review, without actually publishing to Confluence or exporting the final styled HTML.
al-stevReconcile Salesforce account data with Jira, Slack, Asana, and Confluence to populate the customers registry.
leolionartPublish Markdown content to Confluence with synchronized metadata and formatting.
al-stevConvert Slack threads and meeting notes into structured Asana tasks.
idontcarlGenerate meeting pre-reads and agendas from Notion context with Codex enrichment.
