tangweijie/fujian_water_biz_doc
1
0
Fork 0
Code Issues Pull Requests 12 Actions Packages Projects Releases 1 Wiki Activity
fujian_water_biz_doc/specs/003-rev006-reminder-event-design/tasks.md

12 KiB
Raw Blame History

Tasks: REV-006 催缴事件与通知协同设计

Input: Design documents from /specs/003-rev006-reminder-event-design/ Prerequisites: plan.md (required), spec.md (required), research.md, data-model.md, contracts/

Validation: Validation tasks are NOT optional in this repository. Every document change task set MUST include the applicable validation and ledger-sync tasks.

Organization: Tasks are grouped by user story so each document-maintenance slice can be completed, reviewed, and validated independently.

Format: [ID] [P?] [Story] Description

  • [P]: Can run in parallel (different files, no dependencies)
  • [Story]: Which user story this task belongs to (e.g. [US1], [US2], [US3])
  • Include exact file paths in descriptions

Path Conventions

  • Main documents: docs/design/01_Overview/, docs/design/02_Detailed_Design/, docs/design/03_Technical_Design/
  • Governance documents: docs/design/00_Management/
  • Archive references: docs/design/04_Appendix/Archive/
  • Runtime guidance: README.md, AGENTS.md, .specify/templates/

Phase 1: Scope & Source Confirmation (Shared Foundation)

Purpose: Confirm the source-of-truth set and impact boundary before editing.

  • T001 Confirm target documents and exact REV-006 touchpoints in /Volumes/Dpan/github/fujian_water_biz_doc/specs/003-rev006-reminder-event-design/spec.md
  • T002 Confirm governing source-of-truth and allowed reference sources in /Volumes/Dpan/github/fujian_water_biz_doc/specs/003-rev006-reminder-event-design/plan.md
  • T003 [P] Record final scope judgment for REV-006 and exclusions in /Volumes/Dpan/github/fujian_water_biz_doc/specs/003-rev006-reminder-event-design/research.md
  • T004 [P] Identify cross-document impacts for IF-REV-013、四态结果集、停复水联动边界和历史只读口径 in /Volumes/Dpan/github/fujian_water_biz_doc/specs/003-rev006-reminder-event-design/contracts/rev006-interface-contract.md

Phase 2: Foundational Alignment (Blocking Prerequisites)

Purpose: Prepare the cross-document baseline that all user stories depend on.

  • T005 Consolidate REV-006 decisions, entities, and contract fields from /Volumes/Dpan/github/fujian_water_biz_doc/specs/003-rev006-reminder-event-design/research.md, /Volumes/Dpan/github/fujian_water_biz_doc/specs/003-rev006-reminder-event-design/data-model.md, and /Volumes/Dpan/github/fujian_water_biz_doc/specs/003-rev006-reminder-event-design/contracts/rev006-interface-contract.md
  • T006 [P] Cross-check current conflicting references to IF-REV-009 and REV-006 in /Volumes/Dpan/github/fujian_water_biz_doc/docs/design/02_Detailed_Design/12_REV_Detailed.md and /Volumes/Dpan/github/fujian_water_biz_doc/docs/design/03_Technical_Design/03_Interface_Design.md
  • T007 [P] Cross-check historical-only retention rules for 催缴记录/停水记录/预存短信 in /Volumes/Dpan/github/fujian_water_biz_doc/docs/design/03_Technical_Design/01_Database_Design.md and /Volumes/Dpan/github/fujian_water_biz_doc/docs/design/04_Appendix/Archive/05_Data_Dictionary/营收数据字典.md
  • T008 Confirm ledger update expectations for this feature in /Volumes/Dpan/github/fujian_water_biz_doc/docs/design/00_Management/15_SYS002_Requirement_Breakdown.md, /Volumes/Dpan/github/fujian_water_biz_doc/docs/design/00_Management/01_Project_Progress.md, and /Volumes/Dpan/github/fujian_water_biz_doc/docs/design/00_Management/03_Task_Checklist.md

Phase 3: User Story 1 - 定义催缴闭环范围 (Priority: P1) 🎯 MVP

Goal: 让 12_REV_Detailed.md 中的 REV-006 章节具备完整的催缴对象生成、任务分组、停复水联动边界和落地边界说明。

Independent Test: 单独评审 /Volumes/Dpan/github/fujian_water_biz_doc/docs/design/02_Detailed_Design/12_REV_Detailed.md 的 REV-006 章节，应能明确催缴对象来源、策略维度、自动/人工触发边界、停复水只做联动边界、不展开内部流程。

