spawn-task

To create a structured task prompt for feature implementation, define the task description, priority, scope, and timeline, then use a standardized template to guide execution and documentation. This ensures objectives are self-contained without needing additional context.

The best way to document bug fixing tasks is using a structured template that defines descriptions, priorities, scopes, and timelines. This guides task execution with clear objectives and checklists for comprehensive documentation.

Yes, you can use task documentation templates for both feature implementation and bug fixing. The templates assist in defining task descriptions, priorities, scopes, and timelines to guide execution across different software engineering scenarios.

No, you do not need additional project context when generating task prompts. The process creates detailed, self-contained task prompts that facilitate feature implementation and bug fixing independently without requiring supplementary background information.

Task discovery works by gathering essential project planning elements like task descriptions, priorities, scopes, and timelines. This process structures the information into a standardized template that guides subsequent task execution and documentation.