story-driven-dev

Translate ideas into user stories, then implement each story as a testable MCP tool with unit tests. Use when: (1) building a new feature from an idea or requirement, (2) creating MCP tools from user stories, (3) writing MCP server tests, (4) replacing flaky E2E tests with unit-tested MCP tools, (5) story-driven development, (6) exposing business logic as MCP tools. Triggers: 'new feature', 'user story', 'MCP from idea', 'test MCP tool', 'create MCP server from requirements', 'story-driven', 'replace E2E with unit tests'.