Daniel C
Community@dchavez3395 · Winnipeg, Manitoba
Daniel C maintains nine engineering discipline skills covering git worktree isolation, test-driven development, systematic debugging, plan execution, and verified completion for software teams.
Agent Skills by Daniel C
Showing 9 vetted skills indexed across 1 GitHub repositories.
dchavez3395using-git-worktrees
Creates isolated git worktrees or subagent workspaces before starting feature implementation work.
dchavez3395test-driven-development
Enforces red-green-refactor test-driven development before writing any production code.
dchavez3395finding-duplicate-functions
Detects semantically duplicate functions across a codebase using extraction and LLM-based intent clustering.
dchavez3395systematic-debugging
Diagnose bugs through a four-phase root cause investigation process before proposing fixes.
dchavez3395using-superpowers
Enforces discovery and invocation of workspace skills before any agent response or action.
dchavez3395executing-plans
Executes written implementation plans with task tracking, verification checkpoints, and review gates.
dchavez3395finishing-a-development-branch
Guides completion of development branches through structured merge, PR, keep, or discard options.
dchavez3395writing-plans
Generates detailed multi-task implementation plans from specs with TDD steps and exact file paths.
dchavez3395verification-before-completion
Enforces running verification commands and reading output before claiming work is complete.
Frequently Asked Questions About Daniel C
FAQPage SchemaWhat tasks can I accomplish with dchavez3395's skills?▼
You can isolate feature work with git worktrees, apply test-driven development before writing code, systematically debug failures, detect duplicate functions in codebases, write and execute implementation plans with review checkpoints, finish development branches via merge or PR, and verify completion with evidence before claiming success.
Who should use these engineering discipline skills?▼
Software engineers and developers working on features or bugfixes benefit most, especially those maintaining LLM-generated codebases prone to duplicate functions. Teams needing structured plan execution, branch completion decisions, and evidence-based verification before declaring work done are the target personas.
How do the skills fit into a development session?▼
Start with using-superpowers to locate and invoke skills, then write plans for multi-step tasks, isolate work via git worktrees, apply test-driven development during implementation, debug systematically when failures occur, and finish branches with structured merge, PR, or cleanup options after verification passes.
What prerequisites do these skills require?▼
Skills are invoked conditionally based on context: a spec or requirements for writing-plans, a written implementation plan for executing-plans, a bug or test failure for systematic-debugging, and passing tests for finishing-a-development-branch. Git availability supports the worktree fallback for workspace isolation.
How does verification-before-completion prevent false success claims?▼
It mandates running verification commands and confirming actual output before any claim that work is complete, fixed, or passing. The rule is evidence before assertions: no success statement is permitted without executed command results backing it, eliminating premature or unsupported completion reports.