adhoc-plan

Convert user-provided recommendations into an executable backlog plan with epics, stories, and CI matrix wiring.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert user-provided recommendations into a structured backlog plan at a user-defined output path, enabling repeatable, auditable planning.

Core Features & Use Cases

  • Generate execution-ready epics and stories from input recommendations.
  • Enforce validation rules and produce deterministic plans.
  • Provide traceability mappings and test matrix wiring for CI.

Quick Start

Provide a backlog plan by supplying recommended_items and output_plan_path to gait doctor.

Frequently Asked Questions about adhoc-plan

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

FAQPage Schema
How do I convert product recommendations into an executable backlog plan?

To convert recommendations into a backlog plan, supply recommended items and an output path to generate execution-ready epics, stories, and test requirements with deterministic validation.

What is the best way to generate epics and stories from a list of suggested items?

Generating epics and stories from suggested items requires input validation and an output path, producing a structured backlog plan with actionable tasks and CI matrix wiring for traceability.

How does backlog plan validation work for deterministic output?

Backlog plan validation enforces deterministic rules on input recommendations, ensuring the generated epics, stories, and test matrices are auditable and execution-ready at the target output path.

Can I include CI matrix wiring and test requirements in my backlog stories?

Yes, CI matrix wiring and test requirements are integrated directly into the generated backlog stories, providing traceability mappings and run commands alongside the executable epics.

Does this approach overwrite existing files when saving the backlog plan?

Yes, the workflow overwrites the target output path with the final backlog plan, replacing existing content to ensure the destination holds only the latest validated epics and stories.

When do I need a structured backlog plan with traceability mappings?

A structured backlog plan with traceability mappings is needed when converting ad hoc product recommendations into repeatable, auditable engineering tasks with CI test matrix integration.