feat(023): Add epic workflow support for large feature breakdown #83
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add item 023 for epic support in speckit workflow. - Epics section in BACKLOG.md - New /epic command using Opus for breakdown - Ex nomenclature for item traceability Links to #79. Approved for implementation.
Defines: - Epics section in BACKLOG.md - /epic skill for breaking down large features - [Ex] nomenclature for item traceability - Breakdown guidelines and example output
Phase 0 (Research): - Skill/command file patterns from existing /idea command - BACKLOG.md table parsing approach - Opus prompting strategy for BA/Architect analysis - GitHub CLI best practices Phase 1 (Design): - data-model.md: Epic and Item schemas, Epics table structure - quickstart.md: Usage guide for /epic command - plan.md: Implementation plan with constitution check Phase 2 (Media): - planning-post.md: Blog announcement draft - linkedin-planning.md: Social summary
15 tasks across 5 phases: - Infrastructure: BACKLOG.md Epics section - Core: /epic skill implementation (8 tasks) - Validation: manual testing (3 parallel) - Documentation: quickstart and blog updates - Integration: PR creation
- Add Epics table to BACKLOG.md (between Workflow and Items) - Create /epic skill with full workflow: - Input parsing (text, local path, GitHub URL) - Opus-driven BA + Architect analysis - Sequential epic ID assignment (E01, E02...) - BACKLOG.md updates (epic row + item rows) - GitHub issue creation with fallback to local files - Summary report with next steps - Mark Phase 1-2 tasks complete in tasks.md
Evidence: - implementation-review.md: acceptance criteria verification - usage-example.md: example command outputs Media: - shipped-post.md: blog announcement - linkedin-shipped.md: social summary All Phase 1-4 tasks complete.
3 tasks
IanMayo
pushed a commit
that referenced
this pull request
Feb 11, 2026
Vega-Lite based results viewing infrastructure: renderer component, tabbed bottom panel, logical result ID registry, custom editor for drag-to-float, and auto-refresh. Absorbs E03 #83 into E04 #89. Updates E03 cross-epic dependencies (only #82 and #84 need E04). https://claude.ai/code/session_015jzC8noATYLoama7VdveuR
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
/epiccommand to break down large features into 3-10 deliverable backlog items[Ex]nomenclature for item-to-epic traceabilityChanges
Phase 1: Infrastructure
Phase 2: Core Skill Implementation
/epicskill at.claude/commands/epic.md.mdpath, GitHub URL[Ex]prefix)Phase 3: Validation
Phase 4: Documentation & Media
Evidence
Implementation Review
All acceptance criteria verified:
/epicskill exists[Ex]prefix on itemsUsage Example
Test Plan
/ideacommand patternRelated
specs/023-epic-workflow-support/spec.mdspecs/023-epic-workflow-support/tasks.md