By tstapler
Enforces a structured, phased development workflow from requirements gathering through implementation, testing, and PR creation, with subagent-driven execution, spec compliance checks, code reviews, and TDD validation.
Phase 1 — Interview to capture requirements. Outputs: project_plans/<project>/requirements.md
Phase 2 — Parallel research across 4 dimensions. Outputs: project_plans/<project>/research/*.md
Phase 3 — Architecture + task breakdown. Outputs: project_plans/<project>/implementation/plan.md
Phase 4 — Map test coverage to requirements before writing a line of code. Outputs: project_plans/<project>/implementation/validation.md
Phase 5 — Execute plan via subagent dispatcher. START IN A FRESH SESSION.
Execute an implementation plan by dispatching fresh subagents per task with dual-review (spec compliance + code quality). Use when running sdd:5-implement or executing any multi-task implementation plan.
Enforce Red-Green-Refactor TDD cycle. Use when implementing any new class or method — write the failing test first, then make it pass. Never write production code before a failing test exists.
Modifies files
Hook triggers on file write and edit operations
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
These are the configuration for various machines I own. I make every attempt to do things in a cross platform manner when possible.
My primary machines run Manjaro Linux, and Ubuntu Linux. Typically, my Work computers are Macs. There are some bits to make the original Windows Subsystem for Linux work because I used Windows briefly at Work.
I install my dotfiles to a new machine by using this script. It clones this repo, and symlinks my dotfiles to my home directory using cfgcaddy a tool I wrote.
You can use alternatives such as GNU Stow or yadm which have more users and likely less bugs 😉.
The key idea is that you should keep your dotfiles in a git repo in somewhere like $HOME/dotfiles and then symlink them to your $HOME directory for them to be read by other tools.
Once you have that system setup, you can copy pieces of my configuration piecemeal. I don't recommend copying everything directly. This repo has grown pretty organically over the years so it contains a lot of configuration you may not
I a pretty comprehensive ZSH configuration
I use zplug as my package manager, you can find the packages in .zplug_packages.zsh. It is responsible for installing zsh packages as well as a few binaries.
The directory .shell contains several scripts that are sourced in the .zshrc, their names should be fairly self explanatory.
I'm a heavy Vim user, so I have configuration for Intellij's vim plugin as well as actual Vim split across a few different files
I am a polyglot when it comes to programming languages so I use asdf to manage installing different languages and versions across my machines in a consistant way.
.tool-versions sets the global language version used across the system.
I have some configuration for installing each of the language specific plugins in the file .shell/languages.sh.
npx claudepluginhub tstapler/dotfiles --plugin sddHarness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses
Feature development with code-architect/explorer/reviewer agents, CLAUDE.md audit and session learnings, and Agent Skills creation with eval benchmarking from Anthropic.
Reliable automation, in-depth debugging, and performance analysis in Chrome using Chrome DevTools and Puppeteer
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.