skilld
All skills
wshobson avatar

/workflow-patterns

@be57c0b
by Seth Hobsonwshobson/agents40k stars
4,281

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.

Ask your Agent

Use this Skill: https://skilld.dev/gh/wshobson/agents/workflow-patterns

This session only. Nothing lands on disk.

SKILL.md

≈50 tokens always: the name and description. ≈365 when used: this file. ≈3k more on demand in 1 file.

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

Source: SKILL.md on GitHub

Third-party checks

No alerts16d5 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    The skill provides guidelines and workflow patterns for Test-Driven Development (TDD), including standard code snippets for git and testing frameworks like pytest. No security risks or malicious behaviors were detected.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: LOW · No issues

  • Runlayer7mo

    1 file scanned · No issues

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Provenance

Signed by skilld at be57c0b. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 3 days ago.

Activeupdated 4 months ago

Capability

version
1.0.0

Topics

  • Testing
  • Git/VCS
  • workflow
  • tdd
  • conductor
  • quality-assurance
  • phase-management
  • verification

README badge

README badge for wshobson/agents/workflow-patterns

What it does

Guides implementation of tasks using Conductor's TDD workflow, including red-green-refactor cycles, phase checkpoints, git commit management, and verification protocols. Intended for developers following Conductor track plans who need to coordinate quality gates, test-first discipline, and progress tracking across task phases.

Generated from the current SKILL.md.

Frequently asked

What is Conductor and how does this skill relate to it?
Conductor is a TDD-based task implementation framework. This skill provides workflow patterns for following Conductor's red-green-refactor cycle, managing phase checkpoints, and executing its verification protocol.
Does this skill include detailed documentation?
Yes. Detailed pattern documentation and worked examples are in references/details.md, referenced when the main guidance is insufficient.
What should I do at phase checkpoints?
Update plan.md immediately after task completion and wait for checkpoint verification approval before proceeding. Never skip checkpoint verification.
How should I structure git commits?
Make one logical change per commit, ensure each commit leaves code in a working state, and include rich context in git notes to aid future understanding.
What are the key quality gates I need to check?
Run tests frequently during development, maintain coverage above target, follow the red-green-refactor cycle strictly, and verify all quality gates pass before marking tasks complete.

Generated from the current SKILL.md. These answers refresh after source changes.