Skip to main content

Epic 5, Story 1, Task 42: Implementation Planning Workflow (IPW) — ICW consolidation

Task ID: E5:S01:T42
Status: ✅ COMPLETE (v0.5.1.42+3)
Priority: HIGH
Estimated Effort: Medium (documentation + framework alignment; optional handler/registry follow-up)
Created: 2026-03-31
Last updated: 2026-04-02 (v0.5.1.42+3 — AC5 retro wiring + AC7 validator complete; FR-042 closed).
Version: v0.5.1.42+3
Code: E5S01T42

Repository Pattern: FR-042 = E5:S01:T42 (first implementation build when delivered: e.g. v0.5.1.42+1)

Scope​

Repository anchor and implementation home for FR-042: Implementation Planning Workflow (IPW).

This task covers:

  1. Canonical planning workflow — IPW delivers the single, repeatable process for spec + test design + implementation plan as durable docs, with mandatory bidirectional wiring between host task doc and plan doc (FR-042 §2–§3, §7).
  2. ICW merge — The Implementation Cycle Workflow (ICW) brand and parallel planning path (FR-040, ICW Cursor trigger, implementation-cycle-workflow package, icw_handler.py) are consolidated into IPW: IPW / IPW E:S:T is canonical; ICW is deprecated or alias-only per FR-042 R10–R11 and AC10–AC11.
  3. Non-goals — Does not replace RW (release) or Implementation Cycle execution discipline (TDD, etc.); IPW feeds those steps with artifacts.

Deliverables​

  • IPW SoP / workflow doc and plan doc template per FR-042 R01–R02, AC1–AC2, AC8
  • .cursorrules (and any adopter-facing rule copies): IPW canonical; ICW section aligned to FR-042 §7 (AC9–AC10)
  • workflow-registry / framework README: ICW entry notes IPW consolidation (AC11)
  • Cross-references: FR-040, FR-048, E5:S01:T40, E5:S01:T48 updated so planning expectations point at IPW where they previously implied a separate ICW planning pipeline (FR-042 R12, AC12)
  • Optional (FR-042 R13): Technical migration — icw_handler.py module docstring + package README legacy consolidation notice (full handler path cleanup deferred)

Input​

Acceptance Criteria​

Aligned with FR-042 acceptance criteria (AC1–AC12).

  • AC5/AC7 complete: historical plan docs wired; validator script implemented and passing.

Dependencies​

  • None blocking initial doc/RW alignment work
  • Coordinates with: Epic 2/6 workflow maintainers if registry or icw_handler code paths change (R13)

References​

  • Plan doc (bidirectional): IPW-E5S01T42-ipw-icw-consolidation.md
  • Implementation Cycle Workflow package (legacy ICW): packages/frameworks/workflow mgt/workflows/implementation-cycle-workflow/