Implementation for User Story 1

  • T009 [US1] Update REV-006 功能说明、业务流程、关键规则和落地边界 in /Volumes/Dpan/github/fujian_water_biz_doc/docs/design/02_Detailed_Design/12_REV_Detailed.md
  • T010 [P] [US1] Add Reminder Candidate、Reminder Strategy、Reminder Task、Disposal Link 对应的数据与规则摘要 to /Volumes/Dpan/github/fujian_water_biz_doc/docs/design/02_Detailed_Design/12_REV_Detailed.md
  • T011 [P] [US1] Sync REV-006 implementation assessment and Story notes in /Volumes/Dpan/github/fujian_water_biz_doc/docs/design/00_Management/15_SYS002_Requirement_Breakdown.md
  • T012 [US1] Run make validate-file FILE=docs/design/02_Detailed_Design/12_REV_Detailed.md and capture result
  • T013 [US1] Run make validate-file FILE=docs/design/00_Management/15_SYS002_Requirement_Breakdown.md and capture result

Checkpoint: User Story 1 is reviewable and confirms the REV-006 business boundary without depending on interface redesign.

Phase 4: User Story 2 - 统一消息协同与结果回写口径 (Priority: P2)

Goal: 在接口主文档中为 REV-006 建立独立正式接口编号、四态结果集、SYS-002 ↔ SYS-010 协同字段和异常/幂等规则。

Independent Test: 单独评审 /Volumes/Dpan/github/fujian_water_biz_doc/docs/design/03_Technical_Design/03_Interface_Design.md，应能确认 IF-REV-013 的职责、IF-EXT-008 的协同边界、四态状态语义以及不再复用 IF-REV-009。

Implementation for User Story 2

  • T014 [US2] Replace REV-006 对 IF-REV-009 的错误引用 with IF-REV-013 in /Volumes/Dpan/github/fujian_water_biz_doc/docs/design/03_Technical_Design/03_Interface_Design.md
  • T015 [US2] Add IF-REV-013 formal interface definition, request/response shape, and responsibility boundary in /Volumes/Dpan/github/fujian_water_biz_doc/docs/design/03_Technical_Design/03_Interface_Design.md
  • T016 [P] [US2] Update IF-EXT-008 collaboration contract, state semantics, idempotency, exception codes, and timing diagrams in /Volumes/Dpan/github/fujian_water_biz_doc/docs/design/03_Technical_Design/03_Interface_Design.md
  • T017 [P] [US2] Sync REV-006 interface mapping, interface numbering, and state terminology in /Volumes/Dpan/github/fujian_water_biz_doc/docs/design/02_Detailed_Design/12_REV_Detailed.md
  • T018 [US2] Run make validate-file FILE=docs/design/03_Technical_Design/03_Interface_Design.md and capture result
  • T019 [US2] Run make validate-file FILE=docs/design/02_Detailed_Design/12_REV_Detailed.md and capture result after interface sync

Checkpoint: User Story 2 is reviewable and fully expresses the REV-006 interface and integration contract independently.

Phase 5: User Story 3 - 明确历史查询与停复水联动边界 (Priority: P3)

Goal: 在数据库和治理文档中收口历史只读查询口径、迁移验收字段和停复水联动追溯边界。

Independent Test: 单独评审 /Volumes/Dpan/github/fujian_water_biz_doc/docs/design/03_Technical_Design/01_Database_Design.md 与治理台账，应能确认旧“催缴记录/停水记录/预存短信”不被误写为新在线主表，同时查询字段和对账口径完整。

Implementation for User Story 3

  • T020 [US3] Update historical read-only retention and online-model boundary for 催缴记录/停水记录/预存短信 in /Volumes/Dpan/github/fujian_water_biz_doc/docs/design/03_Technical_Design/01_Database_Design.md
  • T021 [P] [US3] Add minimum query fields, traceability expectations, and disposal-link wording for REV-006 in /Volumes/Dpan/github/fujian_water_biz_doc/docs/design/03_Technical_Design/01_Database_Design.md
  • T022 [P] [US3] Sync feature completion, implementation status, and follow-up recommendations in /Volumes/Dpan/github/fujian_water_biz_doc/docs/design/00_Management/15_SYS002_Requirement_Breakdown.md
  • T023 [US3] Update /Volumes/Dpan/github/fujian_water_biz_doc/docs/design/00_Management/01_Project_Progress.md with the REV-006 design closure milestone
  • T024 [US3] Update /Volumes/Dpan/github/fujian_water_biz_doc/docs/design/00_Management/03_Task_Checklist.md with the REV-006 tracked-task closure status
  • T025 [US3] Run make validate-file FILE=docs/design/03_Technical_Design/01_Database_Design.md and capture result
  • T026 [US3] Run make validate-file FILE=docs/design/00_Management/01_Project_Progress.md and make validate-file FILE=docs/design/00_Management/03_Task_Checklist.md and capture result

