---
id: specify-task-enum-pgenum
name: Specify Task Enum Values as Drizzle pgEnum
status: completed
depends_on: []
scope: single
risk: trivial
impact: isolated
level: implementation
---

## Description

**S15**: The categorical enum values (`scope`, `risk`, `impact`, `level`, `priority`, `status`) are documented as text strings in `tasks.md` but not referenced as Drizzle `pgEnum` types. Specify that these should be `pgEnum` for type safety, with the decomposer template consuming the same definitions. This ensures DB-level constraints match the application-level typing.

## Acceptance Criteria

- [ ] `tasks.md` specifies that `scope`, `risk`, `impact`, `level`, `priority`, and `status` should use `pgEnum` in the Drizzle schema
- [ ] Enum value lists in `tasks.md` match the `pgEnum` definitions
- [ ] Note added that the decomposer template should consume these same enum definitions

## References

- docs/reviews/storage-architecture-review-2026-04-21.md#S15
- docs/architecture/storage/tasks.md
- docs/architecture/storage/table-reference.md (enum reference)

## Notes

> To be filled by implementation agent

## Summary

> To be filled on completion