Create Jira Feature

This skill provides implementation guidance for creating Jira features, which represent high-level strategic objectives and solutions to market problems.

When to Use This Skill

This skill is automatically invoked by the /jira:create feature command to guide the feature creation process.

Prerequisites

MCP Jira server configured and accessible
User has permissions to create issues in the target project
Understanding of the strategic objective and market problem
Product/business context for the feature

Reference Documentation:

Markdown for Jira Reference - Markdown formatting for Jira descriptions

Custom Fields (redhat.atlassian.net)

| Field | ID | Type | Usage | |-------|------|------|-------| | Target Version | customfield_10855 | Array | Format: [{"id": "VERSION_ID"}] |

Feature Description Best Practices

Market Problem

Every feature should clearly state:

What customer/business problem does this solve?
Who is affected by this problem?
Why is solving this problem important now?
What happens if we don't solve it?

Good example:

## Market Problem

Enterprise customers managing multiple ROSA HCP clusters (10+) struggle with operational visibility and control. They must navigate between separate dashboards for each cluster, making it difficult to:
- Identify issues across their cluster fleet
- Track resource utilization trends
- Respond quickly to incidents
- Optimize costs across clusters

This leads to increased operational overhead, slower incident response, and higher support costs. Without a unified observability solution, customers face scalability challenges as their cluster count grows.

Bad example:

We need better observability.

Strategic Value

Explain why this feature matters to the business:

Business impact: Revenue, cost reduction, market differentiation
Customer value: What do customers gain?
Competitive advantage: How does this position us vs competitors?
Strategic alignment: How does this support company/product strategy?

Example:

## Strategic Value

### Customer Value
- 60% reduction in time spent on cluster management
- Faster incident detection and response (10min → 2min)
- Better resource optimization across cluster fleet
- Improved operational confidence at scale

### Business Impact
- Supports enterprise expansion (critical for deals >100 clusters)
- Reduces support burden (fewer escalations, faster resolution)
- Competitive differentiator (no competitor offers unified HCP observability)
- Enables upsell opportunities (advanced monitoring add-ons)

### Strategic Alignment
- Aligns with "Enterprise-First" product strategy for FY2025
- Prerequisite for multi-cluster management capabilities in roadmap
- Supports OpenShift Hybrid Cloud Platform vision

Success Criteria

Define how you'll measure success (not just completion):

Adoption metrics: How many customers will use this?
Usage metrics: How will it be used?
Outcome metrics: What improves as a result?
Business metrics: Revenue, cost, satisfaction impact

Example:

## Success Criteria

### Adoption
- 50% of customers with 10+ clusters adopt within 6 months of GA
- Feature enabled by default for new cluster deployments

### Usage
- Average of 5 dashboard views per day per customer
- Alert configuration adoption >30% of customers
- API usage growing 20% month-over-month

### Outcomes
- 40% reduction in time-to-detect incidents (measured via support metrics)
- Customer satisfaction (CSAT) improvement from 7.2 to 8.5 for multi-cluster users
- 25% reduction in cluster management support tickets

### Business
- Closes 10+ enterprise deals blocked by observability gap
- Reduces support costs by $200K annually
- Enables $500K in advanced monitoring upsell revenue

Interactive Feature Collection Workflow

When creating a feature, guide the user through strategic thinking:

1. Market Problem

Prompt: "What customer or market problem does this feature solve? Be specific about who is affected and why it matters."

Probing questions:

Who has this problem? (customer segment, user type)
What pain do they experience today?
What is the impact of not solving this?
Why is solving this important now?

Example response:

Enterprise customers with large ROSA HCP deployments (50+ clusters) struggle with operational visibility. They must manage each cluster separately, leading to slow incident response, difficulty tracking compliance, and high operational overhead. This is blocking large enterprise deals and causing customer escalations.

2. Proposed Solution

Prompt: "How will this feature solve the problem? What capability will be delivered?"

Example response:

