workflow-patterns
Guide TDD Workflow Checkpoints
Teams often lose task status, test discipline, and commit traceability during implementation. This skill guides Claude, Codex, and Claude Code through TDD tasks, verification gates, and checkpoint commits.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "workflow-patterns" from https://skillstore.io/skills/wshobson-workflow-patterns.md and its manifest at https://skillstore.io/api/skills/wshobson-workflow-patterns/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.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 "workflow-patterns". I need to start the next task in my Conductor plan.
Expected outcome:
The assistant identifies the next unchecked task, marks it in progress, commits that status change, and starts with failing tests.
Using "workflow-patterns". Phase 1 looks complete. Prepare it for review.
Expected outcome:
The assistant runs automated checks, summarizes coverage, creates manual verification steps, and waits for explicit approval before checkpointing.
Using "workflow-patterns". The checkpoint was rejected because validation failed.
Expected outcome:
The assistant records the rejection reason, creates remediation work, fixes the failure, and repeats verification before asking for approval again.
Security Audit
SafeStatic analysis flagged Markdown backticks and checklist phrases in SKILL.md. Review found local git, test, coverage, lint, and checkpoint examples only. No executable code, dynamic command construction, exfiltration intent, reconnaissance behavior, or prompt injection attempt was found.
Risk Factors
⚙️ External commands (65)
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/wshobson-workflow-patterns/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/wshobson-workflow-patterns?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/wshobson-workflow-patterns?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/wshobson-workflow-patterns/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/wshobson-workflow-patterns.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
wshobson. (2026). workflow-patterns security audit report (audit version 4) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/wshobson-workflow-patterns/audits/4BibTeX citation
@techreport{wshobson-wshobson-workflow-patterns-2026,
author = {wshobson},
title = {workflow-patterns security audit report (audit version 4)},
institution = {Skillstore},
year = {2026},
number = {4},
url = {https://skillstore.io/skills/wshobson-workflow-patterns/audits/4},
note = {Author version 1.0.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "workflow-patterns security audit report (audit version 4)"
version: "1.0.0"
type: report
authors:
- name: "wshobson"
date-released: "2026-07-08"
url: "https://skillstore.io/skills/wshobson-workflow-patterns/audits/4"
identifiers:
- type: other
value: "skillstore:wshobson-workflow-patterns:audit:4"
description: "Skillstore immutable audit report identifier"
Compare variants
2 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
sickn33-workflow-patterns
2026-08-21
wshobson-workflow-patterns
2026-08-21
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Implement Plan Tasks
Follow a repeatable TDD cycle while moving through tasks in a Conductor plan.
Verify Phase Readiness
Check tests, coverage, manual verification items, and approval status before advancing a phase.
Recover From Failed Checks
Document failures, return to a known green state, and create remediation tasks for rejected checkpoints.
Try These Prompts
Use workflow-patterns to find the next pending task in plan.md, mark it in progress, and begin with failing tests.
Use workflow-patterns for this task. Write failing tests, implement the minimum fix, refactor safely, and report the verification commands you ran.
Use workflow-patterns to verify all phase tasks, run coverage and quality gates, create manual verification steps, and wait for approval.
Use workflow-patterns to document this deviation, update the plan and spec if needed, create remediation tasks, and retry checkpoint approval.
Best Practices
- Keep each task in a clean TDD cycle before starting another task.
- Commit status changes, implementation work, and plan updates as separate logical changes.
- Request explicit user approval before creating or advancing checkpoint commits.
Avoid
- Skipping failing tests and implementing directly.
- Combining unrelated task work in a single commit.
- Marking a phase complete before coverage and manual checks are reviewed.