planning-jira-tasks
Planning Jira Ticket Tasks
Plan a Jira ticket snapshot into docs/<TICKET_KEY>-tasks.md. This is the
Phase 2 orchestrator for the Jira planning workflow: it routes stages,
dispatches specialists, preserves stage artifacts for resume and critique, and
returns a concise handoff.
The orchestrator keeps only workflow state, subagent verdicts, paths, counts, and user decisions in context. Detailed contracts, templates, validation checks, and source-backed background are loaded just in time from bundled references or optional external URLs.
Inputs
| Input | Required | Example |
|---|---|---|
TICKET_KEY |
Yes | JNS-6065 |
RE_PLAN |
No | true |
DECISIONS |
No | SSO decision changes task dependencies |
More from b-mendoza/agent-skills
validate-implementation-plan
Audits an implementation plan for requirements traceability, avoidable complexity, risky assumptions, and evidence gaps. Use when reviewing an AI-generated or human-authored plan, design proposal, implementation outline, task breakdown, or architecture plan and the user wants a standalone audit report without overwriting the source plan.
1.4Kclarifying-assumptions
Runs the conversational clarification layer for workflow orchestration. Use for plan-wide upfront clarification or task-level pre-execution critique while delegating artifact analysis, manifest assembly, and file updates to bundled subagents.
59recency-guard
Validates answers that depend on current external facts, including prices, versions, policies, rankings, recommendations, documentation, and availability. Use when the user asks for current, latest, verified, fact-checked, or up-to-date answers. Coordinates recency-checker and claim-verifier subagents to produce a current, qualified final answer.
56fetching-jira-ticket
Retrieves a Jira ticket into docs/<TICKET_KEY>.md. Use when a Jira URL needs a read-only, validated Markdown snapshot for downstream workflow phases.
49creating-jira-subtasks
Creates or reconciles Jira subtasks for an approved Phase 4 task plan. Use after docs/<TICKET_KEY>-tasks.md is clarified and the user has approved Jira writes; dispatches subtask-creator and returns a compact status summary.
47pr-creator
Create review-ready pull requests from the current branch with a preview-first, user-approved workflow. Use when the user asks to create, open, draft, or submit a PR, pull request, merge request, or code review request, or says their branch is ready for review.
46