Convert approved GDDs and architecture documents into epics with ADR coverage checks.
npx skills add https://github.com/CarlosQ96/robot-crawler --skill create-epics
Please help me install this Agent Skill. Skill: create-epics Source: https://github.com/CarlosQ96/robot-crawler/tree/main/.agents/skills/create-epics Command: npx skills add https://github.com/CarlosQ96/robot-crawler --skill create-epics
Converts approved game design documents and architecture decisions into formal epics so product and engineering teams have clear, architect-owned scope without manual consolidation. It surfaces gaps in ADR coverage, assesses engine risk, and prevents premature story creation so work is scoped and traceable before implementation.
Run /create-epics layer: core --review lean to generate epics for all core systems after architecture and TR checks.
High-intent search queries and answers about installing and using this skill.
To turn GDDs and architecture documents into epics, you need to map each game system to an architecture module and define scope, ownership, and governing ADRs. This process produces one formal epic per module to ensure clear, architect-owned scope.
Requirements tracing and ADR coverage validation involve cross-checking approved architecture decisions against the TR registry to identify untraced requirements. This ensures all technical requirements are governed before scoping work and prevents premature story creation.
Generating epics from approved game design documents requires reading the GDDs and applying architecture rules to produce formal epics. This automated approach surfaces engine compatibility risks and prevents manual consolidation errors during pre-production.
Yes, you can use review gates to control epic file generation by selecting solo, lean, or full review modes. The system prompts for per-epic approval and only writes the EPIC.md and epics index files after you explicitly confirm.
You need approved ADRs and engine risk assessments before scoping epics to guarantee work is traceable and technically viable. Assessing engine compatibility risk early highlights missing architecture decisions that must be completed first.
Epic generation works directly for technical directors and engineering leads handling pre-production planning. It transforms approved design and architecture files into a consistent set of epics tailored for the next milestone.
polseguDecompose game development epics into story files with QA test cases.
Negentropy-LabyTranslate approved CDDs and architecture into epics mapped to architectural modules.
terrylicaAdd ADR references to code with language-specific comment patterns.
SeongHuniCreate game development epics from GDDs and architecture documents.
