flow-tdd
Enforce Test-First Development
Teams lose confidence when code is written before tests and failures are not tracked. This skill guides Claude, Codex, and Claude Code through strict TDD steps with failure checks and error logs.
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "flow-tdd" from https://skillstore.io/skills/dimon94-flow-tdd.md and its manifest at https://skillstore.io/api/skills/dimon94-flow-tdd/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "flow-tdd". Add validation for invalid email addresses using flow-tdd.
Expected outcome:
The agent first proposes a failing validation test, confirms why it should fail, then adds the minimal validation behavior.
Using "flow-tdd". A test failed during implementation.
Expected outcome:
The agent records the phase, failure type, message summary, root cause, resolution, and prevention note in the error log.
Using "flow-tdd". Existing implementation was written before tests.
Expected outcome:
The agent asks for confirmation before any destructive cleanup and offers a non-destructive test-first recovery plan.
Security Audit
High RiskMost static findings are false positives caused by Markdown fences, regex examples, and repository-relative links. One semantic risk remains: the skill tells agents to delete implementation code when TDD was not followed. No evidence of hidden command execution, network access, credential access, or prompt injection was found.
Confirmed security concerns (1)
Risk Factors
⚙️ External commands (21)
📁 Filesystem access (4)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/dimon94-flow-tdd/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/dimon94-flow-tdd?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/dimon94-flow-tdd?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/dimon94-flow-tdd/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/dimon94-flow-tdd.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
Dimon94. (2026). flow-tdd security audit report (audit version 8) [Author version unspecified]. Skillstore. https://skillstore.io/skills/dimon94-flow-tdd/audits/8BibTeX citation
@techreport{dimon94-dimon94-flow-tdd-2026,
author = {Dimon94},
title = {flow-tdd security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/dimon94-flow-tdd/audits/8},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "flow-tdd security audit report (audit version 8)"
version: "unspecified"
type: report
authors:
- name: "Dimon94"
date-released: "2026-07-05"
url: "https://skillstore.io/skills/dimon94-flow-tdd/audits/8"
identifiers:
- type: other
value: "skillstore:dimon94-flow-tdd:audit:8"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Add a Feature with TDD
Use the skill to write a failing test, implement the smallest fix, and refactor only after tests pass.
Review Agent Coding Discipline
Use the checklist to verify that an AI coding session followed test-first development.
Track Test and Build Failures
Use the error logging workflow to capture failures, root causes, resolutions, and prevention notes.
Try These Prompts
Use flow-tdd for this change. First write one failing test, show the failure result, then implement the smallest passing change.
Use flow-tdd to recover test-first discipline for this existing change. Propose a non-destructive plan before changing or removing any code.
Review these tests using flow-tdd quality rules. Identify tests that pass without proving behavior, then propose stronger failing tests.
Apply flow-tdd across red, green, and refactor phases for this requirement. Record each failure, implementation step, and cleanup decision.
Best Practices
- Ask the agent to show the failing test result before implementation.
- Keep implementation scoped to one failing behavior at a time.
- Review destructive cleanup steps before code is removed.
Avoid
- Writing production code before a failing test exists.
- Accepting tests that pass immediately without investigation.
- Treating broad refactors as part of the green step.