foxctl-epic-pipeline

Convert Factory missions or markdown plans into canonical room-agile epics with readiness grades.

3|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/joshka0/foxctl --skill foxctl-epic-pipeline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: foxctl-epic-pipeline
Source: https://github.com/joshka0/foxctl/tree/main/configs/skills-pack/foxctl-epic-pipeline
Command: npx skills add https://github.com/joshka0/foxctl --skill foxctl-epic-pipeline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill converts a mission or plan intake into a canonical room-agile epic with an actionable readiness grade and a prioritized execution frontier, so teams stop guessing what to implement next.

Core Features & Use Cases

  • Epic creation & planning: Imports Factory missions or plan markdown into a standardized room-agile epic model for later dispatch.
  • Readiness grading: Produces a grade that reflects whether the epic is implementation-worthy, distinguishing real implementation blockers from missing planning metadata.
  • Frontier computation & guarded dispatch: Computes which stories can run now and which are blocked, then supports dispatch only from a ready frontier.
  • Evidence-guided repair: Uses status, scout, and grade findings to guide structured repairs (outcomes, milestone contracts, criteria coverage, owners, evidence expectations, and dependency topology) without inflating implementation progress.

Quick Start

Use this skill to import a plan file into a room, then run the standard pipeline stages to obtain a grade and a dispatchable frontier for implementation.

Frequently Asked Questions about foxctl-epic-pipeline

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

FAQPage Schema
How do I convert a markdown plan into an implementation-ready epic?

To turn a markdown plan into an implementation-ready epic, this skill imports the intake file and converts it into a canonical room-agile epic model. It then applies staged execution to compute a readiness grade and an actionable execution frontier.

What is execution frontier computation in agile epic planning?

Execution frontier computation identifies which stories within a room-agile epic can be dispatched immediately and which are blocked. It supports guarded dispatch by ensuring implementation only begins from a validated, ready frontier of stories.

How do I run the epic readiness grading pipeline?

You run the readiness grading pipeline by executing six staged steps in strict order: status, snapshot, scout, grade, frontier, and dispatch-frontier. This sequence preserves intake metadata and separates planning evidence from implementation evidence for correct grading.

Can I use Factory missions as intake for room-agile epic creation?

Yes, you can use Factory missions as direct intake for room-agile epic creation. The skill processes these missions alongside OpenCode plans to produce a standardized epic model with actionable readiness grades and prioritized execution frontiers.

Why does my epic readiness grade show blocked stories despite complete planning metadata?

An epic readiness grade may show blocked stories due to strict separation of planning versus implementation evidence. The grade distinguishes actual implementation blockers from missing planning metadata, ensuring only truly ready stories enter the execution frontier.

How do I repair an epic plan with missing outcome contracts and criteria coverage?

To repair an epic plan with missing outcome contracts, use evidence-guided repair driven by status, scout, and grade findings. This structured process fixes milestone contracts, criteria coverage, and dependency topology without inflating actual implementation progress.