Deliver a unified observability platform for ROSA HCP that aggregates metrics, logs, and events across all clusters in a customer's fleet. Provide centralized dashboards, fleet-wide alerting, and compliance reporting.

3. Strategic Value

Prompt: "Why is this strategically important? What business value does it deliver?"

Helpful questions:

What business impact will this have? (revenue, cost, market position)
How does this align with product strategy?
What competitive advantage does this provide?
What customer value is delivered?

Example response:

Customer value: 50% reduction in cluster management time
Business impact: Unblocks $5M in enterprise deals, reduces support costs
Competitive advantage: No competitor offers unified HCP observability
Strategic alignment: Critical for enterprise market expansion

4. Success Criteria

Prompt: "How will you measure success? What metrics will tell you this feature achieved its goals?"

Categories to consider:

Adoption (who/how many use it)
Usage (how they use it)
Outcomes (what improves)
Business (revenue, cost, satisfaction)

Example response:

Adoption: 50% of enterprise customers within 6 months
Usage: Daily active usage by SREs in 80% of adopting customers
Outcomes: 40% faster incident detection
Business: Closes 15+ blocked enterprise deals

5. Scope and Epics

Prompt: "What are the major components or epics within this feature?"

Identify 3-8 major work streams:

Example response:

1. Multi-cluster metrics aggregation
2. Unified observability dashboard
3. Fleet-wide alerting and automation
4. Compliance and audit reporting
5. API and CLI for programmatic access
6. Documentation and enablement

6. Timeline and Milestones

Prompt: "What is the timeline? What are key milestones?"

Example response:

Timeline: 9 months (3 releases)
Milestones:
- Q1 2025: MVP metrics aggregation (Epic 1)
- Q2 2025: Dashboard and alerting (Epics 2-3)
- Q3 2025: Compliance, API, GA (Epics 4-6)

Field Validation

Before submitting the feature, validate:

Required Fields

✅ Summary clearly states the strategic objective
✅ Description includes market problem
✅ Strategic value articulated
✅ Success criteria defined (measurable)
✅ Component is specified (if required by project)
✅ Target version/release is set (if required)

Feature Quality

✅ Addresses a real market problem
✅ Strategic value is clear
✅ Success criteria are measurable
✅ Scope is larger than an epic (multi-epic)
✅ Timeline is realistic (1-3 releases)
✅ Aligns with product strategy

Security

✅ No credentials, API keys, or secrets in any field
✅ No confidential business information (if public project)

MCP Issue Creation

Create features via createJiraIssue with contentFormat: "markdown". Key parameters:

projectKey: e.g., "CNTRLPLANE"
issueTypeName: "Feature"
summary: feature summary
description: formatted feature template (Markdown) with Market Problem, Strategic Value, Success Criteria, Scope, Timeline sections
additional_fields: include "labels": ["ai-generated-jira"], "security": {"name": "Red Hat Employee"}, and target version when specified

Jira Description Formatting

Use Markdown formatting with contentFormat: "markdown":

Feature Template Format

<Brief feature overview>

## Market Problem

<Detailed description of customer/business problem>
<Who is affected, what pain they experience, impact of not solving>

## Proposed Solution

<Description of the capability/solution being delivered>

## Strategic Value

### Customer Value
- <Benefit 1>
- <Benefit 2>

### Business Impact
- <Impact 1>
- <Impact 2>

### Competitive Advantage
<How this differentiates us>

### Strategic Alignment
<How this supports product/company strategy>

## Success Criteria

### Adoption
- <Adoption metrics>

### Usage
- <Usage metrics>

### Outcomes
- <Customer outcome metrics>

### Business Metrics
- <Revenue, cost, satisfaction metrics>

## Scope

### Epics (Planned)
- Epic 1: <name>
- Epic 2: <name>
- Epic 3: <name>

### Out of Scope
- <Related work NOT in this feature>

## Timeline

- Total duration: <timeframe>
- Target GA: <date/release>

