John Stegeman
Community@johnstegeman
John Stegeman's skill registry enforces disciplined software engineering practices: test-driven development, systematic debugging, git worktree isolation, code review rigor, and multi-repo issue tracking.
Agent Skills by John Stegeman
Showing 14 vetted skills indexed across 1 GitHub repositories.
johnstegemanusing-git-worktrees
Creates isolated git worktree workspaces with native tool detection and baseline test verification.
johnstegemantest-driven-development
Enforces red-green-refactor test-driven development cycles for features, bugfixes, and code modifications.
johnstegemansystematic-debugging
Diagnose bugs through a four-phase root-cause investigation workflow before proposing fixes.
johnstegemanusing-superpowers
Enforces skill discovery and invocation before acting on any task in Pi sessions.
johnstegemandispatching-parallel-agents
Dispatches independent tasks to parallel subagents with focused prompts and isolated context.
johnstegemanexecuting-plans
Executes written implementation plans in batches with beads task tracking and review checkpoints.
johnstegemanfinishing-a-development-branch
Guides merging, pushing, or preserving a completed development branch with test verification and worktree cleanup.
johnstegemanbrainstorming
Guides collaborative dialogue to turn ideas into approved design specs before implementation.
johnstegemanwriting-plans
Converts approved specs into bite-sized implementation task beads with TDD steps and acceptance criteria.
johnstegemanrequesting-code-review
Dispatches a code reviewer subagent to evaluate git diffs against requirements before merging.
johnstegemanreceiving-code-review
Guides verification and implementation of code review feedback with technical rigor.
johnstegemanverification-before-completion
Enforces running verification commands and checking output before claiming work is complete.
johnstegemansubagent-driven-development
Executes implementation plans by dispatching fresh implementer subagents per task with per-task and final code reviews.
johnstegemanbeads
Manages beads task issues across multi-repo umbrella workspaces via in-process beads_* tools.
Frequently Asked Questions About John Stegeman
FAQPage SchemaWhat tasks can I accomplish using John Stegeman's skills?▼
You can enforce test-driven development before writing implementation code, debug failures systematically, isolate feature work in git worktrees, write and execute implementation plans with review checkpoints, request and receive code reviews rigorously, verify completion with evidence, and manage beads issues across multiple repositories.
Who should use these skills?▼
Software engineers and developers who want disciplined engineering practices: TDD practitioners, teams doing structured code review, developers managing parallel feature branches via git worktrees, and engineers tracking tasks and epics across multi-repo umbrella workspaces using beads.
How do the skills fit into a development session?▼
Start with brainstorming and writing-plans before touching code, isolate work with git worktrees, implement via test-driven development or subagent-driven execution, debug failures systematically, then request code review, verify results with actual command output, and finish the branch with a merge decision.
What prerequisites or dependencies do these skills require?▼
Skills rely on native git capabilities including worktree support, a test suite for TDD and verification steps, and the beads (bd) issue system with in-process beads_* tools (pi-beads-lean) for multi-repo task management. Most skills are marked disable-model-invocation and trigger on specific development situations.