b-mendoza/planning-github-issue-tasks
skills/planning-github-issue-tasks/SKILL.md
Phase 2 of the GitHub planning workflow. Reads a GitHub issue snapshot, dispatches a plan/prioritize/validate pipeline, and writes docs/<ISSUE_SLUG>-tasks.md with branch names for every planned child issue.
testing
Updated May 26, 2026
$ install --global
skillsauthnpx skillsauth add b-mendoza/agent-skills planning-github-issue-tasksInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 26, 2026, 3:50 AM102.0s15 files scanned
SKILL.md
- name:
- planning-github-issue-tasks
- description:
- Phase 2 of the GitHub planning workflow. Reads a GitHub issue snapshot, dispatches a plan/prioritize/validate pipeline, and writes docs/<ISSUE_SLUG>-tasks.md with branch names for every planned child issue.
Planning GitHub Issue Tasks
Plan a GitHub issue snapshot into docs/<ISSUE_SLUG>-tasks.md. This is the
Phase 2 orchestrator for the GitHub 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 |
| ----- | -------- | ------- |
| ISSUE_SLUG | Yes | acme-app-42 |
| RE_PLAN | No | true |
| DECISIONS | No | SSO decision changes task dependencies |
Phase 2 is file-driven. docs/<ISSUE_SLUG>.md must already exist as the GitHub
issue snapshot.
Progressive Loading Map
| Need | Load |
| ---- | ---- |
| Normal run, dispatch payloads, retry loop | ./references/execution-guide.md |
| Final artifact contract, branch policy, child-issue handling | ./references/output-contract.md |
| Critique-driven re-plan or recovery from stage artifacts | ./references/re-plan-cycle.md |
| Source-backed background or current platform syntax | ./references/external-sources.md |
| Subagent-specific guides, templates, or validation checks | Load only from the dispatched subagent |
Bundled paths in this file are relative to this SKILL.md; files loaded later
use paths relative to their own locations. All bundled files travel with the
package.
External URLs are optional progressive enhancement: fetch them only when local
contracts need background or current syntax, and proceed from bundled references
when network access is unavailable.
Subagent Registry
| Subagent | Path | Purpose |
| -------- | ---- | ------- |
| task-planner | ./subagents/task-planner.md | Decompose the issue and draft the stage 1 plan |
| dependency-prioritizer | ./subagents/dependency-prioritizer.md | Add dependency order, priority, and branch names |
| task-validator | ./subagents/task-validator.md | Validate the prioritized plan and append QA findings |
| stage-validator | ./subagents/stage-validator.md | Check preflight, inter-stage, and final structural gates |
Workflow
| Path | When | Next reference |
| ---- | ---- | -------------- |
| Normal | RE_PLAN is absent or false | ./references/execution-guide.md |
| Re-plan | RE_PLAN=true with critique decisions | ./references/re-plan-cycle.md, then ./references/execution-guide.md |
The normal path is: preflight snapshot validation, Stage 1 detailed planning, Stage 1 validation, Stage 2 dependency/branch planning, Stage 2 validation, Stage 3 final validation report, Stage 3 validation, postpipeline validation, handoff.
Preserve docs/<ISSUE_SLUG>-stage-1-detailed.md,
docs/<ISSUE_SLUG>-stage-2-prioritized.md, and
docs/<ISSUE_SLUG>-tasks.md on disk. They are orchestration state for resume,
critique, and targeted retries; they are not implementation outputs.
Use targeted fix loops only. Re-dispatch the stage that produced the failing artifact, pass only the validator's issue list, rerun only the failing gate, and stop after 3 failed cycles for the same gate.
Return Format
Return only this phase handoff. Use PLANNING: PASS only when every stage and
stage-validation gate has passed.
PLANNING: PASS | FAIL
ISSUE_SLUG: <ISSUE_SLUG>
File: <final file path or "not written">
Tasks: <N>
Branches: <N unique branch names>
Cross-cutting questions: <N>
Validation warnings: <N>
Failure category: PREFLIGHT | STAGE_1 | STAGE_2 | STAGE_3 | POSTPIPELINE | NONE
Reason: <one line>
Artifacts preserved: <comma-separated paths>
Example
<example> Input: `ISSUE_SLUG=acme-app-42`- Load
./references/execution-guide.mdfor the dispatch payloads. - Dispatch
stage-validatorforpreflight; it returnsSTAGE_VALIDATION: PASS. - Dispatch
task-planner,dependency-prioritizer, andtask-validatorin sequence, validating after each produced artifact. - Dispatch
stage-validatorforpostpipeline; it returnsSTAGE_VALIDATION: PASS. - Return the concise
PLANNING: PASShandoff with preserved artifact paths. </example>
Related Skills
b-mendoza/fetching-work-item
testing
VerifiedTrustedCommunity
Retrieves a Jira ticket or a GitHub issue into docs/<KEY>.md as a read-only, validated Markdown snapshot for downstream workflow phases. Use when a Jira URL, a GitHub issue URL, or owner/repo/number coordinates need the Phase 1 fetch-work-item step. Detects the platform from the input and loads the matching playbook just-in-time.
SKILL.mdUpdated Jun 6, 2026
b-mendoza/council-of-advisors
development
VerifiedTrustedCommunity
Runs a structured nine-seat council deliberation on an idea, project, business, startup, goal, or objective, then returns a reasoned recommendation with the mental models exposed so the user can apply them solo next time. Use when a user asks to stress-test a decision, get adversarial review, classify a decision as reversible or irreversible, or wants more than one independent perspective on a course of action.
SKILL.mdUpdated Jun 4, 2026
b-mendoza/improving-skill-definition
testing
VerifiedTrustedCommunity
Adversarially improves existing agent skill packages by stress-testing workflow design, flow-diagram coherence, personality fit, subagent necessity, and package quality before applying approved changes.
SKILL.mdUpdated May 28, 2026
b-mendoza/planning-codebase-restructuring
development
VerifiedTrustedCommunity
Coordinates subagent-driven architecture reviews and restructuring plans. Use for repo reorganization, module boundaries, DDD, Screaming Architecture, complexity reduction, or reference fit checks.
SKILL.mdUpdated May 26, 2026