Skip to main content

Feature Request: ICW Task Identifier Argument

Type: Feature Request (FR)
Submitted: 2026-03-10
Submitted By: RMS (AI Dev Kit)
Priority: HIGH
Status: PENDING
GitHub Issue: TBD

Summary​

Extend the planning workflow (IPW; historically ICW) to require a task identifier when invoked, binding sessions to a Kanban task (E:S:T). The implemented icw_handler.py behavior applies to the same planning process; the canonical agent trigger is IPW (FR-042 §7).

Description​

What functionality is desired?​

The ICW should require a task identifier argument when invoked, with the following requirements:

  1. Mandatory Task ID: ICW calls must include a task identifier argument
  2. Clear E/S/T Numbering: The identifier must clearly reference Epic/Story/Task numbers
  3. Flexible Formatting: The exact format can be flexible as long as the task is unambiguous
  4. Planning Mode Enforcement: The task identifier requirement works in conjunction with the existing planning mode requirement

What problem does this solve?​

Currently, the ICW can be called without explicit task binding, which can lead to:

  • Ambiguous Workflows: ICW runs without clear association to specific Kanban tasks
  • Lost Traceability: Difficulty linking ICW execution back to specific requirements
  • Poor Planning Integration: Weak connection between ICW sessions and Kanban planning

What is the use case?​

  • Task-Specific Planning: Users want to run ICW for specific tasks like "E5:S01:T47"
  • Clear Workflow Context: Ensure ICW sessions are explicitly tied to Kanban requirements
  • Improved Traceability: Direct mapping between ICW execution and task documentation
  • Better Planning Integration: Strengthen the connection between ICW and Kanban planning

Who would benefit from this feature?​

  • ICW Users: Clear task context for their implementation planning sessions
  • Project Managers: Better visibility into which tasks are being worked on
  • Developers: Explicit task binding for their implementation work
  • Auditors: Clear traceability between ICW sessions and Kanban tasks

Requirements​

Functional Requirements​

  • FR-048:R01 – ICW requires a task identifier argument when invoked
  • FR-048:R02 – Task identifier must include clear E/S/T numbering (e.g., "E5:S01:T47")
  • FR-048:R03 – Flexible formatting support for various task identifier formats
  • FR-048:R04 – Validation that the task identifier references an existing Kanban task
  • FR-048:R05 – Integration with existing planning mode requirement
  • FR-048:R06 – Clear error messages when task identifier is missing or invalid

Non-Functional Requirements​

  • FR-048:NF01 – Backward Compatibility: Ensure existing ICW functionality remains intact
  • FR-048:NF02 – User Experience: Clear and helpful error messages
  • FR-048:NF03 – Performance: Minimal impact on ICW startup time

Scope Analysis​

Problem Domain: Implementation Cycle Workflow (ICW), Task Management, Planning Integration
Affected Areas:

  • Documentation
  • Testing
  • ICW Handler Scripts
  • Configuration
  • Backend/API
  • Frontend/UI
  • Database/Schema
  • Other: Kanban integration

Estimated Complexity:

  • Simple (1-3 days)
  • Medium (1 week)
  • Complex (2+ weeks)
  • Very Complex (1+ month)

Use Cases​

Primary Use Case​

  1. User wants to run ICW for a specific task
  2. User calls ICW with task identifier: icw --task E5:S01:T47
  3. ICW validates the task exists in Kanban
  4. ICW proceeds with planning mode execution for that specific task
  5. All ICW output and artifacts are linked to the task identifier

Additional Use Cases​

  • Multiple Formats: Support various formats like "E5:S01:T47", "E5S01T47", "T47"
  • Task Validation: Verify task exists before proceeding
  • Error Handling: Clear guidance when task identifier is invalid
  • Documentation Integration: Automatic linking to task documentation

Acceptance Criteria​

  • AC1: ICW requires task identifier argument and fails gracefully without it
  • AC2: Task identifier validation checks for E/S/T numbering patterns
  • AC-3: ICW validates that referenced task exists in Kanban
  • AC4: Clear error messages guide users to correct task identifier format
  • AC5: ICW execution context is explicitly bound to the specified task
  • AC6: Planning mode requirement remains intact with task identifier requirement

Dependencies​

Blocks:

  • ICW task-specific planning sessions
  • Improved ICW-Kanban integration

Blocked By:

  • None (this is an enhancement to existing ICW functionality)

Related Work:

  • E5:S01:T40 – Implementation Cycle Workflow (ICW)
  • FR-040 – Implementation Cycle Workflow (ICW)
  • ICW Handler Scripts and Configuration

Intake Decision​

Intake Status: PENDING
Intake Date: 2026-03-10
Intake By: RMS

Decision Flow Results:

  • Story Match Found: [Epic 5, Story 1] → Task [T]
  • New Story Created: Epic 5, Story 1 → Task 48
  • New Epic Created: [Epic X, Story 1, Task 1]

Assigned To:

  • Epic: Epic 5 (Documentation Management and Maintenance)
  • Story: Story 1 (FR Repository)
  • Task: Task 48 (E5:S01:T48)
  • Version: v0.5.1.48+1

Kanban Links:

Notes​

  • This enhancement builds on the existing ICW planning mode requirement
  • The task identifier format should be flexible but unambiguous
  • Integration with Kanban task validation is important for reliability
  • Clear error messaging is critical for good user experience

References​

  • E5:S01:T40 – Implementation Cycle Workflow (ICW)
  • FR-040 – Implementation Cycle Workflow (ICW)
  • ICW Handler: packages/frameworks/workflow mgt/scripts/icw/icw_handler.py
  • ICW Configuration: packages/frameworks/workflow mgt/workflows/implementation-cycle-workflow/

This feature request follows the Kanban Framework FR template and is anchored as FR-048 in the FR repository story (E5:S01:T48).