factory-plan

Translate ADRs and version deltas into epics, user stories, and tasks.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/selossebdc-cell/portail-client-v2 --skill factory-plan-selossebdc-cell
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: factory-plan
Source: https://github.com/selossebdc-cell/portail-client-v2/tree/main/.claude/skills/factory-plan
Command: npx skills add https://github.com/selossebdc-cell/portail-client-v2 --skill factory-plan-selossebdc-cell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This planning orchestration automates the creation of structured planning artifacts (epics, user stories, and tasks) from ADRs and version deltas, reducing manual coordination and ensuring consistency across planning documents.

Core Features & Use Cases

  • Automates planning workflow: fetches the current planning version, runs gate checks, and delegates to a Scrum Master for decomposition.
  • Generates planning artifacts: epics, US, and tasks templates, ensuring independence and BMAD DoD compliance.
  • Use Case: In a release cycle, convert active ADRs into a complete planning backlog with ready-to-implement tasks.

Quick Start

Decompose the current planning specs into epics, US, and tasks using the Scrum Master workflow.

Frequently Asked Questions about factory-plan

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

FAQPage Schema
How do I automate decomposing planning specs into epics, user stories, and tasks?

You can automate planning decomposition by processing ADRs and version deltas to generate structured epics, user stories, and tasks. This workflow runs gate checks and delegates decomposition to ensure artifacts include complete context and Definition of Done.

What is the best way to convert active ADRs into a ready-to-implement agile backlog?

Converting active ADRs into an agile backlog requires fetching the current planning version, excluding superseded ADRs, and extracting deltas to generate template-driven planning artifacts. This produces standalone tasks ready for build and test validation.

Can I generate user stories and tasks directly from version deltas for a release cycle?

Yes, you can generate user stories and tasks directly from version deltas. The process extracts delta changes, runs gate checks to validate inputs, and applies templates to output independent epics and tasks that conform to planning standards.

Does agile planning automation work with BMAD DoD compliance requirements?

Agile planning automation supports BMAD DoD compliance by generating tasks that strictly follow planning templates. It ensures every standalone task includes complete context and meets the defined DoD criteria before build and test validation.

Why does my planning workflow need gate checks before decomposing epics and user stories?

Gate checks are needed before decomposing epics and user stories to validate the current planning version and filter out superseded ADRs. This ensures the decomposition process only operates on active, approved inputs to generate accurate artifacts.

When should I exclude superseded ADRs during automated epic and task generation?

You should exclude superseded ADRs during automated epic and task generation whenever a new planning version invalidates previous decisions. Removing them prevents conflicting inputs and ensures the generated backlog reflects only current specifications.