Can I use different task formats with this plugin?

Yes, while this skill specifically focuses on the Detailed Format, the lovely-tasks plugin also supports Spec-Kit, OpenSpec, and Generic Checklist formats.

Where are these tasks typically stored?

Tasks are managed within the docs/tasks.md file of your project, allowing them to be version-controlled alongside your source code.

What should be recorded in the Notes section?

The Notes section is used to track progress, findings, solutions tried (successful or not), deviations from the original plan, and any active blockers.

How does this skill define a 'Complete' task?

A task is only considered complete when every single checkbox in the Acceptance Criteria, Tests, and Documentation sections is marked as done [x]. There are no exceptions.

What is the primary purpose of the Task Structure skill?

It defines a standardized, detailed markdown format for tracking implementation tasks to ensure consistency, clarity, and thoroughness throughout the development lifecycle.

Lovely Task Structure

Name: Lovely Task Structure
Author: LovelyStack

byLovelyStack

•

Productividad y Flujo de Trabajo

Standardizes project implementation tracking using a comprehensive, multi-section markdown template for software development tasks.

Acerca de

The Task Structure skill provides a rigorous framework for managing development workflows within Claude Code by enforcing a standardized template in your project's tasks documentation. It ensures every implementation task includes measurable acceptance criteria, implementation plans, testing requirements, and documentation updates. By requiring specific status values and complete checkbox verification, it prevents premature task completion and maintains a detailed history of progress, research, and technical decisions directly in your repository.

Características Principales

Strict status enforcement (TODO, In Progress, Complete)
Support for visual demo instructions and research notes
1 GitHub stars
Integrated checklists for testing and documentation
Standardized markdown templates for implementation tasks
Comprehensive acceptance criteria tracking

Casos de Uso

Enforcing a strict 'Definition of Done' across a development team
Tracking complex feature implementations with multiple technical dependencies
Maintaining a transparent audit trail of technical decisions and research

Acerca de

Características Principales

Strict status enforcement (TODO, In Progress, Complete)
Support for visual demo instructions and research notes
1 GitHub stars
Integrated checklists for testing and documentation
Standardized markdown templates for implementation tasks
Comprehensive acceptance criteria tracking

Casos de Uso

Enforcing a strict 'Definition of Done' across a development team
Tracking complex feature implementations with multiple technical dependencies
Maintaining a transparent audit trail of technical decisions and research