moex/moex-vibe
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
moex-vibe/docs/features/architecture-quality-backlog/plan.md

3.5 KiB
Raw Permalink Blame History

Architecture Quality Backlog Implementation Plan

For agentic workers: REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (- [ ]) syntax for tracking.

Goal: publish a canonical architecture backlog in docs/ and reconcile roadmap/audit statuses without changing runtime code.

Architecture: this feature is a documentation workflow. We inventory the already completed architecture work, collapse stale and duplicated backlog entries, and publish one normalized backlog that future features can implement independently.

Tech Stack: Markdown docs in docs/, Docusaurus-published architecture pages in apps/docs/docs/, repository search and patch tooling.

Task 1: Promote canonical feature docs

Files:

  • Create: docs/features/architecture-quality-backlog/spec.md

  • Create: docs/features/architecture-quality-backlog/plan.md

  • Create: docs/features/architecture-quality-backlog/tasks.md

  • Step 1: Move the worktree draft into canonical docs

Create the feature directory in the main workspace and copy the prepared spec/plan/tasks structure.

  • Step 2: Rewrite the feature around the actual output

Describe the feature as completed docs-only normalization work rather than an unexecuted draft.

  • Step 3: Publish the normalized backlog

Keep one ordered backlog with explicit risks, dependencies, and future feature boundaries.

Task 2: Reconcile related source-of-truth docs

Files:

  • Modify: docs/features/frontend-debt-audit/spec.md

  • Modify: docs/features/backend-architecture-refactor/spec.md

  • Step 1: Remove stale already-closed debt notes

Reclassify items already covered by api-envelope-contract and backend-architecture-refactor.

  • Step 2: Point remaining open debt at the canonical backlog

Avoid competing backlog lists by linking residual items to architecture-quality-backlog.

  • Step 3: Synchronize status wording

Update backend-architecture-refactor from draft to completed state to match its finished tasks.

Task 3: Publish roadmap changes

Files:

  • Modify: docs/roadmap.md

  • Step 1: Mark completed architecture refactor work as done

Backend Architecture Refactor must no longer appear as open if the feature tasks and verification log are complete.

  • Step 2: Add the new completed docs-only feature

Record architecture-quality-backlog in the completed work history as the canonical backlog publication step.

  • Step 3: Replace the loose candidate list with normalized tracks

Publish the same ordered backlog from the feature spec so roadmap and feature docs match.

Task 4: Final consistency pass

Files:

  • Read: docs/features/architecture-quality-backlog/spec.md

  • Read: docs/features/architecture-quality-backlog/plan.md

  • Read: docs/features/architecture-quality-backlog/tasks.md

  • Read: docs/features/frontend-debt-audit/spec.md

  • Read: docs/features/backend-architecture-refactor/spec.md

  • Read: docs/roadmap.md

  • Step 1: Confirm docs-only scope

Only documentation files should change.

  • Step 2: Confirm consistent backlog ordering

The five normalized directions must appear with the same meaning everywhere they are referenced.

  • Step 3: Confirm no duplicate stale backlog remains

Historical docs can keep audit context, but they should no longer compete with the canonical backlog.