jira-geo-task

Plan and implement Jira GEO tasks with AGENTS.md standards and checkpoints.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/tecnologia-ibtech/geo-codex --skill jira-geo-task
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-geo-task
Source: https://github.com/tecnologia-ibtech/geo-codex/tree/main/geo-ops/skills/jira-geo-task
Command: npx skills add https://github.com/tecnologia-ibtech/geo-codex --skill jira-geo-task

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates end-to-end Jira GEO task work by reading Jira issues, applying the project's AGENTS.md standards, planning in opus mode, implementing according to repository conventions, and delivering a final quality checklist.

Core Features & Use Cases

  • Automated Jira Task Intake: Reads GEO-related Jira tickets (e.g., GEO-XXXX) and extracts objectives, acceptance criteria, and subtasks.
  • AGENTS.md compliance: References the project's coding and architectural standards to guide planning and implementation.
  • End-to-end Planning with Opus: Generates a detailed opus-based plan before any coding, including impact analysis and sequencing.
  • Implementation & Quality: Produces code changes and a final quality checklist suitable for PR review.

Quick Start

Provide a Jira GEO task key (e.g., GEO-XXXX) and request a full implementation plan.

Frequently Asked Questions about jira-geo-task

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

FAQPage Schema
How do I automate Jira task planning and implementation for GEO projects?

Automating Jira GEO task implementation involves reading Jira issues, applying AGENTS.md standards, and generating an opus-based plan with quality checklists before producing code changes for PR review.

How does AGENTS.md compliance work when implementing Jira tickets?

AGENTS.md compliance works by referencing the project's coding and architectural standards during task analysis to guide implementation, ensuring repository conventions are enforced throughout the planning and coding process.

Can I use this to generate an end-to-end plan from a Jira task key?

Yes, you can provide a Jira GEO task key like GEO-XXXX to automatically extract objectives and acceptance criteria, then generate a detailed implementation plan with impact analysis and sequencing.

What's the best way to ensure quality checks before PR review for GEO implementations?

The best way to ensure quality is generating a final quality checklist alongside code changes, enforcing project conventions and opus-based planning outputs suitable for direct PR review.

Do I need to manually extract subtasks from Jira issues for GEO projects?

No, automated Jira task intake reads GEO-related tickets to extract objectives, acceptance criteria, and subtasks directly, eliminating manual extraction before planning and implementation.

Why does the implementation require an opus-based plan before coding?

An opus-based plan is required before coding to provide detailed impact analysis and sequencing, ensuring structured implementation that adheres to AGENTS.md standards and repository conventions.