# Specifications

Specifications are organized by feature. Each feature keeps product behavior, technical planning, and implementation tasks in separate files.

| Feature | Product specification | Technical plan | Tasks | Status |
| --- | --- | --- | --- | --- |
| Bulk CSV task import | [spec.md](csv-task-import/spec.md) | [plan.md](csv-task-import/plan.md) | [tasks.md](csv-task-import/tasks.md) | Ready for product decisions and implementation planning |

## Workflow

Read the [project constitution](../.specify/memory/constitution.md), then review a feature in this order: specification, plan, tasks. Product-affecting open questions in the specification must be resolved before implementation.

## References

- [GitHub Spec Kit](https://github.com/github/spec-kit) describes a constitution-to-specification-to-plan-to-tasks workflow.
- [Warp's contributing guide](https://github.com/warpdotdev/warp/blob/master/CONTRIBUTING.md) describes separating consumer-visible product behavior from technical planning.

These sources are cited for workflow context only; their text is not reproduced here.