Menu
Implementation guide for creating Jira features that organize multiple epics into strategic initiatives for SRVKP project
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Implementation guide for creating well-formed Jira bug reports in SRVKP project
Implementation guide for creating Jira epics with proper scope and parent linking in SRVKP project
Implementation guide for creating well-formed Jira user stories with acceptance criteria in SRVKP project
Implementation guide for creating Jira tasks for technical and operational work in SRVKP project
Create and manage Jira issues (bugs, epics, stories, tasks) for SRVKP project with intelligent routing and project-specific conventions
| name | Create Jira Feature |
| description | Implementation guide for creating Jira features that organize multiple epics into strategic initiatives for SRVKP project |
This skill provides implementation guidance for creating well-structured Jira features that organize related epics into strategic initiatives for the SRVKP project.
This skill is automatically invoked by:
/jira:create feature commandcreate-epic skill when auto-suggesting parent Featuresacli installed and authenticatedShared conventions (safety rules, component table, confirmation flow, MCP→CLI fallback):
→ Read and follow ../_common.md before proceeding.
CLI reference: ../reference/cli-fallback.md
This skill is exclusively for SRVKP (OpenShift Pipelines project).
A feature is:
| Level | Scope | Duration | Contains | Example |
|---|---|---|---|---|
| Feature | Strategic capability | Multiple quarters | Multiple Epics | "Tekton Chains Signing Enhancements" |
| Epic | Specific capability | One quarter | Multiple Stories | "Recursive Image Manifest signing" |
| Story | User functionality | One sprint | Tasks/Subtasks | "Sign multi-arch manifests automatically" |
Features should:
The feature description should:
Good example:
Expand Tekton Chains signing and attestation capabilities to support modern container image formats, multi-architecture workflows, and emerging supply chain security standards.
This feature addresses the growing need for comprehensive artifact signing in cloud-native CI/CD pipelines, enabling organizations to meet security compliance requirements and prevent supply chain attacks.
Target users: Platform engineers, Security teams, DevOps practitioners
Market need: Supply chain security compliance (SLSA, in-toto)
Feature-level outcomes should be measurable and tied to business value:
Format:
h2. Strategic Outcomes
* <Business outcome 1>
* <Business outcome 2>
* <Business outcome 3>
Example:
h2. Strategic Outcomes
* Organizations can meet SLSA Level 3 requirements for all artifact types
* Multi-architecture image workflows fully supported without manual configuration
* Signing coverage increased to 100% of build artifacts (up from ~70%)
* Developer friction reduced - automatic signing without explicit configuration
Include expected timeline and epic breakdown:
Example:
h2. Timeline
* Target: Q3-Q4 2026
* Duration: 2-3 quarters
* Key milestones:
* Q3 2026: Core multi-architecture support
* Q4 2026: Advanced attestation features
h2. Planned Epics
* Recursive Image Manifest signing in Image Index
* Enhanced attestation formats for multi-arch
* Cross-registry signing support
* (Additional epics to be refined)
Prompt: "What is the strategic objective of this feature? What market need or capability area does it address?"
Helpful questions:
Example response:
Expand Tekton Chains signing to support modern container image formats like Image Index and multi-architecture workflows, addressing supply chain security compliance requirements.
Prompt: "What are the measurable strategic outcomes? How will success be measured?"
Example response:
- Organizations can meet SLSA Level 3 for all artifact types
- Multi-arch workflows fully supported
- Signing coverage reaches 100% of build artifacts
- Reduced manual configuration overhead
Prompt: "What epics are expected under this feature? (Initial list - can evolve)"
Example response:
- Recursive Image Manifest signing
- Enhanced multi-arch attestation
- Cross-registry signing support
- Signature verification improvements
Prompt: "What is the target timeline for this feature?"
Example responses:
Before submitting the feature, validate:
Follow the MCP → CLI Fallback Decision Tree in ../_common.md.
acli jira workitem create \
--project "SRVKP" \
--type "Feature" \
--summary "Tekton Chains Signing Enhancements" \
--description "$(cat <<'EOF'
Expand Tekton Chains signing capabilities to support modern container image formats and multi-architecture workflows.
h2. Strategic Outcomes
* SLSA Level 3 compliance for all artifact types
* Multi-arch workflows fully supported
* 100% signing coverage without manual configuration
h2. Target Users
* Platform engineers building multi-arch images
* Security teams implementing supply chain security
h2. Timeline
* Target: Q3-Q4 2026
* Duration: 2-3 quarters
EOF
)" \
--label "ai-generated-jira" \
--json
Note: Use $(cat <<'EOF' ... EOF) for inline multi-line descriptions with wiki markup. No temp files needed.
{Strategic objective paragraph}
h2. Strategic Outcomes
* {Outcome 1}
* {Outcome 2}
* {Outcome 3}
h2. Target Users
* {User segment 1}
* {User segment 2}
h2. Market Need
{Why this feature area matters strategically}
h2. Timeline
* Target: {quarters/year}
* Duration: {estimated time}
* Key milestones: {major deliverables}
h2. Planned Epics
* {Epic 1 - brief description}
* {Epic 2 - brief description}
* (To be refined as feature develops)
h2. Success Metrics
* {Metric 1}
* {Metric 2}
Context: User creating epic "Recursive Image Manifest signing in Tekton Chains"
Auto-generated Feature:
Summary: Tekton Chains Signing Enhancements
Description:
Expand Tekton Chains signing and attestation capabilities to support modern container image formats, multi-architecture workflows, and emerging supply chain security standards.
This feature addresses the growing need for comprehensive artifact signing in cloud-native CI/CD pipelines, enabling organizations to meet security compliance requirements.
h2. Strategic Outcomes
* Organizations can meet SLSA Level 3 requirements for all artifact types
* Multi-architecture image workflows fully supported without manual configuration
* Signing coverage increased to 100% of build artifacts
* Developer experience improved with automatic signing
h2. Target Users
* Platform engineers building multi-arch images
* Security teams implementing supply chain security
* DevOps practitioners managing CI/CD pipelines
h2. Market Need
Modern container deployments require multi-architecture support (amd64, arm64, s390x, ppc64le). Current signing approaches require manual configuration per architecture, creating friction and potential security gaps.
h2. Timeline
* Target: Q3-Q4 2026
* Duration: 2-3 quarters
* Key milestones:
* Q3 2026: Core recursive signing support
* Q4 2026: Advanced attestation and verification
h2. Planned Epics
* Recursive Image Manifest signing in Image Index
* Enhanced attestation formats for multi-arch artifacts
* Cross-registry manifest signing support
* (Additional epics to be refined)
h2. Success Metrics
* 100% signing coverage for multi-arch builds
* Zero manual pullspec configuration required
* SLSA Level 3 compliance achieved
* Adoption by 80%+ of multi-arch pipelines
Component: Tekton Chains
Input:
/jira:create feature "Enhanced Tekton Results storage and performance"
Interactive prompts:
What is the strategic objective of this feature?
> Improve Tekton Results storage efficiency and query performance to support large-scale pipeline deployments with millions of results
Strategic outcomes? (measurable)
> - Support 10M+ pipeline results per cluster
> - Query response times under 100ms for 95th percentile
> - Storage costs reduced by 60%
> - Retention policies configurable per namespace
Planned epics?
> - Database optimization and partitioning
> - Result pruning and archival
> - Query performance enhancements
> - Storage backend flexibility
Timeline?
> Q2-Q3 2026, estimated 2 quarters
Result:
❌ Feature is actually an epic
"Add recursive signing to Chains" (1-2 sprints)
✅ Too small, create as Epic instead
❌ Feature too broad
"Complete Tekton platform redesign" (multi-year, 50+ epics)
✅ Too large, break into multiple Features
❌ No business value
"Technical improvements to Chains"
✅ Be specific: What business value? What outcomes?
❌ Implementation details
"Refactor Chains to use new storage backend"
✅ Focus on user value, not implementation
Follow the Mandatory Confirmation Flow and MCP → CLI Fallback Decision Tree in
../_common.md. The preview label for this type is PREVIEW: SRVKP Feature.
acli on fallback/jira:create epic - Creating epics under featurescreate-epic skill - Epic creation (enhanced with feature discovery)