skills.rest
rochaluiz8888
rochaluiz8888COMMUNITY
Explore all skills by this author →
WebsiteGitHub

conductor

Enforce plan.md-driven lifecycle governance with conventional commits and TDD cycles.

Updated Mar 19, 2026
Search Tags:#workflow#tdd#plan.md#conductor#ci#project-management
One-click install
npx skills add https://github.com/rochaluiz8888/claude-code-skills --skill conductor-rochaluiz8888
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: conductor
Source: https://github.com/rochaluiz8888/claude-code-skills/tree/main/conductor
Command: npx skills add https://github.com/rochaluiz8888/claude-code-skills --skill conductor-rochaluiz8888

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Conductor provides a structured project lifecycle that enforces plan.md as the single source of truth, standardizes commits, TDD-driven development, and phased checkpoints with verification reports.

Core Features & Use Cases

  • Plan-driven task tracking in plan.md when starting new feature tracks
  • Red/Green/Refactor driven development with automated verification
  • Conventional commits with git notes and CI-friendly workflows
  • Phase checkpoints that document progress and verification outcomes
  • Auto-triggers when plan.md exists in the project root to kick off the workflow

Quick Start

Create a plan.md with an initial task list and acceptance criteria, then follow the conductor workflow to drive development through red/green/refactor cycles and phased checkpoints.

Frequently Asked Questions about conductor

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

FAQPage Schema
How do I enforce a plan.md file as the single source of truth for project management?▼

You can enforce plan.md as the single source of truth by automating project lifecycle governance, standardizing conventional commits, and applying phase-based verification to track milestones and feature development.

How do I automate TDD cycles and maintain test coverage in a CI workflow?▼

Automate TDD cycles by driving development through Red/Green/Refactor stages with automated verification, enforcing conventional commits and requiring over 80% test coverage for new changes within a CI-friendly workflow.

What is the best way to structure phased checkpoints for feature development?▼

Phased checkpoints document progress and verification outcomes by enforcing plan-driven milestones, ensuring feature development transitions only after completing TDD cycles and passing phase-based verification reports.

Can I use conventional commits with git notes for plan-driven milestones?▼

Yes, conventional commits with git notes are supported to maintain a CI-friendly workflow, ensuring that every phase-based checkpoint and plan.md update aligns with your project lifecycle governance.

How do I trigger a plan-driven workflow automatically in my repository?▼

The workflow auto-triggers when a plan.md file exists in your project root, immediately kicking off the structured lifecycle governance, TDD enforcement, and phase-based verification processes.

Do I need to write acceptance criteria in plan.md before starting feature tracks?▼

Yes, you need to create a plan.md with an initial task list and acceptance criteria to establish the source of truth before the conductor workflow can drive development through red/green/refactor cycles.

Related Skills

Explore More Software Engineering Skills→
FlavioCFOliveiraFlavioCFOliveira

task-creator

Convert planning discussions into structured Groadmap tasks and sprints.

Community
Advanced
edfentonedfenton
3

shared-changelog

Generate CHANGELOG.md from Git history using conventional commits.

Community
Advanced
YuriNakayamaYuriNakayama

tdd

Implement TDD workflows with RED, GREEN, and REFACTOR cycles using TypeScript and Jest.

Community
Advanced
hoanghd218hoanghd218

plans-kanban

Visualize and manage implementation plans with a Kanban dashboard.

Community
Advanced