command-generate-issues

You can generate GitHub Issues from requirements, frontend specs, and API definitions by parsing the documentation to automatically identify tasks, assign priorities, and map dependencies for project management.

Yes, dependency mapping is automated by identifying and linking related issues based on dependencies outlined in your project documentation, ensuring structured task tracking.

Duplicate prevention works by checking for and avoiding the creation of duplicate GitHub Issues based on title similarity before generating new tasks from your documentation.

Issue priorities are automatically assigned High, Medium, or Low levels based on the phase and importance of the tasks identified within your project documentation.

The best way to translate feature specifications into actionable tasks is using document analysis logic to parse requirements and automatically create structured backend, frontend, and documentation issues.

No, you do not strictly need API definitions; the issue generation skill can also parse requirements and frontend specifications to identify tasks and create structured GitHub Issues.