clickup-task-description

To generate QA-ready task descriptions for backend feature changes, the Skill reads source files across controllers, actions, and migrations to identify what was built. It then outputs a concise, QA-oriented description ready for ClickUp ticket creation.

For ClickUp ticket creation, the tool analyzes backend source files including controllers, domain actions, resources, models, migrations, routes, and tests. It reads these specific files to accurately identify and summarize implemented backend feature changes.

To document backend migrations and models for QA testing, describe the implemented backend feature and trigger the Skill. It reads the relevant source files and produces a precise, QA-oriented subtask description with scope and acceptance criteria for testing.

Yes, it works for generating ClickUp subtasks by directly reading existing source code. It identifies implemented changes across controllers, actions, and resources to produce accurate QA-oriented documentation without requiring manual input of feature details.

You should use an automated task description generator for backend work when you need to document implemented features involving controllers, actions, models, or migrations. It ensures accurate, QA-oriented ticket creation by reading the actual source code.