Delete /create-epics-stories and update all references

Removes the deprecated skill entirely and updates every reference across:
- README.md, UPGRADING.md (skill count + file lists)
- docs/WORKFLOW-GUIDE.md (pipeline diagrams, step descriptions, command reference)
- docs/examples/skill-flow-diagrams.md, session-*.md
- docs/architecture/tr-registry.yaml
- tests/skills/catalog.yaml
- .claude/skills: adopt, content-audit, create-control-manifest,
  skill-test, story-readiness
- .claude/docs: skills-reference.md, quick-start.md

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
Donchitos
2026-03-16 15:04:15 +11:00
parent 4ca6500a21
commit 9f731f3d86
16 changed files with 85 additions and 450 deletions

View File

@@ -61,7 +61,7 @@
>
> | Gap | Severity | Reason |
> |-----|----------|--------|
> | No systems index | BLOCKING | `/design-system`, `/create-epics-stories`, `/gate-check` all require it |
> | No systems index | BLOCKING | `/design-system`, `/create-stories`, `/gate-check` all require it |
> | GDD files not in template format | HIGH | Skills cannot reference TR-IDs from malformed GDDs |
> | No architecture docs | HIGH | Cannot run `/architecture-review` or `/create-control-manifest` |
> | No production tracking | MEDIUM | Sprint and story skills won't work, but not needed until production phase |

View File

@@ -1,6 +1,6 @@
# Example Session: Full Story Lifecycle — /story-readiness → Implement → /story-done
**Context:** Solo indie dev, mid-production sprint. The movement system GDD and architecture are complete. A story for movement's core implementation has been generated by `/create-epics-stories`.
**Context:** Solo indie dev, mid-production sprint. The movement system GDD and architecture are complete. A story for movement's core implementation has been generated by `/create-stories`.
**Starting State:**
- `design/gdd/movement-system.md` — complete, all 8 sections

View File

@@ -39,7 +39,8 @@ PHASE 3: TECHNICAL SETUP
PHASE 4: PRE-PRODUCTION
/ux-design [screen/hud/patterns] ────────────────────────────► design/ux/*.md
/ux-review ──────────────────────────────────────────────────► UX specs approved
/create-epics-stories ───────────────────────────────────────► production/stories/STORY-*.md
/create-epics [layer] ───────────────────────────────────────► production/epics/*/EPIC.md
/create-stories [epic-slug] ─────────────────────────────────► production/epics/*/story-*.md
/prototype [core-mechanic] ──────────────────────────────────► prototypes/[name]/
/playtest-report ────────────────────────────────────────────► tests/playtest/vertical-slice.md
/sprint-plan new ────────────────────────────────────────────► production/sprints/sprint-01.md
@@ -117,10 +118,15 @@ upstream GDDs (input, if any)
How a story gets from backlog to closed:
```
/create-epics-stories
/create-epics [layer: foundation]
└── Output: production/stories/STORY-[SYS]-NNN.md
(Status: backlog or blocked if ADR is Proposed)
└── Output: production/epics/[slug]/EPIC.md
/create-stories [epic-slug]
└── Output: production/epics/[slug]/story-NNN-[slug].md
(Status: Ready or Blocked if ADR is Proposed)
/story-readiness [story]