workflow-patterns
Implement Tasks with TDD Workflow
Task plans can drift when implementation, tests, commits, and approvals are handled inconsistently. This skill provides a structured TDD workflow with checkpoints, verification gates, and git tracking.
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/sickn33-workflow-patterns.md and its manifest at https://skillstore.io/api/skills/sickn33-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". Start the next task in the current phase.
Expected outcome:
The assistant identifies the next unchecked task, marks it in progress, and proposes the first failing test.
Using "workflow-patterns". Complete task 2.1 after tests pass.
Expected outcome:
The assistant summarizes changed files, records verification status, and prepares task completion notes with a commit reference.
Using "workflow-patterns". Finish phase one and request approval.
Expected outcome:
The assistant presents automated verification results, manual checks, and a clear request for human approval before continuing.
Security Audit
SafeAll static findings are false positives. The flagged backticks are markdown formatting for file paths or example SHAs, and blocker entries are ordinary TDD checklist text. No evidence found for prompt injection, data exfiltration, malicious network activity, or hidden execution intent.
Risk Factors
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/sickn33-workflow-patterns/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-workflow-patterns?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-workflow-patterns?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-workflow-patterns/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-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
sickn33. (2026). workflow-patterns security audit report (audit version 5) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/sickn33-workflow-patterns/audits/5BibTeX citation
@techreport{sickn33-sickn33-workflow-patterns-2026,
author = {sickn33},
title = {workflow-patterns security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-workflow-patterns/audits/5},
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 5)"
version: "1.0.0"
type: report
authors:
- name: "sickn33"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/sickn33-workflow-patterns/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-workflow-patterns:audit:5"
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 Planned Tasks
Follow a plan file through one task at a time with tests, commits, and progress updates.
Review Phase Readiness
Check that tests, coverage, documentation, and manual verification are complete before a checkpoint.
Coordinate AI Coding Agents
Give Claude, Codex, or Claude Code a repeatable workflow for task execution and status tracking.
Try These Prompts
Use workflow-patterns to find the next pending task in plan.md. Mark it in progress and explain the first test to write.
Use workflow-patterns for this task. Write failing tests first, implement the smallest change, then refactor after tests pass.
Use workflow-patterns to prepare a phase checkpoint. List automated results, manual verification items, and approval requirements.
Use workflow-patterns to document this implementation deviation. Update the plan notes, affected requirements, and verification steps.
Best Practices
- Write the failing test before implementation work starts.
- Keep commits focused on one logical task or checkpoint.
- Record deviations and approval decisions in the plan files.
Avoid
- Do not skip the RED step to save time.
- Do not continue past a checkpoint without explicit approval.
- Do not mark a task complete while tests or quality gates fail.
Frequently Asked Questions
What workflow does this skill support?
Can it be used outside Conductor projects?
Does it run tests automatically?
Does it require git?
How does it handle blocked tasks?
Which AI tools can use it?
Developer Details
Author
sickn33License
MIT
Author version
v1.0.0
Skillstore revision
r1
Ref
f93e9bb0daca99badb6a7e574b97737155d57cb3
Maintenance freshness
7/18/2026
Usage
7 downloads ยท 161 views
File structure