akka-checklistlisted

## Checklist Purpose: "Unit Tests for English" **CRITICAL CONCEPT**: Checklists are **UNIT TESTS FOR REQUIREMENTS WRITING** - they validate the quality, clarity, and completeness of requirements in a given domain. **NOT for verification/testing**: - NOT "Verify the button clicks correctly" - NOT "Test error handling works" - NOT "Confirm the API returns 200" - NOT checking if code/implementation matches the spec **FOR requirements quality validation**: - "Are visual hierarchy requirements defined for all card types?" (completeness) - "Is 'prominent display' quantified with specific sizing/positioning?" (clarity) - "Are hover state requirements consistent across all interactive elements?" (consistency) - "Are accessibility requirements defined for keyboard navigation?" (coverage) - "Does the spec define what happens when logo image fails to load?" (edge cases) **Metaphor**: If your spec is code written in English, the checklist is its unit test suite. You're testing whether the requirements are well-written, complete, unambiguous, and ready for implementation - NOT whether the implementation works. ## User Input You **MUST** consider the user input before proceeding (if not empty). ## Execution Steps 1. **Setup**: Call the `akka_sdd_list_specs` MCP tool to find features and their available documents. From the response, identify the target feature's FEATURE_DIR and which artifacts exist (AVAILABLE_DOCS: spec.md, plan.md, tasks.md, etc.). If no features exist, instruct