(workflow) phase-3-build

Coordinates phase-3 build workflow with gated quality checks across frontend, backend, DevOps, and PR validation.

1|Updated Mar 20, 2026
One-click install
npx skills add https://github.com/stericishere/skills --skill workflow-phase-3-build
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: (workflow) phase-3-build
Source: https://github.com/stericishere/skills/tree/main/%28workflow%29%20phase-3-build
Command: npx skills add https://github.com/stericishere/skills --skill workflow-phase-3-build

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Phase 3 build processes often suffer from misalignment between feature discovery, specification, and release gating. This Skill codifies a structured, multi-step workflow that enforces quality gates, traceability, and predictable delivery across frontend, backend, and DevOps tasks.

Core Features & Use Cases

  • End-to-end phase-3 workflow from feature discovery to PR merge with gated checks.
  • Centralizes steps for feature list creation, user stories, specs, prioritization, worktrees, QA, and reviews.
  • Supports multi-model reviews and ADR-driven decisions to reduce rework.

Quick Start

Initialize the phase-3 build workflow by triggering Step 1 to create a prioritized feature list and proceed through the gated steps.

Frequently Asked Questions about (workflow) phase-3-build

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

FAQPage Schema
How do I automate gated quality checks for a multi-feature release workflow?

Automate gated quality checks for multi-feature releases by orchestrating an end-to-end phase-3 build workflow that enforces strict verification before merge. This structured approach coordinates feature discovery, QA, and PR-based validation across frontend, backend, and DevOps tasks to ensure predictable delivery.

What is the best way to manage feature discovery and specification before a PR merge?

Managing feature discovery and specification before a PR merge requires a centralized workflow that creates prioritized feature lists and user stories. This process systematically progresses through gated steps to ensure specifications are fully defined and traceable prior to code review.

How do I track ADR changes during a multi-step phase-3 build process?

Track ADR changes during a phase-3 build by utilizing a structured workflow that requires traceable outputs at each gated step. This ensures architecture decision records are systematically monitored and validated throughout feature development and prior to final merge.

Does this gated workflow approach work for both frontend and backend release coordination?

Yes, this gated workflow explicitly applies to multi-feature releases requiring coordination across frontend, backend, and DevOps tasks. It centralizes worktree management, QA, and reviews to align feature discovery and release gating across these distinct technical domains.