foxctl-factory-epic-creation

Normalizes imported Factory missions into foxctl canonical room-agile epic artifacts with READY/NOT READY checks.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It transforms an imported Factory mission into a canonical foxctl room-agile epic that is structurally ready to serve as an implementation plan, while preventing premature implementation.

Core Features & Use Cases

  • Factory-to-epic import normalization: Imports a Factory mission and normalizes it into foxctl’s canonical room-agile epic artifact, suitable for plan review.
  • Creation readiness gating (READY / NOT READY): Cross-checks the normalized epic against the epic-creation Definition of Done and reports only planning gaps when not ready.
  • Structure-first evidence-aware planning: Improves milestones, story decomposition, validator lanes, evidence expectations, and provenance mapping without starting implementation work.

Quick Start

Import a Factory mission into foxctl for creation-only normalization and grading by running: foxctl room epic import-factory <room-id> --mission-dir ~/.factory/missions/<mission-dir> --sender <coordinator>.

Frequently Asked Questions about foxctl-factory-epic-creation

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

FAQPage Schema
How do I normalize a Factory mission into an implementation-ready epic plan?

To normalize a Factory mission into an implementation-ready epic plan, import it using the foxctl room epic import-factory command to restructure milestones and story decomposition into a canonical room-agile artifact.

What is evidence-aware planning in epic creation?

Evidence-aware planning in epic creation structures milestones and story decomposition with explicit evidence expectations and provenance mapping, ensuring all structural validation requirements are documented before implementation begins.

How does the READY NOT READY validation lane work for epic planning?

The READY NOT READY validation lane cross-checks your normalized epic against the epic-creation Definition of Done, reporting specific planning gaps in milestones and validators when the epic is graded NOT READY.

Can I start implementation while normalizing an imported Factory mission?

No, normalizing an imported Factory mission is a creation-only process that gates implementation by design, focusing strictly on structure-first validation and readiness grading to prevent premature development.

What do I need to run the Factory mission import for epic creation?

You need a valid room-id, a local mission directory path, and a designated coordinator sender to execute the deterministic import and generate the canonical room-agile epic artifact for review.

Why does my Factory to room-agile epic import return NOT READY?

Your epic import returns NOT READY when the normalized artifact fails the Definition of Done cross-check, indicating missing planning elements like story decomposition, validator lanes, or evidence expectations that require restructuring.