### Milestones
- <Quarter/Release>: <deliverable>
- <Quarter/Release>: <deliverable>

## Dependencies (if any)

- PROJ-XXX - <dependency description>

## Risks and Mitigation (optional)

### Risks
- <Risk 1>
- <Risk 2>

### Mitigation
- <Mitigation strategy 1>
- <Mitigation strategy 2>

Error Handling

Feature Too Small

Scenario: Feature could be accomplished as a single epic.

Action:

Suggest creating as Epic instead
Explain feature should be multi-epic effort

Example:

This feature seems small enough to be a single Epic (1-2 months, single capability).

Features should typically:
- Contain 3-8 epics
- Span multiple releases (6-12 months)
- Address strategic market problem

Would you like to create this as an Epic instead? (yes/no)

Missing Strategic Context

Scenario: User doesn't provide market problem or strategic value.

Action:

Explain importance of strategic framing
Ask probing questions
Help articulate business case

Example:

For a feature, we need to understand the strategic context:

1. What market problem does this solve?
2. Why is this strategically important to the business?
3. What value do customers get?

These help stakeholders understand why we're investing in this feature.

Let's start with: What customer problem does this solve?

Vague Success Criteria

Scenario: Success criteria are vague or not measurable.

Action:

Identify vague criteria
Ask for specific metrics
Suggest measurable alternatives

Example:

Success criteria should be measurable. "Feature is successful" is too vague.

Instead, consider metrics like:
- Adoption: "50% of enterprise customers within 6 months"
- Usage: "10+ daily dashboard views per customer"
- Outcomes: "40% faster incident response time"
- Business: "Close 10 blocked deals worth $3M"

What specific metrics would indicate success for this feature?

No Epic Breakdown

Scenario: User doesn't identify component epics.

Action:

Explain features are delivered through epics
Help identify major work streams
Suggest 3-8 epic areas

Example:

Features are typically delivered through 3-8 epics. What are the major components or work streams?

For observability, typical epics might be:
1. Metrics collection infrastructure
2. Dashboard and visualization
3. Alerting system
4. Reporting capabilities
5. API development
6. Documentation

What would be the major components for your feature?

Security Validation Failure

Scenario: Sensitive data detected in feature content.

Action:

STOP submission
Inform user what type of data was detected
Ask for redaction

Example:

I detected confidential business information (customer names, revenue figures).

If this is a public Jira project, please sanitize:
- Use "Enterprise Customer A" instead of actual customer names
- Use ranges ($1-5M) instead of exact revenue figures

MCP Tool Error

Scenario: MCP tool returns an error when creating the feature.

Action:

Parse error message
Provide user-friendly explanation
Suggest corrective action

Common errors:

"Issue type 'Feature' not available" → Check if project supports Features
"Field 'customfield_xyz' does not exist" → Remove unsupported custom field

Examples

Example 1: Complete Feature

Input:

/jira:create feature CNTRLPLANE "Advanced hosted control plane observability"

Interactive prompts collect:

Market problem (enterprise customer pain)
Strategic value (business impact, customer value)
Success criteria (measurable metrics)
Epic breakdown (7 major components)
Timeline (9 months, 3 releases)

Result:

Complete feature with strategic framing
All CNTRLPLANE conventions applied
Ready for epic planning

Example 2: Feature with Component Detection

Input:

/jira:create feature CNTRLPLANE "Multi-cloud cost optimization for ROSA and ARO HCP"

Auto-detected:

Component: HyperShift (affects both ROSA and ARO)
Target version: openshift-4.21

Result:

Feature with appropriate component
Multi-platform scope

Best Practices Summary

Strategic framing: Always articulate market problem and business value
Measurable success: Define specific metrics for adoption, usage, outcomes, business
Multi-epic scope: Feature should contain 3-8 epics
Customer-focused: Describe value from customer perspective
Business case: Clear ROI or strategic justification
Realistic timeline: 1-3 releases (6-12 months typical)
Risk awareness: Identify and mitigate known risks

