plan-implement

Execute backlog plan stories with Git bootstrap, CodeQL validation, and DoD revalidation.

12|5|Updated Feb 5, 2026

Search Tags:#workflow #testing #implementation #backlog #plan #codeql

Ready to run

npx skills add https://github.com/Clyra-AI/gait --skill plan-implement-clyra-ai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-implement
Source: https://github.com/Clyra-AI/gait/tree/main/.agents/skills/plan-implement
Command: npx skills add https://github.com/Clyra-AI/gait --skill plan-implement-clyra-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Implement backlog plan execution end-to-end with strict bootstrap, per-story test wiring, CodeQL validation, and final DoD/acceptance revalidation, ensuring deterministic, auditable delivery.

Core Features & Use Cases

Plan-driven execution: orchestrates plan files (e.g., PLAN_NEXT.md) into a reproducible, auditable run.
Quality gates: enforces Git bootstrap steps, CodeQL validation, and acceptance criteria validation before completion.
Use Case: When planning multi-story sprints, this skill ensures each story is validated, tested, and revalidated against the DoD.

Quick Start

Provide PLAN_NEXT.md and run the end-to-end plan-implement workflow to execute backlog stories and validate the DoD.

Frequently Asked Questions about plan-implement

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

FAQPage Schema

How do I automate backlog plan execution with DoD validation for multi-story sprints?▼

Automating backlog plan execution requires orchestrating plan files like PLAN_NEXT.md into a reproducible run that validates each story against acceptance criteria and the DoD. This skill enforces Git bootstrap, per-story test wiring, and CodeQL prepush checks to ensure deterministic, auditable delivery across sprints.

What is the best way to validate acceptance criteria and run CodeQL checks across multiple product plan stories?▼

Validating acceptance criteria across plan stories is best handled by an end-to-end workflow that parses plan files, wires per-story tests, and runs CodeQL prepush checks. This approach enforces quality gates and performs a final DoD revalidation before marking any epic or story complete.

How do I set up a reproducible workflow for Git bootstrap and per-story test wiring?▼

Setting up reproducible Git bootstrap and per-story test wiring involves providing a structured plan file such as PLAN_NEXT.md. The workflow parses the plan, orchestrates dependencies across stories, and applies strict bootstrap steps to ensure every execution is auditable and deterministic.

Does plan-implement work with existing Gait workflow plans and CodeQL validation?▼

Yes, this skill operates within the Gait workflow to orchestrate plan stories, dependencies, and CodeQL validation. It parses your existing product plans, applies Git bootstrap, and enforces CodeQL prepush checks to satisfy functional requirements and final DoD revalidation.

What are the limitations of automating plan execution without final DoD revalidation?▼

Automating plan execution without final DoD revalidation risks delivering incomplete stories that pass initial tests but fail acceptance criteria. Without strict quality gates like CodeQL prepush checks and Git bootstrap, the delivery lacks the deterministic and auditable guarantees required for multi-story sprints.