Claude Skills by GxFn

Use in a Wakeflow Test window when a test card, smoke run, runtime observation, or user report shows a failing or uncertain behavior that needs reproduction, root-cause tracing, and ownership classification.

Use in a Wakeflow Test window to review target evidence, diffs, reports, runtime logs, or validation output and return blockers, missing evidence, residual risk, and a controller-ready interpretation.

Use when the Test window needs a source-derived chain plan, node-by-node validation, isolated repair evidence, scoped round verdicts, before/after metrics, or a progressive validation plan for a long workflow.

Use in a Wakeflow Test window to design behavior-focused regression coverage from a confirmed bug, requirement, test card, or target result without coupling to private implementation details.

Use in a Wakeflow Test window to design a risk-based validation plan for a controller test card, real-project scenario, release check, runtime observation, or cross-repository integration question.

Use in a Wakeflow Design window to prepare a compact handoff for controller intake from clarified requirements, option plans, requirement designs, and Design signals.

Use in a Wakeflow Design window when a clarified requirement needs multiple implementation, architecture, sequencing, or rollout options before controller or user confirmation.

Use in a Wakeflow Design window when a user idea, controller request, handoff candidate, or product change needs clarification before it can become an original plan, requirement design, TODO candidate, or controller decision.

Use in a Wakeflow Design window to turn a clarified and confirmed requirement, or a non-bug outcome mismatch that needs redesign, into a controller-intake-ready requirement design with user stories, decisions, tests, non-goals, and acceptance criteria.

Use in a Wakeflow Design window to break a confirmed requirement design into vertical-slice TODO or task-package candidates for controller intake.

Use in a Wakeflow Test window when a test card, smoke run, runtime observation, or user report shows a failing or uncertain behavior that needs reproduction, root-cause tracing, and ownership classification.

Use in a Wakeflow Test window to review target evidence, diffs, reports, runtime logs, or validation output and return blockers, missing evidence, residual risk, and a controller-ready interpretation.

Use when the Test window needs a source-derived chain plan, node-by-node validation, isolated repair evidence, scoped round verdicts, before/after metrics, or a progressive validation plan for a long workflow.

Use in a Wakeflow Test window to design behavior-focused regression coverage from a confirmed bug, requirement, test card, or target result without coupling to private implementation details.

Use in a Wakeflow Test window to design a risk-based validation plan for a controller test card, real-project scenario, release check, runtime observation, or cross-repository integration question.

Use in a Wakeflow Design window to prepare a compact handoff for controller intake from clarified requirements, option plans, requirement designs, and Design signals.

Use in a Wakeflow Design window when a clarified requirement needs multiple implementation, architecture, sequencing, or rollout options before controller or user confirmation.

Use in a Wakeflow Design window when a user idea, controller request, handoff candidate, or product change needs clarification before it can become an original plan, requirement design, TODO candidate, or controller decision.

Use in a Wakeflow Design window to turn a clarified and confirmed requirement, or a non-bug outcome mismatch that needs redesign, into a controller-intake-ready requirement design with user stories, decisions, tests, non-goals, and acceptance criteria.

Use in a Wakeflow Design window to break a confirmed requirement design into vertical-slice TODO or task-package candidates for controller intake.

Use in a Wakeflow Test window when a test card, smoke run, runtime observation, or user report shows a failing or uncertain behavior that needs reproduction, root-cause tracing, and ownership classification.

Use in a Wakeflow Test window to review target evidence, diffs, reports, runtime logs, or validation output and return blockers, missing evidence, residual risk, and a controller-ready interpretation.

Use when the Test window needs a source-derived chain plan, node-by-node validation, isolated repair evidence, scoped round verdicts, before/after metrics, or a progressive validation plan for a long workflow.

Use in a Wakeflow Test window to design behavior-focused regression coverage from a confirmed bug, requirement, test card, or target result without coupling to private implementation details.

Use in a Wakeflow Test window to design a risk-based validation plan for a controller test card, real-project scenario, release check, runtime observation, or cross-repository integration question.

