implement
Issue Blaster implement command: implement a selected issue plan from plans/issue-* with explicit git, validation, commit, and PR handling.
What this skill does
Implement the specified solution plan(s). In Claude Code this skill is normally
invoked as `/issue-blaster:implement`. In Codex, implement directly from the
selected plan using normal repo-editing, validation, commit, push, and PR
workflow; do not rely on Claude `Task`, `TaskOutput`, or `AskUserQuestion`.
## Arguments
$ARGUMENTS
## Instructions
### Step 1: Parse Arguments
Determine the invocation style:
**Single plan — two separate numbers** (e.g., `123 1`):
- Issue number = first argument, option number = second
- Invoke the plan-implementer agent directly with: `123 1`
**Single plan — colon syntax** (e.g., `123:1`):
- Same as above, invoke directly with: `123 1`
**Multiple plans — colon syntax** (e.g., `123:1 456:2 789:1`):
- Parse each `issue:option` pair
- Proceed to parallel dispatch
**Single path** (e.g., `plans/issue-123/option-1-fix.md`):
- Invoke the plan-implementer agent directly with the path
### Step 2: Dispatch
#### Single Plan
Invoke the plan-implementer agent directly with the parsed arguments.
In Codex:
- Read the selected plan file and verify it matches the requested issue/option
- Check `git status --short --branch` before editing
- Use the current branch when that matches the user's request; create a new
`codex/` branch or explicit worktree when isolation is needed
- Implement the plan with normal Codex file edits
- Run focused validation that matches the changed files
- Commit, push, open a PR, and merge only when the user has asked for those
actions
#### Multiple Plans (Parallel)
For EACH issue:option pair, use the Task tool with:
- **subagent_type**: `"plan-implementer"`
- **run_in_background**: `true`
- **description**: `"Implementing issue #{issue} option {option}"`
- **prompt**: `"{issue} {option}"`
After spawning all tasks, wait for completion using TaskOutput.
In Codex:
- Do not implement multiple plans in parallel unless the user explicitly asks
for subagents or parallel agent work
- If parallel work is authorized, use one disjoint branch/worktree per plan and
keep ownership boundaries explicit
- If parallel work is not authorized, implement one selected plan or ask which
plan should go first
### Step 3: Report Results
**Single plan**: The plan-implementer agent handles its own reporting.
**Multiple plans**: Output a summary table:
| Issue | Option | Branch | Worktree | Status |
|-------|--------|--------|----------|--------|
| #{N} | {opt} | `{branch}` | `.worktrees/{branch}` | SUCCESS/FAILED |
Then offer to merge any or all of them.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.