phase-workflow-runner

UBAIDRAZA1's avatarfrom UBAIDRAZA1

Runs a complete phase workflow: audit existing work, fill gaps, run tests, verify acceptance criteria, and report readiness for next phase. Use when user asks to run or complete a project phase.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 5, 2026
[Project Management]

When & Why to Use This Skill

The Phase Workflow Runner is a sophisticated Claude skill designed to automate and standardize the execution of project phases. It follows a deterministic workflow—comprising auditing, gap filling, testing, and verification—to ensure that project milestones are met with high precision. By integrating test-driven principles and automated documentation updates, it streamlines the transition between project stages while maintaining code integrity and quality.

Use Cases

  • Automated Phase Transitions: Seamlessly move from development to production readiness by automatically auditing code, running test suites, and verifying acceptance criteria.
  • Technical Debt Reduction: Use the audit and gap-filling steps to identify missing tests or incomplete implementations in existing projects, ensuring a solid foundation for new features.
  • Project Status Synchronization: Automatically update project tracking files like tasks.md and spec.md based on actual implementation progress, providing a real-time 'source of truth' for the team.
  • Quality Assurance Gatekeeping: Implement a mandatory verification gate that prevents moving to the next project phase until all tests pass and all documentation is updated, ensuring zero-defect handovers.
namephase-workflow-runner
descriptionRuns a complete phase workflow: audit existing work, fill gaps, run tests, verify acceptance criteria, and report readiness for next phase. Use when user asks to run or complete a project phase.

Phase Workflow Runner

This skill executes a deterministic, repeatable phase workflow.

Core Principles

  • Never overwrite existing working code
  • Never redo completed tasks
  • Always audit before action
  • Tests define correctness
  • Phase completion requires verification

Workflow Steps (MANDATORY)

1. Phase Audit

  • Inspect project structure
  • Read relevant spec and tasks files
  • Identify:
    • Completed items
    • Missing files
    • Failing or absent tests
    • Partial implementations

Produce a concise audit report before proceeding.

2. Gap Filling

Only after audit:

  • Create missing source files
  • Create missing test files (RED)
  • Implement minimal code to pass tests (GREEN)
  • Refactor if required

Rules:

  • Do not modify completed, passing code
  • Do not remove existing functionality

3. Execution & Verification

  • Run full test suite
  • Perform manual smoke checks if CLI/project requires
  • Verify acceptance criteria from spec.md

4. Documentation Update

  • Update tasks.md checkboxes
  • Mark checkpoints complete
  • Add short completion summary

5. Completion Gate

If all criteria pass:

  • Declare phase COMPLETE
  • Ask user: “Phase X complete. Proceed to Phase X+1?”

If not:

  • Report blockers and stop

Safety Rules

  • Never hallucinate missing work
  • Never assume tests exist
  • Never skip audit
  • Never continue if tests fail

Output Format

Always output:

  1. Audit Summary
  2. Actions Taken
  3. Test Results
  4. Acceptance Criteria Status
  5. Next Step Recommendation