Use this skill to start work on a GitHub issue. It synthesizes all relevant context (specs, retrospective, issue details) using the Gemini CLI to generate a step-by-step implementation plan, then creates a feature branch to begin work. Triggers include "start work on issue
npx claudepluginhub joshuarweaver/cascade-code-devops-misc-1 --plugin bodangren-git-workflowThis skill uses the workspace's default tool permissions.
To kickstart the development workflow for a single GitHub issue by generating a comprehensive, context-aware implementation plan. This skill leverages the Gemini CLI to synthesize issue details, relevant specifications, and historical learnings from the project retrospective into a clear, actionable plan. It then creates an isolated feature branch, setting the stage for focused, spec-driven dev...
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
To kickstart the development workflow for a single GitHub issue by generating a comprehensive, context-aware implementation plan. This skill leverages the Gemini CLI to synthesize issue details, relevant specifications, and historical learnings from the project retrospective into a clear, actionable plan. It then creates an isolated feature branch, setting the stage for focused, spec-driven development.
Use this skill in the following situations:
main branch.gh CLI tool installed and authenticated.jq tool installed for JSON parsing.gemini CLI tool installed and authenticated.docs/ structure with specs and a RETROSPECTIVE.md.Instead of just viewing files, the skill synthesizes all relevant context into a coherent plan:
All work happens on a dedicated feature branch to:
main branch from work-in-progress.Each issue represents a single, well-defined task that can be completed and reviewed as a unit.
Determine which issue to work on. The user specifies the issue number (e.g., #45).
Execute the work-on-issue.sh script with the issue number:
bash scripts/work-on-issue.sh 45
The helper script automates these critical setup steps:
jq, a clean git status, and being on the main branch..md) in docs/specs/ or docs/changes/ and identifies RETROSPECTIVE.md.@file syntax) and calls the gemini CLI. It asks Gemini to produce a step-by-step implementation plan based on all provided information.feat/45-restructure-doc-indexer) and checks it out.After the script completes, carefully review the implementation plan generated by Gemini. This plan is your starting guide for the implementation, synthesized from all available project context.
With the plan and feature branch ready:
Symptom: Script reports uncommitted changes or that you are not on the main branch.
Solution: Commit, stash, or discard your changes. Switch back to the main branch before re-running the script.
jq or gemini ToolSymptom: Script reports that jq or gemini is not installed.
Solution: Install the required tool. For jq, use sudo apt install jq or brew install jq. For gemini, follow its official installation instructions.
Symptom: The script fails while generating the implementation plan, showing an error from the gemini command.
Solution:
gemini CLI is installed correctly and is in your system's PATH.gemini auth.Symptom: The script runs, but the plan doesn't seem to include context from a spec file you expected. Solution:
docs/specs/my-spec.md). The script only includes files that are directly mentioned.feat/ISSUE_NUMBER-kebab-case-title.