workflow-patterns – Agents & Automation skill for AI agents
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
Install the workflow-patterns skill with one command
Pick the tool you use, copy the command and paste it in your terminal. The skill lands in that tool's skills folder and is ready in your next session.
Claude Code
mkdir -p ~/.claude/skills && curl -fsSL https://skill.dn1nguoi.com/z/workflow-patterns-9771d.tgz | tar xz -C ~/.claude/skills
Call it in Claude Code: /workflow-patterns – then describe the task you want done.
Codex
mkdir -p ~/.codex/skills && curl -fsSL https://skill.dn1nguoi.com/z/workflow-patterns-9771d.tgz | tar xz -C ~/.codex/skills
Call it in Codex: $workflow-patterns – then describe the task you want done.
Hermes Agent
mkdir -p ~/.hermes/skills && curl -fsSL https://skill.dn1nguoi.com/z/workflow-patterns-9771d.tgz | tar xz -C ~/.hermes/skills
Call it in Hermes Agent: /workflow-patterns – then describe the task you want done.
DeepSeek
mkdir -p ~/.deepcode/skills && curl -fsSL https://skill.dn1nguoi.com/z/workflow-patterns-9771d.tgz | tar xz -C ~/.deepcode/skills
Call it in DeepSeek: /workflow-patterns – then describe the task you want done.
SKILL.md content
Workflow Patterns
Guide for implementing tasks using Conductor's TDD workflow, managing phase checkpoints, handling git commits, and executing the verification protocol that ensures quality throughout implementation.
When to Use This Skill
- Implementing tasks from a track's plan.md
- Following TDD red-green-refactor cycle
- Completing phase checkpoints
- Managing git commits and notes
- Understanding quality assurance gates
- Handling verification protocols
- Recording progress in plan files
Detailed patterns and worked examples
Detailed pattern documentation lives in references/details.md. Read that file when the navigation tier above is insufficient.
Best Practices
1. Never skip RED: Always write failing tests first
2. Small commits: One logical change per commit
3. Immediate updates: Update plan.md right after task completion
4. Wait for approval: Never skip checkpoint verification
5. Rich git notes: Include context that helps future understanding
6. Coverage discipline: Don't accept coverage below target
7. Quality gates: Check all gates before marking complete
8. Sequential phases: Complete phases in order
9. Document deviations: Note any changes from original plan
10. Clean state: Each commit should leave code in working state
11. Fast feedback: Run relevant tests frequently during development
12. Clear blockers: Address blockers promptly, don't work around them
Related skills
- find-complementary-founders – Use when an owner explicitly asks for a cofounder or project partner, or explicitly says…
- firecrawl-scraper – Deep web scraping, screenshots, PDF parsing, and website crawling using Firecrawl API…
- flowhunt-skill – Automation discovery audit skill. Walks through a 5-question workflow intake, then…
- folder-specific-claude-and-agents-md – Create folder-scoped CLAUDE.md and AGENTS.md guidance for future agents working in that…
- framework-migration-legacy-modernize – Orchestrate a comprehensive legacy system modernization using the strangler fig pattern…
- freshdesk-automation – Automate Freshdesk helpdesk operations including tickets, contacts, companies, notes…
- freshservice-automation – Automate Freshservice ITSM tasks via Rube MCP (Composio): create/update tickets, bulk…
- self-improving-agent – Curate the agent's own memory into durable project knowledge. Reviews Claude Code…