yaaf

Use when turning a raw feature request, product goal, enhancement idea, or user prompt into a concrete implementation plan and local task-file draft. Produces a scoped proposal, acceptance criteria, actionable task list, legend, task tracker, phased tasks, subtasks, and step-by-step execution items. Replaces open questions with explicit user decisions backed by recommended options, then asks for approval before creating `.tasks/<slug>.md` in the repository.

Use when maintaining yaaf MCP protocol support documentation, the MCP support matrix, generated MCP schema files, MCP config behavior, transports, tool integration, or tests. Keeps libyaaf/mcp/README.md aligned with native MCP implementation and validation.

Use when updating yaaf user documentation, README files, Lua API docs, tool reference docs, MCP docs, examples, build/run instructions, CLI option docs, or runtime behavior docs. Keeps README.md, docs/, docs/modules/, docs/tools/, libyaaf/mcp/README.md, and MCP_PLAN.md aligned with implementation and tests.

Run native unit test coverage with covdbg in this C++20/CMake project. Use when evaluating gtest coverage, finding uncovered C++ code, deciding whether to add tests or remove dead code, and iterating on coverage for libyaaf without using CTest.