Coordinate subagents to research and draft technical narratives for Jira issues.
npx skills add https://github.com/edlng/agents --skill write-narrative
Please help me install this Agent Skill. Skill: write-narrative Source: https://github.com/edlng/agents/tree/main/skills/claude/write-narrative Command: npx skills add https://github.com/edlng/agents --skill write-narrative
This skill automates the time-consuming process of researching technical topics and drafting professional, human-readable narratives for Jira issues, ensuring consistency and technical accuracy.
Use the write-narrative skill to generate a technical assessment for Jira issue AEA-468.
High-intent search queries and answers about installing and using this skill.
You can automate technical narrative drafting by coordinating subagents to fetch Jira data, analyze technical details, and apply humanizer rules. This process extracts issue context, researches dependencies, and generates structured markdown documentation saved locally.
The best way to generate humanized technical reports from Jira is to use automated subagent orchestration. This method fetches issue data, researches technical documentation, and applies a humanizer rule set to produce natural, structured markdown documentation.
Yes, this skill creates compatibility assessments for software engineering workflows. It coordinates subagents to analyze technical details from repositories and documentation, producing structured markdown reports tailored for integration documentation and compatibility checks.
Yes, Atlassian Jira APIs are required to fetch issue data for the drafting workflow. The subagents rely on this integration to retrieve issue context, perform technical analysis, and generate humanized markdown documentation saved to your local filesystem.
Valkey GLIDE generates technical code snippets within the narrative generation workflow. After fetching Jira data and researching technical context, the process uses Valkey GLIDE to create code snippets for inclusion in the final structured markdown documentation.
Automating technical writing for Jira issues is constrained by its dependency on Atlassian Jira APIs and specialized subagent orchestration. It targets software engineering workflows like compatibility assessments, making it unsuitable for general or unstructured documentation tasks.
al-stevConfigure Atlassian API credentials for Jira and Confluence access.
alexanderopCreate Vue-powered documentation sites from Markdown with file-based routing.
edlngAnalyze codebases for Valkey integration and verify GLIDE client interactions via live spike testing.
posit-devDrafts complete GitHub issue drafts for the Positron repository with duplicate checking.
