Agent skill
factory-plan
Phase ACT (planning) - Génère epics/US/tasks
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/factory-plan
SKILL.md
Factory Plan - Phase ACT (Planning)
Tu es l'orchestrateur de la phase planning.
Workflow
-
Instrumentation (si activée) - Enregistrer le début de phase :
bashnode tools/instrumentation/collector.js phase-start '{"phase":"ACT","skill":"factory-plan"}' node tools/instrumentation/collector.js skill '{"skill":"factory-plan"}' -
Vérifier Gate 2 :
node tools/gate-check.js 2 -
Déléguer à l'agent
scrum-mastervia Task tool :bash# Instrumentation (si activée) node tools/instrumentation/collector.js agent '{"agent":"scrum-master","source":"factory-plan"}'Task( subagent_type: "scrum-master", prompt: "Décompose docs/specs/* et docs/adr/* en epics/US/tasks. IMPORTANT - Tasks auto-suffisantes (principe BMAD): Chaque TASK doit être 100% indépendante avec: - Template: templates/planning/task-template.md - Contexte complet: références specs avec résumés - Code existant pertinent: extraits avec lignes - Aucune dépendance à la task précédente Le développeur doit pouvoir implémenter la task SANS connaître les autres tasks.", description: "Scrum Master - Planning BMAD" ) -
Vérifier les outputs :
docs/planning/epics.mdexiste- Au moins 1 fichier
docs/planning/us/US-*.md - Au moins 1 fichier
docs/planning/tasks/TASK-*.md - Chaque TASK contient TOUTES ces sections (auto-suffisance BMAD):
- Objectif technique
- Contexte complet (specs référencées avec résumés)
- Fichiers concernés (liste exhaustive)
- Definition of Done
- Tests attendus
- Critères de validation automatique
-
Exécuter Gate 3 :
node tools/gate-check.js 3 -
Logger via :
bashnode tools/factory-log.js "ACT-PLAN" "completed" "Phase planning terminée" -
Retourner un résumé avec liste des tasks créées (numérotées)
En cas d'échec
Si Gate 3 échoue → STOP et rapport des éléments manquants.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?