Skip to main content

Story 006 – Feature Requests

Status: IN PROGRESS Priority: MEDIUM
Estimated Effort: [TBD]
Created: 2025-12-07
Last updated: 2026-04-20 (v0.6.6.62+1 – Kanban documentation setup) Version: v0.6.6.62+1 Code: E6S06

Note: This story was renumbered from S05 to S06 as part of the repository story abstract space resolution (E9:S01:T08).

Story Type: Perpetual Maintenance
Completed: N/A (Perpetual story - never completes)
Explanation: This story represents ongoing feature request tracking and implementation work. New feature requests will create new tasks under this story. The story remains IN PROGRESS even when all current tasks are complete, as new feature requests may be submitted at any time.

Task Checklist​

  • E6:S06:T01 – FR/BR/UXR Prioritization Board Implementation - ✅ COMPLETED (HIGH priority, Create prioritization board for FRs, BRs, and UXRs with identical structure to Kanban board)

  • E6:S06:T02 – Fix Release Workflow Micromanagement Issues - 🔄 IN PROGRESS, BLOCKED (CRITICAL, User pain and frustration with tool discovery, pattern matching failures, and excessive manual intervention; blocking productive work. Root cause identified as Cascade whitelist security prompts.)

  • E6:S06:T03 – Investigate Apple SDK License Blocking Issue - ✅ COMPLETED (HIGH priority, Apple SDK license blocking issue prevents proper installation or usage of ai-dev-kit components on Apple platforms; needs investigation to understand root cause and implement solution)

  • E6:S06:T41 – Windsurf: Investigate how to leverage AGENTS.md and SKILL.md for workflows - ✅ COMPLETED (CRITICAL, Implement AGENTS.md and SKILL.md to define specialized workflow agents and capabilities, enabling Cascade to execute workflows autonomously without manual intervention. This addresses fundamental workflow execution issues including terminal interaction problems and agent behavior inconsistencies.)

  • E6:S06:T42 – Fix UKW Agent Board Cleanup Failure - ✅ COMPLETED (HIGH priority, UKW Agent does not properly clean up completed tasks from MoSCOW sections, leaving completed tasks listed in active priority sections despite being marked as COMPLETE. This impairs autonomous workflow reliability and requires manual intervention.)

  • E6:S06:T57 – BR-039: Cascade whitelist / security prompt usability (vendor) - ✅ COMPLETE (RW -k v0.6.6.57+5 v0.4.704+5 — Option B SemVer; BR-039 IN PROGRESS for product)

  • E6:S06:T58 - RW --art flag should work in all RW modes - ✅ COMPLETE (v0.6.6.58+2) (HIGH priority, BR-060: all-mode support implemented; follow-up cleanup release for board consistency and repo hygiene)

  • E6:S06:T56 – RW Ambiguous Task Identifier Typo Risk - ✅ COMPLETE (v0.6.6.56+4) (HIGH priority, BR-056: validate_rw_task_intent + Step 1b; live verification 2026-03-25)

  • BR-060 — canonical implementing task E2:S01:T09 (RW agent execution / validators); task doc | stub for old paths | BR-060

  • E6:S06:T61 – UXR-006: MoSCOW row last-modified UTC stamps - 🔄 IN PROGRESS (v0.6.6.61+1 — RW; HIGH — drift / IPW; optional AC-4 tooling open)

  • E6:S06:T62 – Global IPW-gated implementation contract (FR-083) - TODO (HIGH, enforce repository-wide implementation lock behind IPW preconditions plus explicit user authorization)

  • E6:S06:T999 – Board Cleanup Test Task - ✅ COMPLETED (LOW priority, Dummy task for testing UKW Agent board cleanup functionality. This task will be marked as COMPLETE to trigger board cleanup and verify removal from active sections.)

    • Task: T999-board-cleanup-test.md
    • Status: ✅ COMPLETED - Board implemented with MoSCOW structure, all 69 items tracked
    • Completed: 2026-03-09

  • E6:S06:T02 – Fix Release Workflow Micromanagement Issues - TODO (HIGH priority, Implement simplified, reliable Release Workflow to reduce user friction)

Overview​

This story tracks all feature requests related to framework management, installation tools, update mechanisms, and related framework management processes. Feature requests are converted into tasks following the FR/BR → Task → Story → Epic flow defined in the Kanban governance policy.

Perpetual Story: This is a perpetual maintenance story that never completes. New feature requests will create new tasks under this story. The story remains IN PROGRESS even when all current tasks are complete, as feature request tracking is an ongoing activity.

Goal​

Systematically track, prioritize, and implement feature requests for framework packages, installation tools, update mechanisms, and related framework management processes.

Tasks​

  • E6:S06:T01 – FR/BR/UXR Prioritization Board Implementation - ✅ COMPLETED (HIGH priority)

  • E6:S06:T02 – Fix Release Workflow Micromanagement Issues - TODO (HIGH priority)

Dependencies​

Blocks:

  • None

Blocked By:

  • None

Coordinates With:

  • Epic 5 (Documentation Management) - Features may require documentation updates
  • Epic 2 (Workflow Management Framework) - Features for workflow framework tools
  • Epic 7 (Examples & Adoption) - Features for framework adoption and examples

References​

  • docs/project-management/kanban/epics/Epic-6/Epic-6.md
  • docs/project-management/rituals/policy/kanban-governance-policy.md - FR/BR → Task → Story → Epic flow