adhoc-implement

Execute a Gait backlog plan story-by-story with Git branching, tests, and CodeQL validation.

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

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 user-defined backlog plans within a Git repository, ensuring strict adherence to predefined workflows, testing, and validation criteria.

Core Features & Use Cases

  • Plan Execution: Executes a specified plan file story-by-story, managing dependencies and priorities.
  • Strict Git Workflow: Enforces a mandatory Git branching strategy and checks for worktree cleanliness.
  • Comprehensive Validation: Integrates linting, unit tests, integration tests, CodeQL scans, and final revalidation against acceptance criteria and Definition of Done.
  • Use Case: A product manager provides a plan.md file detailing new features. This Skill takes that plan and executes each story, ensuring all code, tests, and documentation changes meet the defined quality gates before completion.

Quick Start

Use the adhoc-implement skill to execute the plan located at '/path/to/your/plan.md'.

Frequently Asked Questions about adhoc-implement

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

FAQPage Schema
How do I automate backlog plan execution story-by-story with strict Git workflow enforcement?

Backlog plan execution is automated story-by-story by enforcing a strict Git branching strategy and checking worktree cleanliness before proceeding with code implementation. Dependencies and priorities are managed automatically throughout the process.

Can I wire CodeQL validation and a test matrix into my CI/CD pipeline during feature implementation?

CodeQL validation and a test matrix are wired into CI/CD pipelines during feature implementation by integrating linting, unit tests, integration tests, and security scans as required quality gates before story completion.

How does Definition of Done revalidation work when implementing a plan file?

Definition of Done revalidation works by performing a final acceptance criteria check against the implemented plan file after all stories are complete, ensuring verifiable evidence confirms the feature meets predefined quality gates.

What format does the plan file need to be in for automated story-by-story implementation?

The plan file needs to be a markdown document, such as a plan.md file, detailing new features and stories for automated implementation. The Skill reads this user-specified file to execute the backlog end-to-end.

Do I need a clean Git worktree before starting automated feature plan execution?

A clean Git worktree is required before starting automated feature plan execution because the workflow strictly enforces a mandatory branching strategy and checks for worktree cleanliness to ensure deterministic implementation.

What is the best way to ensure deterministic implementation of a backlog plan with automated testing?

Deterministic implementation of a backlog plan with automated testing is best achieved by enforcing staged development with strict branch bootstrapping, comprehensive test-matrix wiring, and CodeQL validation gates for verifiable evidence.