Epic Implementation Command

You are tasked with implementing a comprehensive GitHub Epic with multiple sub-issues. Follow this systematic approach to ensure high-quality, well-tested implementation.

promptBeginner5 min to valuemarkdown

0 views

Jan 14, 2026

Loading actions...

Additional Files (4)

Epic Implementation Command

You are tasked with implementing a comprehensive GitHub Epic with multiple sub-issues. Follow this systematic approach to ensure high-quality, well-tested implementation.

Parameters

Epic Issue Number: The GitHub issue number for the main Epic (e.g., #86)

Implementation Process

Phase 1: Analysis & Planning

Repository Analysis: Use @repo-analyzer to thoroughly understand:
- Current codebase architecture and patterns
- Existing test coverage and patterns
- Development workflows and conventions
- Key dependencies and their usage patterns
Epic Breakdown: Analyze the Epic and all sub-issues to create a granular TODO list where each item:
- Can be completed in 1-2 commits maximum
- Has clear acceptance criteria
- Includes specific test requirements
- Follows atomic change principles
Planning Considerations:
- Review current state vs Epic requirements
- Identify dependencies between tasks
- Plan commit strategy for incremental progress
- Consider impact on existing functionality

Phase 2: Implementation Standards

Code Quality Principles

Keep it Simple: Favor clarity over cleverness
Keep it Modular: Single responsibility, loose coupling
Keep it DRY: Eliminate repetition, create reusable utilities

TypeScript Standards

Type Safety: Avoid any and unknown - use proper typed interfaces
Fix Existing Issues: Replace any encountered any/unknown with proper types
Comprehensive Types: Define interfaces for all data structures

Documentation Requirements

Extensive Docblocks: Every function, class, and complex logic block
Context for Future Work: Explain "why" not just "what"
Examples: Include usage examples in docblocks where helpful

Testing Requirements

>90% Coverage: All new code must have comprehensive test coverage
Test Categories: Unit, integration, and E2E tests as appropriate
Test Quality: Tests should validate behavior, not just existence

Phase 3: Execution Workflow

For Each TODO Item:

Context Review: Re-analyze current codebase state and completed items
Implementation: Code the specific feature/fix following standards
Testing: Write comprehensive tests achieving >90% coverage
Validation: Ensure all tests pass and no regressions
Documentation: Update docblocks and relevant docs
Commit: Make atomic commit with descriptive message

Commit Standards:

Atomic Changes: Each commit represents one complete logical change
Test Passing: Never commit failing tests
Descriptive Messages: Follow conventional commit format
Incremental Progress: Regular commits showing steady progress

Progress Tracking:

GitHub Comments: Update Epic issue with progress after each commit
Checklist Updates: Mark completed items and note current status
PR Management: Create PR after first commit, push subsequent commits
Branch Strategy: Use feature branch named epic/issue-{number}

Phase 4: Quality Assurance

Before Each Commit:

Epic Completion Criteria:

All sub-issues implemented and tested
Integration tests passing
Documentation updated
PR ready for review
No regressions in existing functionality

Command Usage

/epic 86

This will:

Analyze the repository using repo-analyzer
Break down Epic #86 into granular tasks
Begin systematic implementation
Create PR and track progress
Iterate until Epic is complete

Success Metrics

All Epic acceptance criteria met
Comprehensive test coverage (>90%)
Clean, well-documented code
No regressions
Atomic commits with clear progression
Ready-to-merge PR

Remember: Quality over speed. Each commit should represent production-ready code that passes all tests and maintains system integrity.

View Original Source

Related Skills

General

PromptBeginner5 minmarkdown

<h1 align="center">

Jan 12, 2026

General

PromptBeginner5 minmarkdown

2. Apply Deepthink Protocol (reason about dependencies

risks

Jan 15, 2026

General

PromptBeginner5 minmarkdown

Frontend Typescript Linting.mdc

TypeScript and ESLint rules that MUST be followed when creating, modifying, or reviewing any file under apps/frontend/, including .ts, .tsx, .js, and .jsx files. Also apply when discussing frontend linting, type safety, or ESLint configuration.

Feb 15, 2026