Work Items
Feature vs Task, lifecycle, prior approval and versioned evidence with review by diff.
Feature vs Task · versioned evidence
Feature or Task
All work starts as a Work Item with an identifier and a type. The type decides which plan is generated and whether the GitHub Issues integration opens an issue and a branch.
Feature
- requirements.md
- design.md
- tasks.md
The work needs a specification, involves several design decisions, or changes behavior or architecture.
Task
- plan.md
Documentation, contracts or a small, localized change, with no change in behavior or architecture.
Lifecycle and prior approval
Features and Tasks share the same states. No Work Item can be implemented without an approved plan, and none finishes without going through the Reviewer.
- pendingWork Item created, waiting to be planned.
- readyPlanning finished, waiting for human approval.
- Planning approvalA human sign-off releases the sheet. Silence is not approval.
- in_progressImplementation under way. Only one can exist at a time.
- reviewImplementation finished, waiting for review.
- doneCompleted and approved; terminal state.
- blockedThe work cannot continue.
- changes_requestedThe review rejected the implementation and asks for changes.
Branches, not shortcuts: they describe stopped work or a review that demands corrections.
Prior approval is a checkpoint, not a formality: the person reviews requirements, design and tasks before any code is written. If the Reviewer rejects the implementation, the Work Item returns to in_progress with the requested changes.
Versioned evidence
The repository keeps the evidence of the work; the chat is not the record. Each document has an owner and a moment.
rei item show 2026-10-27_22-04__home-demostrativa-playwright2026-10-2824 lines
- rei item show 2026-10-27_22-04__home-demostrativa-playwright
- Work Item: 2026-10-27_22-04__home-demostrativa-playwright
- title: Home demostrativa con demos y capturas reales
- type: feature
- status: done
- created_at: 2026-10-27T22:04:00-05:00
- base_commit: 8df53a9599b424ee1b3f62bf48562068de70b082
- last_review_commit: (vacío)
- Enlaces: (sin links.json)
- Documentos:
- plan.md no
- requirements.md sí
- design.md sí
- tasks.md sí
- impl.md sí
- review.md sí
- spec.md no
- Sesión: no es la sesión activa
- Validación:
- (sin hallazgos)
- Resultado: OK
The output scrolls vertically and horizontally inside the window; the text is complete.
rei validate 2026-10-27_22-04__home-demostrativa-playwright2026-10-283 lines
- rei validate 2026-10-27_22-04__home-demostrativa-playwright
- == Validando Work Item: 2026-10-27_22-04__home-demostrativa-playwright ==
- Resultado: OK
Complete output.
rei doctor2026-10-2843 lines
- rei doctor
- [OK] AGENTS.md
- [OK] .rei/docs/harness/workflow.md
- [OK] .rei/docs/harness/specs.md
- [OK] .rei/docs/harness/task.md
- [OK] .rei/docs/harness/meta.md
- [OK] .rei/docs/harness/progress.md
- [OK] .rei/docs/harness/integrations/github.md
- [OK] .rei/docs/harness/integrations/github/core.md
- [OK] .rei/docs/harness/integrations/github/backlog.md
- [OK] .rei/docs/harness/integrations/github/templates.md
- [OK] .rei/docs/harness/integrations/github/errors.md
- [OK] .rei/docs/project/architecture.md
- [OK] .rei/docs/project/conventions.md
- [OK] .rei/docs/project/verification.md
- [OK] .rei/agents/leader.md
- [OK] .rei/agents/spec_author.md
- [OK] .rei/agents/implementer.md
- [OK] .rei/agents/initializer.md
- [OK] .rei/agents/reviewer.md
- [OK] .rei/templates/current.md
- [OK] .rei/templates/history.md
- [OK] .rei/templates/meta.json
- [OK] .rei/specs/
- [OK] .rei/progress/work-items/
- [OK] .rei/progress/current.md
- [OK] .rei/progress/history.md
- [OK] Documentación del proyecto personalizada.
- [OK] 2026-10-27_00-31__estrategia-producto-web
- [OK] 2026-10-27_01-54__fundaciones-visuales-shell-docs
- [OK] 2026-10-27_02-59__tests-logica-jest
- [OK] 2026-10-27_03-17__contenido-producto-flujo
- [OK] 2026-10-27_11-04__pulido-home-copy-aprobacion
- [OK] 2026-10-27_11-36__conceptos-guias-docs
- [OK] 2026-10-27_12-08__referencia-operacion-docs
- [OK] 2026-10-27_20-34__pulido-hero-inline-github-issues
- [OK] 2026-10-27_22-04__home-demostrativa-playwright
- [OK] 2026-10-28_01-06__pulido-tipografia-movil-a11y
- [OK] 2026-10-28_02-49__producto-secciones-full-bleed
- [OK] 2026-10-28_23-07__producto-ciclo-terminal-interactivos
- [OK] Sesión activa: 2026-10-28_23-07__producto-ciclo-terminal-interactivos (estado: in_progress, agente: _—_)
- [OK] Repositorio git detectado. HEAD=e7c9a600ae6a67e782e3b281a45f72e10c876db6
- [INFO] 2 checks configurados en .rei/config.json (no ejecutados).
- [OK] Sin fallos. Harness íntegro.
The output scrolls vertically and horizontally inside the window; the text is complete.
.rei/specs/<id>/
.rei/
specs/ <id>/ meta.json Type, status, base_commit and last_review_commit.
Leader on create and approve; Reviewer on reject
.rei/
specs/ <id>/ requirements.md What the Feature must do and how it is verified.
Spec Author
.rei/
specs/ <id>/ design.md How it is implemented: decisions, files and verification.
Spec Author
.rei/
specs/ <id>/ tasks.md Ordered tasks with their R-id.
Spec Author
.rei/
specs/ <id>/ plan.md Short step-by-step plan for a Task.
Spec Author
.rei/
specs/ <id>/ links.json Issue, branch and base when the GitHub integration is active.
Leader · GitHub integration
.rei/progress/
.rei/
progress/ current.md Live session: state, log and next step.
Spec Author starts it; Implementer maintains it
.rei/
progress/ history.md Append-only summary of each closed Work Item.
Reviewer when archiving the session
.rei/progress/work-items/<id>/
.rei/
progress/ work-items/ <id>/ impl.md Summary, files, changes and verification of the implementation.
Implementer
.rei/
progress/ work-items/ <id>/ review.md Verdict, verifications, observations and required actions.
Reviewer
.rei/
progress/ work-items/ <id>/ spec.md Reason for the block, missing information and decisions that need human intervention.
Spec Author
Review by diff
With git, review is limited to the actual changes of the Work Item. base_commit marks the start of the implementation and last_review_commit the point already reviewed; rei review-diff produces the review package. Without git, the flow still works in read mode.