create-tasks

The create-tasks skill is an essential tool for software engineers and product managers aimed at transforming high-level requirements or PRDs into granular, executable development units. It enforces a rigorous discipline in task decomposition, ensuring that every task is self-contained, high-context, and ready for immediate implementation without ambiguity. By mandating vertical slicing, the skill prevents the common pitfall of horizontal task creation (e.g., building separate API and UI tasks), ensuring each deliverable represents a user-facing improvement that can be demoed upon completion.

• Employs Example Mapping to translate vague PRD bullet points into concrete executable specifications using the Given-When-Then format for acceptance criteria.

• Enforces the INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable) to ensure tasks are manageable and sized for a single day of work.

• Uses the SPIDR technique (Paths, Interfaces, Data, Rules, Spikes) to systematically break down epics and complex features into manageable vertical slices.

• Provides a robust task template including context, key design decisions, acceptance criteria, dependencies, related code, and verification steps to minimize context switching for the implementing engineer.

• Promotes the 'Definition of Done' culture by ensuring every task has clear, verifiable outcomes.

• Best used during sprint planning, feature breakdown sessions, or when grooming a backlog of technical requirements.

• Expected inputs include raw PRD notes, user stories, bug reports, or feature requests. Outputs are markdown-formatted, structured task cards ready for project management tools like Jira, GitHub Issues, or Linear.

• Always validate task size before creation; if a task cannot be completed within one day, use SPIDR to split it further.

• Ensure deliverables are user-centric rather than technical in nature to maintain value alignment.

• If documentation or project conventions are unclear, the skill instructs the user to clarify and document them first.