Menu
Pull Jira issue details into the current session as working context. Use before starting implementation to understand requirements.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Demo pipeline state machine — 7-phase autonomous sequence with delegation context templates, phase transition logic, BLOCKED recovery strategies, and demo-state.json schema. Used exclusively by demo-conductor.
Cinematic narration style guide for demo-conductor — ANSI-coloured banner formats, live pipeline scoreboard, audience-facing language, phase summaries, and error narration patterns. Keeps the demo presentation-quality throughout.
Standardized completion and escalation protocol for subagent responses. Ensures the conductor can machine-parse every subagent return. Use when reporting completion status back to the orchestrator.
Cross-session learnings lifecycle — schema, storage, retrieval, and pruning of lessons learned during orchestrator sessions. Use when managing learnings via the /learn command.
Agent Teams assembly and task injection — selects appropriate team, validates prerequisites, estimates cost, injects tasks into the shared task list, and manages team lifecycle.
Token and cost tracking with model tier enforcement
| name | issue-context |
| description | Pull Jira issue details into the current session as working context. Use before starting implementation to understand requirements. |
| argument-hint | <issue-key> |
get_issue tool--- Jira Context: {ISSUE-KEY} ---
Title: {summary}
Status: {status}
Priority: {priority}
Assignee: {assignee}
Requirements:
{description, formatted as bullet points}
Acceptance Criteria:
- {criterion 1}
- {criterion 2}
Linked Issues:
- {ISSUE-KEY}: {relationship} - {summary}
Recent Discussion:
- {author} ({date}): {comment summary}
Blockers: {none | list of blocking issues}
claude /cc-jira:issue-context PROJ-123