Anti-Patterns to Avoid

❌ Feature is actually an epic

"Multi-cluster dashboard" (single capability, 1 epic)

✅ Too small, create as Epic

❌ No strategic context

"Build monitoring system"

✅ Must explain market problem and business value

❌ Vague success criteria

"Feature is successful when customers like it"

✅ Use measurable metrics: "50% adoption, 8.5 CSAT score, $2M revenue"

❌ Technical implementation as feature

"Migrate to Kubernetes operator pattern"

✅ Technical work should be epic/task. Features describe customer-facing value.

Workflow Summary

✅ Parse command arguments (project, summary)
🔍 Auto-detect component from summary keywords
⚙️ Apply project-specific defaults
💬 Interactively collect market problem
💬 Interactively collect strategic value
💬 Interactively collect success criteria
💬 Collect epic breakdown and timeline
🔒 Scan for sensitive data
✅ Validate feature quality and scope
📝 Format description with Markdown
✅ Create feature via MCP tool
📤 Return issue key and URL

Create Jira Feature

This skill provides implementation guidance for creating Jira features, which represent high-level strategic objectives and solutions to market problems.

When to Use This Skill

This skill is automatically invoked by the /jira:create feature command to guide the feature creation process.

Prerequisites

MCP Jira server configured and accessible
User has permissions to create issues in the target project
Understanding of the strategic objective and market problem
Product/business context for the feature

Reference Documentation:

Markdown for Jira Reference - Markdown formatting for Jira descriptions

Custom Fields (redhat.atlassian.net)

| Field | ID | Type | Usage | |-------|------|------|-------| | Target Version | customfield_10855 | Array | Format: [{"id": "VERSION_ID"}] |

Feature Description Best Practices

Market Problem

Every feature should clearly state:

What customer/business problem does this solve?
Who is affected by this problem?
Why is solving this problem important now?
What happens if we don't solve it?

Good example:

## Market Problem

Enterprise customers managing multiple ROSA HCP clusters (10+) struggle with operational visibility and control. They must navigate between separate dashboards for each cluster, making it difficult to:
- Identify issues across their cluster fleet
- Track resource utilization trends
- Respond quickly to incidents
- Optimize costs across clusters

This leads to increased operational overhead, slower incident response, and higher support costs. Without a unified observability solution, customers face scalability challenges as their cluster count grows.

Bad example:

We need better observability.

Strategic Value

Explain why this feature matters to the business:

Business impact: Revenue, cost reduction, market differentiation
Customer value: What do customers gain?
Competitive advantage: How does this position us vs competitors?
Strategic alignment: How does this support company/product strategy?

Example:

## Strategic Value

### Customer Value
- 60% reduction in time spent on cluster management
- Faster incident detection and response (10min → 2min)
- Better resource optimization across cluster fleet
- Improved operational confidence at scale

### Business Impact
- Supports enterprise expansion (critical for deals >100 clusters)
- Reduces support burden (fewer escalations, faster resolution)
- Competitive differentiator (no competitor offers unified HCP observability)
- Enables upsell opportunities (advanced monitoring add-ons)

### Strategic Alignment
- Aligns with "Enterprise-First" product strategy for FY2025
- Prerequisite for multi-cluster management capabilities in roadmap
- Supports OpenShift Hybrid Cloud Platform vision

Success Criteria

Define how you'll measure success (not just completion):

Adoption metrics: How many customers will use this?
Usage metrics: How will it be used?
Outcome metrics: What improves as a result?
Business metrics: Revenue, cost, satisfaction impact

Example:

## Success Criteria

### Adoption
- 50% of customers with 10+ clusters adopt within 6 months of GA
- Feature enabled by default for new cluster deployments

### Usage
- Average of 5 dashboard views per day per customer
- Alert configuration adoption >30% of customers
- API usage growing 20% month-over-month

