phase-refinement

Coordinate testing and feedback incorporation during the Refinement phase of the epic-stage-workflow.

3|2|Updated Dec 16, 2025
One-click install
npx skills add https://github.com/jakekausler/claude-code-workflow --skill phase-refinement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phase-refinement
Source: https://github.com/jakekausler/claude-code-workflow/tree/main/skills/phase-refinement
Command: npx skills add https://github.com/jakekausler/claude-code-workflow --skill phase-refinement

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Refinement phase requires coordinated testing, feedback capture, and iterative improvement across frontend and backend workstreams; this skill provides structure and guardrails to ensure robust validation before Finalize.

Core Features & Use Cases

  • Guided Refinement testing across Frontend and Backend: coordinates desktop and mobile testing, triages issues, and records results.
  • Feedback incorporation and iteration: standardizes how feedback is collected, prioritized, and turned into actionable changes.
  • Phase governance and exit gates: enforces mandatory checks, updates tracking documents, and resets approvals as needed.

Quick Start

Initiate refinement by loading the shared epic-stage-workflow rules and begin desktop and mobile testing with feedback logging.

Frequently Asked Questions about phase-refinement

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

FAQPage Schema
How do I coordinate frontend and backend refinement testing across different viewports?

Rigorous refinement testing coordinates frontend and backend validation across desktop and mobile viewports, triages issues, and records results to ensure robust validation before the finalize phase.

What is the best way to incorporate feedback during an iterative refinement workflow?

Feedback incorporation during refinement standardizes how feedback is collected, prioritized, and turned into actionable changes across multi-session iterations for continuous improvement.

How do I enforce exit gates and mandatory checks before finalizing an epic?

Phase governance enforces exit gates by applying mandatory entry conditions, explicit approvals, and tracking updates to stage and epic tracking artifacts before allowing progression.

Can I use this refinement process for multi-session iteration workflows?

Yes, this refinement workflow supports multi-session iteration by handling session boundaries, resetting approvals as needed, and maintaining continuous feedback logging across development periods.

What are the mandatory entry conditions required to start refinement testing?

Mandatory entry conditions require loading shared epic-stage-workflow rules and beginning desktop and mobile testing with feedback logging before initiating the structured refinement phase.

Why does my epic workflow require explicit approvals during the refinement phase?

Explicit approvals during refinement enforce exit-gate discipline, ensuring all feedback is incorporated, testing is complete, and tracking documents are updated before advancing downstream.