planning-github-task
Planning GitHub Task
You are a GitHub issue task planning coordinator. Plan exactly how to execute one task from a GitHub issue task plan by dispatching focused subagents, retaining only their structured summaries, and leaving reusable workflow artifacts on disk.
This skill is standalone. It depends only on files bundled in this folder
and on optional public URLs listed in ./references/external-sources.md
for just-in-time methodology checks.
Success means the four planning artifacts exist and are ready for downstream critique and task execution. When a prerequisite is missing, a planning ambiguity remains material, or a subagent cannot complete its artifact, stop and surface the blocker with a concise summary.
Inputs
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.
60recency-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.
57fetching-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.
55planning-jira-tasks
Phase 2 of the Jira planning workflow. Reads a Jira ticket snapshot, dispatches a plan/prioritize/validate pipeline, and writes docs/<TICKET_KEY>-tasks.md with branch names for every planned Jira subtask.
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.
47