implement-phase

Execute phase plans SI by SI with tests and user confirmation.

16|145|Updated Mar 16, 2026

Search Tags:#automation #workflow #planning #phase-execution #dependency-management #tests

Ready to run

npx skills add https://github.com/devfullcycle/mba-ia-greenfield-project --skill implement-phase-devfullcycle

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implement-phase
Source: https://github.com/devfullcycle/mba-ia-greenfield-project/tree/main/.claude/skills/implement-phase
Command: npx skills add https://github.com/devfullcycle/mba-ia-greenfield-project --skill implement-phase-devfullcycle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Execute a phase implementation plan SI by SI, ensuring each SI's implementation exists and its tests pass before advancing.

Core Features & Use Cases

Plan-driven execution of phase SIs with dependency-aware sequencing.
Per-SI testing, fix-loop handling, and explicit stop/continue prompts.
Progress tracking via a phase progress artifact and auditable completion.

Quick Start

Ask me to implement a phase, and I will execute it SI by SI, running tests after each SI and only moving forward when all tests pass.

Frequently Asked Questions about implement-phase

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

FAQPage Schema

How do I execute a phase plan SI by SI with dependency management?▼

Phase execution stops advancing when tests fail after an SI implementation. The workflow runs a fix loop for up to three iterations to resolve test failures, enforcing a hard stop if issues persist until the user intervenes.

Can I use test-driven progress tracking for multi-SI projects across subprojects?▼

Yes, test-driven progress applies to multi-SI projects across subprojects by validating each SI with tests before advancing. Progress is tracked via a phase progress artifact, ensuring auditable completion and dependency-aware sequencing throughout the workflow.

What is the required workflow to implement phase plans with iterative testing?▼

The required workflow to implement phase plans involves planning the SI, implementing actions, writing tests, running tests, and fixing up to three iterations. It enforces a hard stop between SIs, pausing for user confirmation before proceeding to the next SI.

When do I need a hard stop between SIs during phase execution?▼

A hard stop between SIs is needed during phase execution to enforce controlled progression and verify tests pass. It prevents moving to the next SI until the current implementation is validated and the user explicitly confirms continuation.