Checkpoint: User Story 3 is reviewable and confirms the historical-query and ledger-governance closure independently.

Final Phase: Cross-Cutting Closure

Purpose: Ensure repository-wide consistency after all story slices are complete.

  • T027 [P] Re-check source-of-truth alignment across /Volumes/Dpan/github/fujian_water_biz_doc/docs/design/02_Detailed_Design/12_REV_Detailed.md, /Volumes/Dpan/github/fujian_water_biz_doc/docs/design/03_Technical_Design/03_Interface_Design.md, /Volumes/Dpan/github/fujian_water_biz_doc/docs/design/03_Technical_Design/01_Database_Design.md, and /Volumes/Dpan/github/fujian_water_biz_doc/docs/design/00_Management/15_SYS002_Requirement_Breakdown.md
  • T028 [P] Run make check-links after all document changes and capture result
  • T029 Prepare final summary with modified files, validation results, remaining risks, and next-step suggestions in /Volumes/Dpan/github/fujian_water_biz_doc/specs/003-rev006-reminder-event-design/quickstart.md

Dependencies & Execution Order

Phase Dependencies

  • Phase 1: Scope & Source Confirmation: No dependencies; MUST finish before content edits
  • Phase 2: Foundational Alignment: Depends on Phase 1; MUST finish before user story work
  • Phase 3: User Story 1: Depends on Phase 2
  • Phase 4: User Story 2: Depends on Phase 2 and should follow User Story 1 because interface mapping must align with the finalized REV-006 business scope
  • Phase 5: User Story 3: Depends on Phase 2 and should follow User Story 2 because database and ledger wording must use the finalized interface numbering and state terms
  • Final Phase: Depends on all selected user stories being complete

Within Each User Story

  • Update target documents before syncing supporting or governance documents
  • Complete content edits before validation
  • Complete validation before ledger updates are marked done
  • Complete ledger sync before final summary

User Story Completion Order

US1 -> US2 -> US3

Parallel Opportunities

  • T003 and T004 can run in parallel after source confirmation
  • T006 and T007 can run in parallel during foundational alignment
  • In US1, T010 and T011 can run in parallel after T009
  • In US2, T016 and T017 can run in parallel after T014 and T015
  • In US3, T021 and T022 can run in parallel after T020
  • T027 and T028 can run in parallel during final closure

Parallel Execution Examples

User Story 1

Run in parallel after T009:
- T010 [P] [US1] Add data/rule summaries in 12_REV_Detailed.md
- T011 [P] [US1] Sync implementation assessment in 15_SYS002_Requirement_Breakdown.md

User Story 2

Run in parallel after T014 and T015:
- T016 [P] [US2] Update IF-EXT-008 contract, states, exceptions, diagrams
- T017 [P] [US2] Sync interface mapping back into 12_REV_Detailed.md

User Story 3

Run in parallel after T020:
- T021 [P] [US3] Add query-field and traceability wording in 01_Database_Design.md
- T022 [P] [US3] Sync feature completion notes in 15_SYS002_Requirement_Breakdown.md

Implementation Strategy

MVP First

先完成 US1，因为 12_REV_Detailed.md 的业务边界是所有后续接口和数据库收口的前提。只要 US1 完成并通过校验，就可以先交付一版可评审的 REV-006 业务范围说明。

Incremental Delivery

  1. 完成 US1，锁定业务边界和排除项
  2. 完成 US2，锁定接口编号、协同边界和四态结果集
  3. 完成 US3，锁定历史只读口径、迁移验收字段和治理台账闭环
  4. 最后统一执行全局一致性检查和链接校验

Notes

  • 每个 story 都可以独立评审，不要求一次性改完全部文档
  • 所有任务都必须回写既有正式文档，不能新建平行正式稿
  • Archive 只作为核对来源，不直接替代主文档
  • 验证和台账同步不是可选项