Feature Request
Summary
CLEO has no first-class deadline / due-date field. Time-pressured tasks (e.g., external API sunsets, regulatory deadlines) can only be expressed in description text or acceptance criteria — invisible to cleo briefing, cleo next, and any orchestration heuristic.
Concrete need
SG-SoR T148 + T149 (cleo show T148, cleo show T149) have hard external deadline 2026-06-01 (Google Gemini 2.0 sunset, 12 days from 2026-05-20). The deadline is buried in the acceptance criteria and description. cleo briefing does not surface it. Future agents resuming this project see "P1 severity, medium priority" and have no signal that the clock is ticking.
cleo show T148 | jq '.data.task.acceptance[1]'
# → "Hard deadline: 2026-06-01 (Google sunset); ADR landed by 2026-05-25"
# No way to query "what's due in the next 14 days?"
cleo deadlines # ← does not exist
cleo find --due-before 2026-06-01 # ← does not exist
Proposed design
- New field
deadline on tasks (ISO 8601 date, nullable).
cleo update <id> --deadline 2026-06-01 to set.
- New command
cleo deadlines [--before YYYY-MM-DD] [--severity Pn] [--within Nd] returning sorted list (soonest first).
cleo briefing surfaces tasks within N days (default 14) under a ⚠ deadlines section.
cleo next boosts deadline-pressured tasks in the ranking (alongside priority + severity).
cleo show <id> renders Deadline: 2026-06-01 (12 days) when set.
Impact
Severity (P0-P3) is the closest existing primitive but doesn't carry a date — and (separately) the P0 attestation gate makes it unusable without signing keys (see related bug). A deadline field is the clean orthogonal axis.
Cross-ref
.cleo/research/sg-sor/06-cleo-gaps.md issue #6.
Area: cli
Are you using an AI agent?
Yes - AI agent filed this issue
Environment
| Component |
Version |
| CLEO |
2026.2.1 |
| Node.js |
v24.13.1 |
| OS |
linux 6.19.14-200.fc43.x86_64 x64 (x64) |
| Shell |
/bin/bash |
| gh CLI |
gh version 2.87.3 (2026-02-23) |
| Install |
/home/keatonhoskins/.npm-global/bin/cleo |
Feature Request
Summary
CLEO has no first-class deadline / due-date field. Time-pressured tasks (e.g., external API sunsets, regulatory deadlines) can only be expressed in description text or acceptance criteria — invisible to
cleo briefing,cleo next, and any orchestration heuristic.Concrete need
SG-SoR T148 + T149 (
cleo show T148,cleo show T149) have hard external deadline 2026-06-01 (Google Gemini 2.0 sunset, 12 days from 2026-05-20). The deadline is buried in the acceptance criteria and description.cleo briefingdoes not surface it. Future agents resuming this project see "P1 severity, medium priority" and have no signal that the clock is ticking.Proposed design
deadlineon tasks (ISO 8601 date, nullable).cleo update <id> --deadline 2026-06-01to set.cleo deadlines [--before YYYY-MM-DD] [--severity Pn] [--within Nd]returning sorted list (soonest first).cleo briefingsurfaces tasks within N days (default 14) under a⚠ deadlinessection.cleo nextboosts deadline-pressured tasks in the ranking (alongside priority + severity).cleo show <id>rendersDeadline: 2026-06-01 (12 days)when set.Impact
Severity (
P0-P3) is the closest existing primitive but doesn't carry a date — and (separately) the P0 attestation gate makes it unusable without signing keys (see related bug). A deadline field is the clean orthogonal axis.Cross-ref
.cleo/research/sg-sor/06-cleo-gaps.mdissue #6.Area: cli
Are you using an AI agent?
Yes - AI agent filed this issue
Environment