foxctl-room-agile

Name: foxctl-room-agile
Availability: InStock
Author: joshka0

Coordinate durable agile workflows with epic, milestone, and story lifecycle commands in foxctl rooms.

3|Updated Apr 14, 2026

Search Tags:#story validation #agile workflow #durable state #milestone review #epic milestone stories #room orchestration #work-pack sync

Ready to run

npx skills add https://github.com/joshka0/foxctl --skill foxctl-room-agile

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: foxctl-room-agile
Source: https://github.com/joshka0/foxctl/tree/main/configs/skills-pack/foxctl-room-agile
Command: npx skills add https://github.com/joshka0/foxctl --skill foxctl-room-agile

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps teams manage long-running agile work with durable scoping, structured milestones/stories, and cross-session execution evidence instead of relying on ephemeral chat.

Core Features & Use Cases

Durable Epic → Milestone → Story Lifecycle: Intake, shape, resume, and checkpoint an epic, then promote proposals into milestones and stories for explicit execution scope.
Evidence-Driven Reviews, Summaries, and Validations: Record milestone review verdicts, write synthesis as durable milestone summaries, and attach proof via story validation and work-pack mirroring.
Room-Scale Mission Control & Sync Artifacts: Maintain a delivery log, keep ~/.foxctl/epics/<epic-id>/... mirrors in sync, and promote high-signal artifacts into ContextWiki drafts for later semantic retrieval.

Quick Start

Start an epic in an existing room so the durable agile hierarchy can drive future milestone proposals and execution planning.

Frequently Asked Questions about foxctl-room-agile

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

FAQPage Schema

How do I manage long-running agile workflows across multiple chat sessions?▼

To manage long-running agile workflows across multiple sessions, you need durable state orchestration that structures epic intake, milestone proposals, and story validations. This approach replaces ephemeral chat by maintaining cross-session state via persistent epic artifacts.

What is the best way to track milestone review verdicts and story validation evidence?▼

The best way to track milestone review verdicts and story validation evidence is through evidence-driven reviews. You record verdicts, write synthesis as durable milestone summaries, and attach proof via work-pack mirroring for later semantic retrieval.

How do I structure epic intake and promote proposals into milestones and stories?▼

To structure epic intake and promote proposals, you orchestrate a durable epic to milestone to story lifecycle. You intake, shape, and checkpoint an epic, then promote proposals into milestones and stories to define explicit execution scope.

Do I need a base room protocol to run durable agile workflows?▼

Yes, running durable agile workflows requires a base room protocol. You must use room-level commands for lifecycle orchestration within an existing room, enforcing room protocol assumptions to properly maintain cross-session state.

How does work-pack sync handle cross-session state for agile epics?▼

Work-pack sync handles cross-session state by mirroring persistent epic artifacts. It maintains a delivery log and keeps local file mirrors in sync, ensuring high-signal artifacts are promoted into ContextWiki drafts for semantic retrieval.

When should I not use ephemeral chat for agile project management?▼

You should not use ephemeral chat for agile project management when handling long-running objectives that span many sessions. If your work requires explicit acceptance criteria, proof evidence, and work-pack mirroring, you need durable state orchestration.