phase-test

Orchestrates seven specialist lenses to test a completed phase and produce a deploy gate decision.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/scoots31/engineering-playbook --skill phase-test-scoots31
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phase-test
Source: https://github.com/scoots31/engineering-playbook/tree/main/skills/phase-test
Command: npx skills add https://github.com/scoots31/engineering-playbook --skill phase-test-scoots31

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Slice-level QA confirms each piece was built correctly, but nothing verifies the whole phase works as an integrated product with real data. This Skill runs a structured end-to-end phase test and produces a single gate decision: ready to deploy or hold with specific items to resolve. ## Core Features & Use Cases - Seven-stage specialist sequence: environment readiness, use case creation, data validation, scenario testing, regression checking, acceptance review, and a final gate decision. - Derived test plan: builds test scenarios from the discovery brief, design artifact, edge cases, done criteria, and to-be process map rather than inventing them. - Gate decision with receipts: outputs a HOLD or OPEN verdict with named open issues, and appends a phase completion record to the backlog when the gate opens. - Use Case: After all Phase 1 slices reach In Test, invoke the skill to walk every user journey against real APIs, catch regressions between slices, and confirm the phase delivers the original discovery intent before deploying. ## Quick Start Invoke the phase test by saying: run the phase test for this phase now that all slices are in test.

Frequently Asked Questions about phase-test

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

FAQPage Schema
How do I test a complete development phase before deploying?

Invoke the phase test once all slices in the phase show In Test status. It runs environment readiness, derives a test plan from the discovery brief and design, validates real data flows, walks every scenario, checks regressions, and issues a gate decision of OPEN or HOLD.

What is the difference between slice QA and phase testing?

Slice QA verifies each slice against its done criteria in isolation. Phase testing verifies the slices working together as a product: real data, full user journeys, integration points between screens, and the original intent from the discovery brief.

When should I invoke the phase test skill?

Invoke it when all current-phase slices are In Test, qa-triage items are resolved or deferred, integration deliverables are accepted, and scope is frozen. Do not invoke it while slices are still In Build or In QA, since testing an incomplete build gives unreliable results.

What happens when the phase test gate returns HOLD?

A HOLD lists the specific open issues blocking deployment. Fix those items, then re-test only the affected scenarios rather than re-running the full phase test. The gate opens once all hold items are cleared.

Does phase testing require re-running everything after a fix?

No. After resolving hold items, the tester re-runs only the failed scenarios, the regression specialist re-checks only affected slices, and environment and data stages re-run only if the fix touched config or APIs.