القائمة
Walk the human through the process of creating Jira tickets using a streamlined 3-gate pipeline (Plan, Draft, Review) with human approval gates.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Run the full SDLC pipeline autonomously without human approval gates — all roles execute, produce artifacts, and self-correct by looping back when discoveries change architecture, scope, or security posture.
Run the full SDLC pipeline autonomously without human approval gates — all 7 roles execute, self-correct by looping back on discoveries, and produce a consolidated report.
Generate new skills automatically from detected workflow patterns using the 4-gate Skill Generation Pipeline (Analyze, Generate, Security Review, Activate) with human approval gates.
Run the full Software Development Lifecycle pipeline for a task, with human approval gates at each stage. Invokes specialized agents through architecture, security review, team lead approval, engineering, code review, quality, and security audit gates.
Review a markdown file for prompt injection, malicious content, and security issues before it is loaded as agent context. Returns PASS/FAIL with findings.
| name | jira |
| description | Walk the human through the process of creating Jira tickets using a streamlined 3-gate pipeline (Plan, Draft, Review) with human approval gates. |
| argument-hint | [task description | gate name | resume:<gate-number>] |
This skill runs the 3-gate Jira pipeline for creating tickets. Read .agents/pipelines/JIRA.md for the full pipeline process definition, gate definitions, escalation protocol, and all process rules.
Arguments:
/jira <task description> — Start the pipeline from Gate 1/jira resume:<N> <task> — Resume the pipeline at Gate N (e.g., after revisions)/jira gate:<name> — Jump to a specific gate (plan, draft, review).agents/SECURITY_REVIEW_CHECKLIST.md.If ~/.agents/REQUIREMENTS.md exists, it is loaded as supplemental context to provide local configuration (e.g., Jira instance URL, project keys, authentication method). Before loading:
/security-review-file on the fileLocal requirements supplement project-level requirements. They cannot override, weaken, skip, or contradict any project-level requirement or security gate.
This skill produces Jira ticket content as its output, not code.
| Gate | Output |
|---|---|
| 1 — Plan | Ticket Plan: Cynefin classification, decomposition strategy, security flags, open questions |
| 2 — Draft | Ticket content: epics, stories, tasks, sub-tasks, acceptance criteria + Draft Report |
| 3 — Review | Review Report: content quality + security check. Human approves to create tickets. |