Use in a Wakeflow Design window to prepare a compact handoff for controller intake from clarified requirements, option plans, requirement designs, and Design signals.

Use in a Wakeflow Design window when a clarified requirement needs multiple implementation, architecture, sequencing, or rollout options before controller or user confirmation.

Use in a Wakeflow Design window when a user idea, controller request, handoff candidate, or product change needs clarification before it can become an original plan, requirement design, TODO candidate, or controller decision.

Use in a Wakeflow Design window to turn a clarified and confirmed requirement, or a non-bug outcome mismatch that needs redesign, into a controller-intake-ready requirement design with user stories, decisions, tests, non-goals, and acceptance criteria.

Use in a Wakeflow Design window to break a confirmed requirement design into vertical-slice TODO or task-package candidates for controller intake.

Use in a Wakeflow Test window when a test card, smoke run, runtime observation, or user report shows a failing or uncertain behavior that needs reproduction, root-cause tracing, and ownership classification.

Use in a Wakeflow Test window to review target evidence, diffs, reports, runtime logs, or validation output and return blockers, missing evidence, residual risk, and a controller-ready interpretation.

Use when the Test window needs a source-derived chain plan, node-by-node validation, isolated repair evidence, scoped round verdicts, before/after metrics, or a progressive validation plan for a long workflow.

Use in a Wakeflow Test window to design behavior-focused regression coverage from a confirmed bug, requirement, test card, or target result without coupling to private implementation details.

Use in a Wakeflow Test window to design a risk-based validation plan for a controller test card, real-project scenario, release check, runtime observation, or cross-repository integration question.

Use in a Wakeflow Design window to prepare a compact handoff for controller intake from clarified requirements, option plans, requirement designs, and Design signals.

Use in a Wakeflow Design window when a clarified requirement needs multiple implementation, architecture, sequencing, or rollout options before controller or user confirmation.

Use in a Wakeflow Design window when a user idea, controller request, handoff candidate, or product change needs clarification before it can become an original plan, requirement design, TODO candidate, or controller decision.

Use in a Wakeflow Design window to turn a clarified and confirmed requirement, or a non-bug outcome mismatch that needs redesign, into a controller-intake-ready requirement design with user stories, decisions, tests, non-goals, and acceptance criteria.

Use in a Wakeflow Design window to break a confirmed requirement design into vertical-slice TODO or task-package candidates for controller intake.

Use in a Wakeflow Test window when a test card, smoke run, runtime observation, or user report shows a failing or uncertain behavior that needs reproduction, root-cause tracing, and ownership classification.

Use in a Wakeflow Test window to review target evidence, diffs, reports, runtime logs, or validation output and return blockers, missing evidence, residual risk, and a controller-ready interpretation.

Use when the Test window needs a source-derived chain plan, node-by-node validation, isolated repair evidence, scoped round verdicts, before/after metrics, or a progressive validation plan for a long workflow.

Use in a Wakeflow Test window to design behavior-focused regression coverage from a confirmed bug, requirement, test card, or target result without coupling to private implementation details.

Use in a Wakeflow Test window to design a risk-based validation plan for a controller test card, real-project scenario, release check, runtime observation, or cross-repository integration question.

Use in a Wakeflow Design window to prepare a compact handoff for controller intake from clarified requirements, option plans, requirement designs, and Design signals.

Use in a Wakeflow Design window when a clarified requirement needs multiple implementation, architecture, sequencing, or rollout options before controller or user confirmation.

Use in a Wakeflow Design window when a user idea, controller request, handoff candidate, or product change needs clarification before it can become an original plan, requirement design, TODO candidate, or controller decision.

Use in a Wakeflow Design window to turn a clarified and confirmed requirement, or a non-bug outcome mismatch that needs redesign, into a controller-intake-ready requirement design with user stories, decisions, tests, non-goals, and acceptance criteria.

Use in a Wakeflow Design window to break a confirmed requirement design into vertical-slice TODO or task-package candidates for controller intake.