plan-implement

Implements Gait backlog plans with Git branching, per-story tests, CodeQL validation, and DoD revalidation.

12|5|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/davidahmann/gait --skill plan-implement-davidahmann
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-implement
Source: https://github.com/davidahmann/gait/tree/main/.agents/skills/plan-implement
Command: npx skills add https://github.com/davidahmann/gait --skill plan-implement-davidahmann

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the end-to-end implementation of a Gait backlog plan, ensuring strict adherence to Git branching, per-story testing, code validation, and final acceptance criteria.

Core Features & Use Cases

  • Plan Execution: Implements stories from a specified plan file (PLAN_NEXT.md by default).
  • Strict Git Workflow: Enforces a mandatory Git bootstrap contract for safe and traceable development.
  • Comprehensive Validation: Includes linting, fast testing, story-specific tests, epic-level integration, and final CodeQL validation.
  • Definition of Done Enforcement: Verifies implementation against acceptance criteria, DoD, and exit criteria with command evidence.
  • Use Case: Automate the entire development cycle for a new feature, from parsing the product plan to final validation and reporting, ensuring all quality gates are met.

Quick Start

Use the plan-implement skill to execute the default plan file located at product/PLAN_NEXT.md.

Frequently Asked Questions about plan-implement

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

FAQPage Schema
How do I execute backlog stories end-to-end with strict Git branching?

Backlog execution with strict Git branching uses the plan-implement skill to enforce a mandatory Git bootstrap contract, ensuring safe and traceable development across all story implementations.

What is the best way to validate code against a Definition of Done after plan implementation?

Definition of Done validation is enforced by verifying the implementation against acceptance criteria, DoD, and exit criteria with command evidence after running CodeQL validation and epic-level integration.

How do I wire per-story tests during backlog execution?

Per-story test wiring is handled automatically during plan implementation, running story-specific tests alongside linting and fast testing to ensure comprehensive validation before final CodeQL checks.

Can I use this approach to automate issue and PR creation during plan implementation?

Automating issue and PR creation is not supported; this plan implementation approach manages story execution, validation, and reporting without handling issue or PR creation.

Do I need a specific plan file format to start plan implementation?

A plan file is required to start plan implementation, defaulting to product/PLAN_NEXT.md, which contains the Gait backlog stories to be executed end-to-end.

Why does CodeQL validation fail during my backlog execution?

CodeQL validation during backlog execution fails when the implementation does not pass the final quality gate, which runs after linting, fast testing, story-specific tests, and epic-level integration.