workflow-patterns

Implements TDD task lifecycles with phase checkpoints, git commits, and verification protocols.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/SanketAdlak/PDMProjectDesign --skill workflow-patterns-sanketadlak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-patterns
Source: https://github.com/SanketAdlak/PDMProjectDesign/tree/main/.agents/skills/workflow-patterns
Command: npx skills add https://github.com/SanketAdlak/PDMProjectDesign --skill workflow-patterns-sanketadlak

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It provides a disciplined, repeatable process for implementing tasks from a Conductor track plan, ensuring every change is test-driven, committed with traceable metadata, and verified through phase checkpoints before proceeding. ## Core Features & Use Cases - 11-Step TDD Task Lifecycle: Guides task selection, red-green-refactor cycles, coverage verification, commit creation, git notes, and plan.md status updates with commit SHAs. - Phase Completion Protocol: Runs full test suites, generates manual verification checklists, waits for user approval, and records checkpoint SHAs for semantic reversion. - Quality Gates & Deviation Handling: Enforces 80% coverage, linting, type safety, and security checks while documenting scope changes and technical deviations. - Use Case: While implementing a user-authentication track, follow the lifecycle to write failing tests for email validation, implement the minimum code, commit with a structured message and git note, then record the SHA in plan.md before requesting phase checkpoint approval. ## Quick Start Ask the assistant to implement the next pending task from the track's plan.md following the TDD workflow and checkpoint protocol.

Frequently Asked Questions about workflow-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement a task using a TDD workflow?

Follow the 11-step lifecycle: select the next pending task from plan.md, mark it in progress, write failing tests (RED), implement minimum code to pass (GREEN), refactor, verify 80% coverage, then commit with a structured message and record the SHA in plan.md.

How to create phase checkpoints in git for a project plan?

After all phase tasks complete, run the full test suite, generate a manual verification checklist, and wait for explicit user approval. Then create a checkpoint commit including all changes and record the checkpoint SHA in the plan.md checkpoints table.

What commit message format should I use for task-based development?

Use the conventional format type(scope): subject, with types like feat, fix, refactor, test, docs, and chore. Include bullet-point changes in the body and task and track references in the footer, plus a git note with a detailed summary.

What happens if tests fail after reaching the GREEN phase?

Do not proceed to refactor. Identify which test started failing, check whether a change broke existing behavior, revert to the last known green state, and re-approach the implementation before continuing.

When should I not proceed to the next phase in a checkpoint workflow?

Never proceed without explicit user approval of the verification checklist. If a checkpoint is rejected, note the reason in plan.md, create remediation tasks, complete them, and request approval again.