adhoc-plan

Convert recommended work items into a structured Gait backlog plan.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the conversion of raw work item recommendations into a structured, execution-ready backlog plan, ensuring all development tasks are clearly defined with necessary tests and CI integration.

Core Features & Use Cases

  • Automated Backlog Generation: Transforms user-provided recommendations into epics, stories, tasks, and acceptance criteria.
  • Integrated Test Planning: Ensures every story includes defined test requirements and matrix wiring.
  • Use Case: After a product brainstorming session, feed the raw ideas into this Skill to generate a prioritized backlog with actionable tasks, ready for the engineering team to start development.

Quick Start

Use the adhoc-plan skill to convert the provided recommended items into a backlog plan saved to '/Users/davidahmann/Projects/gait/backlog.md'.

Frequently Asked Questions about adhoc-plan

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

FAQPage Schema
How do I convert raw product ideas into a structured backlog plan?

Converting raw product ideas into a structured backlog plan involves clustering recommendations into epics, prioritizing stories with P0/P1/P2 levels, and defining tasks with repo paths, test requirements, and CI matrix wiring. This ensures your engineering team receives execution-ready work items.

What is the best way to automate agile backlog generation from brainstorming sessions?

Automated backlog generation transforms brainstorming outputs into epics, stories, and acceptance criteria with integrated test planning. It ensures every story includes defined test requirements and CI matrix wiring, yielding a prioritized backlog ready for development.

How do I generate CI matrix wiring and test requirements for agile stories?

Generating CI matrix wiring and test requirements for agile stories is handled by defining specific test criteria for each story during backlog creation. The process enforces determinism and fail-closed policy checks to respect architecture boundaries and schema stability.

Does this backlog planning approach work offline and enforce fail-closed policies?

Yes, this backlog planning approach uses offline-first defaults and enforces fail-closed policies. It guarantees determinism by respecting architecture boundaries and schema stability while structuring your recommended work items into an actionable plan.

Can I prioritize backlog stories using P0 P1 P2 levels automatically?

You can prioritize backlog stories automatically using P0, P1, and P2 levels. The task clustering mechanism groups recommendations into epics and assigns these priority tiers to stories, ensuring the most critical development tasks are addressed first.

When do I need automated task management to define repo paths and run commands?

You need automated task management to define repo paths and run commands when transitioning from high-level recommendations to an execution-ready development plan. It maps out specific repository locations and execution commands for every generated task.