### Outcomes
- 40% reduction in time-to-detect incidents (measured via support metrics)
- Customer satisfaction (CSAT) improvement from 7.2 to 8.5 for multi-cluster users
- 25% reduction in cluster management support tickets

### Business
- Closes 10+ enterprise deals blocked by observability gap
- Reduces support costs by $200K annually
- Enables $500K in advanced monitoring upsell revenue

Interactive Feature Collection Workflow

When creating a feature, guide the user through strategic thinking:

1. Market Problem

Prompt: "What customer or market problem does this feature solve? Be specific about who is affected and why it matters."

Probing questions:

Who has this problem? (customer segment, user type)
What pain do they experience today?
What is the impact of not solving this?
Why is solving this important now?

Example response:

Enterprise customers with large ROSA HCP deployments (50+ clusters) struggle with operational visibility. They must manage each cluster separately, leading to slow incident response, difficulty tracking compliance, and high operational overhead. This is blocking large enterprise deals and causing customer escalations.

2. Proposed Solution

Prompt: "How will this feature solve the problem? What capability will be delivered?"

Example response:

Deliver a unified observability platform for ROSA HCP that aggregates metrics, logs, and events across all clusters in a customer's fleet. Provide centralized dashboards, fleet-wide alerting, and compliance reporting.

3. Strategic Value

Prompt: "Why is this strategically important? What business value does it deliver?"

Helpful questions:

What business impact will this have? (revenue, cost, market position)
How does this align with product strategy?
What competitive advantage does this provide?
What customer value is delivered?

Example response:

Customer value: 50% reduction in cluster management time
Business impact: Unblocks $5M in enterprise deals, reduces support costs
Competitive advantage: No competitor offers unified HCP observability
Strategic alignment: Critical for enterprise market expansion

4. Success Criteria

Prompt: "How will you measure success? What metrics will tell you this feature achieved its goals?"

Categories to consider:

Adoption (who/how many use it)
Usage (how they use it)
Outcomes (what improves)
Business (revenue, cost, satisfaction)

Example response:

Adoption: 50% of enterprise customers within 6 months
Usage: Daily active usage by SREs in 80% of adopting customers
Outcomes: 40% faster incident detection
Business: Closes 15+ blocked enterprise deals

5. Scope and Epics

Prompt: "What are the major components or epics within this feature?"

Identify 3-8 major work streams:

Example response:

1. Multi-cluster metrics aggregation
2. Unified observability dashboard
3. Fleet-wide alerting and automation
4. Compliance and audit reporting
5. API and CLI for programmatic access
6. Documentation and enablement

6. Timeline and Milestones

Prompt: "What is the timeline? What are key milestones?"

Example response:

Timeline: 9 months (3 releases)
Milestones:
- Q1 2025: MVP metrics aggregation (Epic 1)
- Q2 2025: Dashboard and alerting (Epics 2-3)
- Q3 2025: Compliance, API, GA (Epics 4-6)

Field Validation

Before submitting the feature, validate:

Required Fields

✅ Summary clearly states the strategic objective
✅ Description includes market problem
✅ Strategic value articulated
✅ Success criteria defined (measurable)
✅ Component is specified (if required by project)
✅ Target version/release is set (if required)

Feature Quality

✅ Addresses a real market problem
✅ Strategic value is clear
✅ Success criteria are measurable
✅ Scope is larger than an epic (multi-epic)
✅ Timeline is realistic (1-3 releases)
✅ Aligns with product strategy

Security

✅ No credentials, API keys, or secrets in any field
✅ No confidential business information (if public project)

MCP Issue Creation

Create features via createJiraIssue with contentFormat: "markdown". Key parameters:

projectKey: e.g., "CNTRLPLANE"
issueTypeName: "Feature"
summary: feature summary
description: formatted feature template (Markdown) with Market Problem, Strategic Value, Success Criteria, Scope, Timeline sections
additional_fields: include "labels": ["ai-generated-jira"], "security": {"name": "Red Hat Employee"}, and target version when specified

