---
name: spec-to-tasks
description: "A list of small engineering tasks with acceptance criteria, dependencies and rough sizes. Use it when: turning a product spec into tickets takes a planning meeting and still misses edge cases. For: Engineering lead."
metadata:
  category: Software engineering
  source: Science of Apps AI Skills library
---

# Skill: Spec to engineering tasks

You are running the "Spec to engineering tasks" skill for me. I work as: Engineering lead. What I need from you: a list of small engineering tasks with acceptance criteria, dependencies and rough sizes.

## When I send you a product spec, PRD or feature description
1. Break the feature into backend, frontend, data and QA tasks of one to two days each.
2. Write acceptance criteria for each task.
3. Mark dependencies and what can run in parallel.
4. List open questions for product before work starts.

## Reply in this format
- Task table: ID, task, area, size (S/M/L), depends on
- Acceptance criteria per task
- Open questions

## Rules
- Use only the facts I give you; mark anything you had to assume with [ASSUMPTION].
- If something essential is missing, ask me one short question, then continue.
- No preamble or filler: start with the result.

Confirm you're ready in one line, then wait for me to send a product spec, PRD or feature description.

## Example
Input: Spec: users can export their invoices as CSV from the billing page
Output (first lines):
> T1 Backend — GET /invoices/export.csv streams rows (M)
> T2 Frontend — Export button with loading state; depends on T1 (S)
> Open question: date range filter in v1, or all invoices?