Menu
Review the backlog to determine what to work on next by checking epic and story statuses in docs/backlog/.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Implement a backlog story following the layer order (Domain, Database, API, Frontend, E2E) with TDD.
Automates pre-commit workflow: lint, test, review changes, then commit with conventional commit format.
Verify a story is complete by checking acceptance criteria, running all tests, and updating status.
Add end-to-end Playwright tests for a feature using data-testid selectors, with API and UI test patterns.
Add unit tests for domain logic, database adapters, API endpoints, or frontend components using Vitest patterns.
Create a new user story in the backlog with technical tasks, test scenarios, and epic integration.
| name | review-backlog |
| description | Review the backlog to determine what to work on next by checking epic and story statuses in docs/backlog/. |
docs/backlog/README.md to understand the implementation orderdocs/backlog/ for story statusesFor each story marked Pending or In Progress, run a quick sanity check to detect status drift:
test -f)⚠ DRIFT: E2-US04 is marked Pending but implementation files exist:
- packages/domain/src/use-cases/AccountLockout.ts ✓
- packages/api/src/common/guards/lockout.guard.ts ✓
→ Run /story-complete to verify and update status
**Status**: field vs Epic README table## Backlog Status
### Phase 1: Foundation (Done)
- [x] E1-US01: Project Setup (Done)
...
### Drift Warnings
⚠ E2-US04: Marked Pending but 5/7 implementation files exist → verify with /story-complete
⚠ E3-US02: Story file says Done but Epic README says Pending → sync statuses
### Next Up
<next story to implement>