gstredny/tdd-planning
scaffold/.codex/skills/tdd-planning/SKILL.md
Plan implementation work before coding by defining public interfaces, real collaborator boundaries, and vertical RED or VERIFY slices.
$ install --global
skillsauthnpx skillsauth add gstredny/lauren-loop tdd-planningInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 5, 2026, 3:32 PM4.9s1 file scanned
SKILL.md
- name:
- tdd-planning
- description:
- Plan implementation work before coding by defining public interfaces, real collaborator boundaries, and vertical RED or VERIFY slices.
TDD Planning
Use this skill after the goal is clear but before writing the first test or implementation edit.
When to Use
- New feature work with multiple behaviors
- Bug fixes where the existing interface is unclear
- Refactors that need an explicit observable-behavior contract
Skip it for trivial documentation edits or one-line fixes with one obvious test.
Planning Questions
- What public interface or observable behavior will prove the change works?
- Which collaborators must stay real, and which boundaries are truly external and mockable?
- What is the smallest first RED slice that proves real progress?
- Which steps are not meaningfully testable and should be called out as
VERIFYinstead?
Output Shape
Produce a short plan with:
- Interface under test
- Allowed mocks and required real collaborators
- Ordered vertical slices, one behavior per slice
- Explicit
VERIFYsteps for non-testable work
Rules
- Keep tests on observable behavior through public entry points.
- Do not batch-write tests up front.
- If the plan changes task scope materially, update the task file before coding.
Related Skills
gstredny/workflow
development
VerifiedTrustedCommunity
Follow the end-to-end delivery workflow for planning, task-file management, execution, code review, verification, and closeout without relying on Claude-specific hooks or command conventions.
1SKILL.mdUpdated Apr 5, 2026
gstredny/task-manager
development
VerifiedTrustedCommunity
Manage task files in docs/tasks/open and docs/tasks/closed, including task discovery, resume/create rules, append-only Attempts logging, Left Off At updates, Code Review field handling, and needs verification closeout.
1SKILL.mdUpdated Apr 5, 2026
gstredny/plan-review
data-ai
VerifiedTrustedCommunity
Review an implementation plan before execution to catch missed success criteria, scope creep, constraint violations, unverified assumptions, and missed reuse opportunities.
1SKILL.mdUpdated Apr 5, 2026
gstredny/code-review
development
VerifiedTrustedCommunity
Run code review with findings-first, severity-ordered output focused on bugs, regressions, edge cases, error handling, performance, architecture, caller impact, and missing tests.
1SKILL.mdUpdated Apr 5, 2026