implement

Automate phased feature implementation with user-story validation and quality gates.

2|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/stratus/my-claude --skill implement-stratus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implement
Source: https://github.com/stratus/my-claude/tree/main/skills/implement
Command: npx skills add https://github.com/stratus/my-claude --skill implement-stratus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end feature implementation with user-story validation and phased execution to reduce rework and speed delivery.

Core Features & Use Cases

  • Pre-flight checks to verify user story and criteria are defined.
  • Phase execution that iterates through development phases with code, tests, and linting.
  • Quality gates that ensure tests pass, coverage thresholds met, and lint rules satisfied after each phase.

Quick Start

Validate the user story and initiate the first development phase with tests and quality checks.

Frequently Asked Questions about implement

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

FAQPage Schema
How do I automate feature implementation with quality gates and tests?

Feature implementation is automated through phased execution that validates user stories, runs tests, and enforces lint rules. Quality gates ensure coverage thresholds are met and tests pass after each development phase to reduce rework.

What is phased execution for software feature development?

Phased execution iterates through structured development stages, applying code, tests, and linting at each step. It requires pre-flight checks to verify user stories and acceptance criteria before development begins.

How do I enforce test coverage thresholds during a feature launch?

Test coverage thresholds are enforced by quality gates evaluated after each execution phase. These gates verify that tests pass, coverage minimums are met, and lint rules are satisfied before proceeding to the next stage.

Do I need defined user stories and acceptance criteria before starting feature work?

Defined user stories and acceptance criteria are required before starting. Pre-flight checks validate that these inputs exist, ensuring the automated workflow has structured requirements to validate against during phased execution.

What's the best way to structure a workflow for ongoing feature plan phases?

The best way to structure feature plan phases is using an automated workflow with checkpoint summaries. This approach iterates through development phases while imposing structured requirements like tests, linting, and coverage thresholds at each checkpoint.

Why does feature development fail quality gates between phases?

Quality gates fail when tests do not pass, coverage thresholds are unmet, or lint rules are violated after a development phase. The structured workflow enforces these checks to prevent moving forward with incomplete or incorrect code.