Skip to content

Technical Debt Roadmap Execution #237

@ArthurCRodrigues

Description

@ArthurCRodrigues

Purpose

Coordinate the remediation work described in docs/roadmaps/TECHNICAL_DEBT_ROADMAP.md. The focus is to stabilize the existing pipeline architecture (Load Template → Export) before expanding features. Each sub-issue below maps 1:1 with the roadmap so work can be parallelized and tracked transparently.

Scope

  • Use this tracker to stage work, discuss sequencing, and surface blockers across steps/services/templates/web layers.
  • Sub-issues already contain detailed scope, impacted files, risks, and acceptance criteria drawn from the roadmap.
  • Update the checklist as work lands; feel free to add blockers/notes inline.

Sub-Issue Checklist

How to Work This Board

  1. Claim an open sub-issue, add context/assignee, and link PRs back to both the sub-issue and this tracker.
  2. Keep docs/tests in sync with the scope outlined in each issue.
  3. Use this parent issue for overall status updates, sequencing discussions, and cross-cutting risks (e.g., order dependencies between Items 17–21).

Metadata

Metadata

Assignees

No one assigned

    Labels

    Issue Level: WideThe actions related to a wide issue are several and could even require a service or repository.enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions