Extract Shared Templates: Centralize checkpoint patterns and eliminate duplication

Author: JeffallanCreated Dec 17, 2025Updated Feb 1, 2026

Summary

Extract common patterns (checkpoints, output formats, tables) into shared templates to improve maintainability and consistency across workflow commands.

Problem

Current state has significant duplication:

  • Checkpoint pattern repeated 19+ times with slight variations
  • Output format inconsistent across commands
  • Table structures duplicated
  • Configuration values (90% coverage) hardcoded in multiple places
  • ~2,128 lines total, estimated 30-40% duplication

Examples of inconsistency:

markdown
# Different checkpoint phrasings:
"Is this correct? (Yes / No / Correct)"
"Proceed with these documents? (Yes / No / Correct)"
"Are all tickets complete...? (Yes / No / Review)"

Proposed Solution

Directory Structure

/.claude/
  /commands/
    create-epic-plan.md
    ...
  /templates/           [NEW]
    checkpoint.md       # Standard confirmation pattern
    output-format.md    # Success message templates
    table-templates.md  # Reusable table structures
    failure-condition.md # Error reporting pattern
  /config/              [NEW]
    workflow-config.yaml
  /reference/           [NEW]
    glossary.md
    quick-reference.md

Shared Checkpoint Template

markdown
## MANDATORY CHECKPOINT - {Checkpoint_Name}

{Checkpoint_Content}

Proceed with this action? (Yes / No / Modify)

- **Yes** → Continue to {Next_Phase}
- **No** → {Alternative_Action}
- **Modify** → {Modification_Process}

**DO NOT PROCEED** without explicit user confirmation.

Configuration File

yaml
# workflow-config.yaml
coverage_targets:
  branch_coverage: 90
  overall_coverage: 85

confluence:
  default_epic_path: "/Epics/In Progress/"
  complete_path: "/Epics/Complete/"
  retrospective_path: "/Retrospectives/"

story_points:
  simple: "1-2"
  moderate: "3-5"
  complex: "8"
  max_before_split: 8

risk_thresholds:
  low: "7-11"
  medium: "12-16"
  high: "17-21"

Benefits

  • Single source of truth for patterns
  • Easier to update behavior globally
  • Consistent user experience
  • Reduced maintenance burden
  • Enables per-organization customization

Acceptance Criteria

  • Templates directory created with core patterns
  • Config file with all magic numbers/strings
  • Commands refactored to reference templates
  • Checkpoint options standardized to (Yes / No / Modify)
  • Documentation for template usage