sdd:add-task

The skill automates draft task file creation by parsing user-provided titles to generate action-oriented names and sanitized filenames. It verifies the .specs/tasks/draft/ folder structure exists before writing the standardized markdown file.

Dependency handling extracts declared prerequisites from user input and preserves them in the draft file. The skill also verifies the .specs/tasks/ folder structure exists before writing the output markdown.

Yes, it integrates with repository-based project workflows by writing standardized draft markdown files into the .specs/tasks/draft/ directory. It sanitizes filenames and classifies issue types to match existing repository conventions.

Yes, you can input a brief stakeholder note like 'Add validation to form inputs' to generate a draft task file. The skill parses the intent to produce an action-oriented title, issue type, and sanitized filename for triage.

The best way to formalize ad-hoc requests is using automated task generation to convert brief descriptions into consistent markdown files. This reduces repetitive manual effort and errors by placing standardized drafts in .specs/tasks/draft/.

Automated task generation eliminates repetitive and error-prone manual entry by standardizing the creation process. It automatically parses input for issue types and dependencies, ensuring consistent draft markdown files for faster triage.