Jira Description Formatting

Use Markdown formatting with contentFormat: "markdown":

Feature Template Format

<Brief feature overview>

## Market Problem

<Detailed description of customer/business problem>
<Who is affected, what pain they experience, impact of not solving>

## Proposed Solution

<Description of the capability/solution being delivered>

## Strategic Value

### Customer Value
- <Benefit 1>
- <Benefit 2>

### Business Impact
- <Impact 1>
- <Impact 2>

### Competitive Advantage
<How this differentiates us>

### Strategic Alignment
<How this supports product/company strategy>

## Success Criteria

### Adoption
- <Adoption metrics>

### Usage
- <Usage metrics>

### Outcomes
- <Customer outcome metrics>

### Business Metrics
- <Revenue, cost, satisfaction metrics>

## Scope

### Epics (Planned)
- Epic 1: <name>
- Epic 2: <name>
- Epic 3: <name>

### Out of Scope
- <Related work NOT in this feature>

## Timeline

- Total duration: <timeframe>
- Target GA: <date/release>

### Milestones
- <Quarter/Release>: <deliverable>
- <Quarter/Release>: <deliverable>

## Dependencies (if any)

- PROJ-XXX - <dependency description>

## Risks and Mitigation (optional)

### Risks
- <Risk 1>
- <Risk 2>

### Mitigation
- <Mitigation strategy 1>
- <Mitigation strategy 2>

Error Handling

Feature Too Small

Scenario: Feature could be accomplished as a single epic.

Action:

Suggest creating as Epic instead
Explain feature should be multi-epic effort

Example:

This feature seems small enough to be a single Epic (1-2 months, single capability).

Features should typically:
- Contain 3-8 epics
- Span multiple releases (6-12 months)
- Address strategic market problem

Would you like to create this as an Epic instead? (yes/no)

Missing Strategic Context

Scenario: User doesn't provide market problem or strategic value.

Action:

Explain importance of strategic framing
Ask probing questions
Help articulate business case

Example:

For a feature, we need to understand the strategic context:

1. What market problem does this solve?
2. Why is this strategically important to the business?
3. What value do customers get?

These help stakeholders understand why we're investing in this feature.

Let's start with: What customer problem does this solve?

Vague Success Criteria

Scenario: Success criteria are vague or not measurable.

Action:

Identify vague criteria
Ask for specific metrics
Suggest measurable alternatives

Example:

Success criteria should be measurable. "Feature is successful" is too vague.

Instead, consider metrics like:
- Adoption: "50% of enterprise customers within 6 months"
- Usage: "10+ daily dashboard views per customer"
- Outcomes: "40% faster incident response time"
- Business: "Close 10 blocked deals worth $3M"

What specific metrics would indicate success for this feature?

No Epic Breakdown

Scenario: User doesn't identify component epics.

Action:

Explain features are delivered through epics
Help identify major work streams
Suggest 3-8 epic areas

Example:

Features are typically delivered through 3-8 epics. What are the major components or work streams?

For observability, typical epics might be:
1. Metrics collection infrastructure
2. Dashboard and visualization
3. Alerting system
4. Reporting capabilities
5. API development
6. Documentation

What would be the major components for your feature?

Security Validation Failure

Scenario: Sensitive data detected in feature content.

Action:

STOP submission
Inform user what type of data was detected
Ask for redaction

Example:

I detected confidential business information (customer names, revenue figures).

If this is a public Jira project, please sanitize:
- Use "Enterprise Customer A" instead of actual customer names
- Use ranges ($1-5M) instead of exact revenue figures

MCP Tool Error

Scenario: MCP tool returns an error when creating the feature.

Action:

Parse error message
Provide user-friendly explanation
Suggest corrective action

Common errors:

"Issue type 'Feature' not available" → Check if project supports Features
"Field 'customfield_xyz' does not exist" → Remove unsupported custom field

Examples

Example 1: Complete Feature

Input:

