plan-feature

Generate Jira tasks from Jira features and Figma designs.

10|7|Updated Mar 18, 2026

Search Tags:#impact analysis #SDLC #Jira #task generation #repository analysis

Ready to run

npx skills add https://github.com/RHEcosystemAppEng/sdlc-plugins --skill plan-feature-rhecosystemappeng

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-feature
Source: https://github.com/RHEcosystemAppEng/sdlc-plugins/tree/main/plugins/sdlc-workflow/skills/plan-feature
Command: npx skills add https://github.com/RHEcosystemAppEng/sdlc-plugins --skill plan-feature-rhecosystemappeng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires serena-mcp, jira-api, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of creating detailed Jira tasks from Jira features and associated Figma designs, saving time and reducing errors in task creation.

Core Features & Use Cases

Task Generation: Automatically generates Jira tasks based on Jira feature descriptions and Figma design mockups.
Impact Analysis: Analyzes impacted repositories, modules, APIs, and tests.
Documentation & Testing: Assists in documenting and testing the impact of features.
Use Case: When you have a Jira feature and a corresponding Figma design, use this Skill to automatically generate the tasks needed to implement the feature.

Quick Start

Use the /plan-feature slash command followed by the Jira issue ID and optionally the Figma URL. For example: /plan-feature PROJ-123

Frequently Asked Questions about plan-feature

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

FAQPage Schema

How do I automate Jira task generation from feature descriptions and Figma designs?▼

Automate Jira task generation by using the /plan-feature slash command with a Jira issue ID and an optional Figma URL to automatically parse requirements and create detailed implementation tasks.

How does impact analysis work for mapping Jira features to repository modules?▼

Impact analysis maps Jira features to repository modules by using Serena MCP to scan impacted repositories, identify affected APIs, and determine required tests for comprehensive SDLC coverage.

Do I need Serena MCP and Jira API configured to generate Jira tasks from features?▼

Yes, you need Serena MCP configured for repository analysis and the Jira REST API connected for task creation, with the Jira API acting as a fallback mechanism within your SDLC workflow.

What's the best way to analyze impacted repositories when planning a new software feature?▼

Analyze impacted repositories by running the /plan-feature command, which leverages Serena MCP to evaluate your codebase, map impacted modules and APIs, and document testing requirements.

Can I use Jira feature tickets alone without a Figma design to generate implementation tasks?▼

Yes, you can generate implementation tasks using only a Jira feature ticket by providing the Jira issue ID to the /plan-feature command, as the Figma design URL is an optional input.

What are the limitations of automating SDLC task generation from Jira features?▼

Limitations include dependency on Serena MCP for accurate repository analysis and the Jira REST API for task creation, meaning task generation accuracy relies entirely on the initial feature description quality.