Packs

12 packs

Build Feature with TDD Pipeline

Research, plan, implement with TDD, review, and commit a new feature.

5 skills · pack

Ship Feature with TDD

Deliver a new feature by writing specs, implementing incrementally with TDD, and verifying before completion.

6 skills · pack

Testing & Quality

Testing, TDD, code review, linting and debugging.

25 skills · pack

TDD Feature Development

Drive feature development by writing tests first, implementing, verifying, and committing via a gated pipeline.

10 skills · pack

Spec-Driven Development

Write a structured spec, plan vertical slices, and build iteratively with TDD and gated commits.

9 skills · pack

Pocock Engineering

Engineering workflow skills from Matt Pocock's skills repo (triage, to-issues, to-prd, tdd, prototype, diagnose, grill-with-docs, improve-codebase-architecture, zoom-out). Covers issue lifecycle, TDD, prototyping, architectural review, domain grilling, and PRD generation. NOT for: daily development workflow — install individual skills as needed.

7 skills · pack

Fix Defect with TDD

Reproduce a bug as a failing regression test, fix until green, review, and commit via a delegated pipeline.

9 skills · pack

Build MVP from Spec

Turn a design or spec document into a working MVP by planning thin vertical slices, scaffolding, then building iteratively with TDD and gated commits.

5 skills · pack

Datenschutzrecht

DSGVO/BDSG/TDDDG – PIA/DPIA, AVV-Review, Auskunft Art. 15, Datenpanne Art. 33/34, Drittlandstransfer Art. 44 ff. inkl. US-Transfer, DPF, SCC, TIA, Behördenpaket und Brückenskills zur Sanktionsverteidigung.

4 skills · pack

Sam Superpowers

Fork of obra/superpowers 5.0.7: the 14 core skills (TDD, debugging, collaboration patterns) with the mandatory-gate SessionStart injection replaced by a short judgment-based router. Skills are tools, not gates.

14 skills · pack

Code-writing and execution skills for the Han suite. Home of the tdd skill, which drives a feature or behavior through a BDD-framed red-green-refactor loop with an enforced observed-failure gate. Depends on han-core and han-communication; bundled by the han meta-plugin.

11 skills · pack

@alirezarezvani

Engineering Team

32 engineering skills: architecture, frontend, backend, fullstack, QA, DevOps, security, AI/ML, data engineering, Playwright (9 sub-skills), self-improving agent, Stripe integration, TDD guide, tech stack evaluator, Google Workspace CLI, a11y audit (WCAG 2.2), Azure cloud architect, GCP cloud architect, security pen testing, Snowflake development, adversarial-reviewer, ai-security, cloud-security,

16 skills · pack

Results for “tdd”

4 skills

2521-de-b6b4830f

Provides German data protection compliance guidance covering DSGVO, BDSG, and TDDDG, including legal bases, retention periods, cookie rules, and standard wording templates.

backend-mindset

Guides backend development across API design, authentication, security, performance, architecture, and testing, with decision guides and defaults for production-ready systems.

More results

Write code through a disciplined, BDD-framed Test-Driven Development loop: build a behavior test list, then drive each behavior through red-green-refactor with an enforced observed-failure gate. Use when the user wants to implement, build, or write code test-first, "do TDD", follow "red-green-refactor", drive code from tests, choose the next test by the Transformation Priority Premise (TPP) or ZOMBIES ordering, or grow a feature behavior-by-behavior with tests leading. This skill writes and changes code; it does not produce a test plan document (use automated-test-planning, or manual-test-planning for a plan a person runs by hand), review or audit existing code (use code-review), restructure existing code outside a TDD loop (use refactor), specify what a feature should do (use plan-a-feature), or find the root cause of a bug (use investigate). Runs its loop to completion without pausing for review; to review each behavior as it lands, use pairing.

automated-test-planning

Produce a standalone test plan by analyzing code for test coverage gaps and edge cases. Use when you need to create, generate, or draft a test plan for a branch, need to analyze test coverage, or need to identify what tests to write for specific files or directories. Does not produce a plain-language plan for a person to run tests by hand — use manual-test-planning for that. Does not write test code — use tdd to implement behavior test-first. Does not refine existing plans — use iterative-plan-review. Does not review code quality, security, or style — use code-review for full code review. Does not evaluate architectural testability or structural coupling — use architectural-analysis for architectural assessment.