/jira:create feature CNTRLPLANE "Advanced hosted control plane observability"

Interactive prompts collect:

Market problem (enterprise customer pain)
Strategic value (business impact, customer value)
Success criteria (measurable metrics)
Epic breakdown (7 major components)
Timeline (9 months, 3 releases)

Result:

Complete feature with strategic framing
All CNTRLPLANE conventions applied
Ready for epic planning

Example 2: Feature with Component Detection

Input:

/jira:create feature CNTRLPLANE "Multi-cloud cost optimization for ROSA and ARO HCP"

Auto-detected:

Component: HyperShift (affects both ROSA and ARO)
Target version: openshift-4.21

Result:

Feature with appropriate component
Multi-platform scope

Best Practices Summary

Strategic framing: Always articulate market problem and business value
Measurable success: Define specific metrics for adoption, usage, outcomes, business
Multi-epic scope: Feature should contain 3-8 epics
Customer-focused: Describe value from customer perspective
Business case: Clear ROI or strategic justification
Realistic timeline: 1-3 releases (6-12 months typical)
Risk awareness: Identify and mitigate known risks

Anti-Patterns to Avoid

❌ Feature is actually an epic

"Multi-cluster dashboard" (single capability, 1 epic)

✅ Too small, create as Epic

❌ No strategic context

"Build monitoring system"

✅ Must explain market problem and business value

❌ Vague success criteria

"Feature is successful when customers like it"

✅ Use measurable metrics: "50% adoption, 8.5 CSAT score, $2M revenue"

❌ Technical implementation as feature

"Migrate to Kubernetes operator pattern"

✅ Technical work should be epic/task. Features describe customer-facing value.

Workflow Summary

✅ Parse command arguments (project, summary)
🔍 Auto-detect component from summary keywords
⚙️ Apply project-specific defaults
💬 Interactively collect market problem
💬 Interactively collect strategic value
💬 Interactively collect success criteria
💬 Collect epic breakdown and timeline
🔒 Scan for sensitive data
✅ Validate feature quality and scope
📝 Format description with Markdown
✅ Create feature via MCP tool
📤 Return issue key and URL

Adoption

openshift-eng/create-feature

$ install --global

Security Scan Results

SKILL.md

Create Jira Feature

When to Use This Skill

Prerequisites

Custom Fields (redhat.atlassian.net)

Feature Description Best Practices

Market Problem

Strategic Value

Success Criteria

Interactive Feature Collection Workflow

1. Market Problem

2. Proposed Solution

3. Strategic Value

4. Success Criteria

5. Scope and Epics

6. Timeline and Milestones

Field Validation

Required Fields

Feature Quality

Security

MCP Issue Creation

Jira Description Formatting

Feature Template Format

Error Handling

Feature Too Small

Missing Strategic Context

Vague Success Criteria

No Epic Breakdown

Security Validation Failure

MCP Tool Error

Examples

Example 1: Complete Feature

Example 2: Feature with Component Detection

Best Practices Summary

Anti-Patterns to Avoid

Workflow Summary

See Also

Related Skills

openshift-eng/status-analysis

openshift-eng/payload-snapshot

openshift-eng/payload-analysis

openshift-eng/stage-payload-reverts

openshift-eng/create-feature

$ install --global

Security Scan Results

SKILL.md

Create Jira Feature

When to Use This Skill

Prerequisites

Custom Fields (redhat.atlassian.net)

Feature Description Best Practices

Market Problem

Strategic Value

Success Criteria

Interactive Feature Collection Workflow

1. Market Problem

2. Proposed Solution

3. Strategic Value

4. Success Criteria

5. Scope and Epics

6. Timeline and Milestones

Field Validation

Required Fields

Feature Quality

Security

MCP Issue Creation

Jira Description Formatting

Feature Template Format

Error Handling

Feature Too Small

Missing Strategic Context

Vague Success Criteria

No Epic Breakdown

Security Validation Failure

MCP Tool Error

Examples