189 lines
4.6 KiB
Markdown
189 lines
4.6 KiB
Markdown
# TASKS
|
|
|
|
## TASK-000 — Bootstrap RDB project standards
|
|
|
|
Status: Done
|
|
|
|
Goal: Add the project control files used by RDB agent workflows.
|
|
|
|
Acceptance Criteria:
|
|
|
|
- PROJECT_STATE.md exists
|
|
- AGENT_HANDOFF.md exists
|
|
- .rdb/project.json exists
|
|
- context/repository-context.md exists
|
|
- TEST_PLAN.md exists
|
|
- RUN_LOG.md exists
|
|
- README.md explains the structure
|
|
|
|
## TASK-001 — Implement rdb init
|
|
|
|
Status: Done
|
|
|
|
Goal: Create the command that initialises the standard RDB project structure.
|
|
|
|
## TASK-002 — Generate agent prompts
|
|
|
|
Status: Done
|
|
|
|
Goal: Add a command that generates a ready-to-paste implementation prompt for the next Todo task.
|
|
|
|
Acceptance Criteria:
|
|
|
|
- `rdb prompt` reads the next Todo task from TASKS.md
|
|
- The prompt tells the agent to read README.md, TASKS.md, PROJECT_STATE.md, AGENT_HANDOFF.md, and context/agent-guidelines.md
|
|
- The prompt says to implement one task only
|
|
- The prompt includes the task title, status, goal, and acceptance criteria
|
|
- The prompt includes validation instructions
|
|
- The prompt includes reporting instructions
|
|
- Add or update tests
|
|
|
|
## TASK-003 — Improve discovery workflow
|
|
|
|
Status: Done
|
|
|
|
Goal:
|
|
Improve `rdb discover` so it records structured answers into the discovery ledger.
|
|
|
|
Acceptance Criteria:
|
|
|
|
- Ask the 10 core discovery questions
|
|
- Record:
|
|
- Question
|
|
- Answer
|
|
- Confidence
|
|
- Follow-up needed
|
|
- Linked decision
|
|
- Linked task
|
|
- Date
|
|
- Append answers safely
|
|
- Preserve existing discovery history
|
|
- Add/update tests
|
|
- Update RUN_LOG.md
|
|
|
|
## TASK-004 — Implement ask-more command
|
|
|
|
Status: Done
|
|
|
|
Goal: Add a command that finds weak answers and asks deeper follow-up questions.
|
|
|
|
Acceptance Criteria:
|
|
|
|
- command reads discovery-log.md
|
|
- low-confidence answers are detected
|
|
- follow-up answers are appended to discovery-log.md
|
|
|
|
## TASK-005 — Task lifecycle commands
|
|
|
|
Status: Done
|
|
|
|
Goal:
|
|
Allow tasks to be managed from the CLI rather than manually editing TASKS.md.
|
|
|
|
Acceptance Criteria:
|
|
|
|
- `rdb start TASK-ID`
|
|
- Marks task In Progress
|
|
|
|
- `rdb complete TASK-ID`
|
|
- Marks task Done
|
|
|
|
- Updates PROJECT_STATE.md
|
|
- Updates AGENT_HANDOFF.md
|
|
- Updates RUN_LOG.md
|
|
- Preserves task formatting
|
|
- Add/update tests
|
|
- Run python -m pytest
|
|
|
|
## TASK-006 — Agent execution guardrails
|
|
|
|
Status: Done
|
|
|
|
Goal:
|
|
Detect agent stalls, repeated reads, long reasoning loops, and non-progressing execution.
|
|
|
|
Acceptance Criteria:
|
|
|
|
- `rdb guardrails` command exists ✓
|
|
- Detects repeated file reads via AGENT_HANDOFF.md analysis ✓
|
|
- Detects repeated command entries in RUN_LOG.md ✓
|
|
- Flags project files not modified in >48 hours ✓
|
|
- Flags missing test run records in RUN_LOG.md ✓
|
|
- Checks TASKS.md ↔ RUN_LOG.md consistency ✓
|
|
- Produces clear human-readable report with overall status ✓
|
|
- All existing tests still pass (33 → 51) ✓
|
|
- Guardrail-specific tests added (18 new tests) ✓
|
|
|
|
## TASK-007 — Improve generated agent prompts
|
|
|
|
Status: Done
|
|
|
|
Goal:
|
|
Make `rdb prompt` produce smaller, more direct prompts for Claude Code/local LLM agents.
|
|
|
|
Acceptance Criteria:
|
|
|
|
- Prompt includes exact known implementation gap when available
|
|
- Prompt includes existing test command from CLAUDE.md
|
|
- Prompt tells agent not to repeatedly reread unchanged files
|
|
- Prompt tells agent to inspect first, then edit
|
|
- Prompt limits scope to one small implementation step
|
|
- Add/update tests
|
|
|
|
## TASK-012 — Agent telemetry foundation
|
|
|
|
Status: Todo
|
|
|
|
Goal:
|
|
Create a minimal telemetry writer for future agent activity tracking.
|
|
|
|
Implementation Gap:
|
|
There is currently no persistent session log for recording agent activity. Guardrails infer behaviour from markdown and RUN_LOG.md instead of structured telemetry.
|
|
|
|
Acceptance Criteria:
|
|
|
|
- Add a telemetry module
|
|
- Create `.rdb/session-log.jsonl` when recording an event
|
|
- Record JSONL events with:
|
|
- timestamp
|
|
- event_type
|
|
- target
|
|
- details
|
|
- Add tests for writing and appending telemetry events
|
|
- Do not integrate telemetry into every CLI command yet
|
|
|
|
## TASK-013 — Log CLI command execution
|
|
|
|
Status: Todo
|
|
|
|
Goal:
|
|
Record rdb CLI command execution into telemetry.
|
|
|
|
Implementation Gap:
|
|
Telemetry writer exists, but CLI commands do not yet record command execution events.
|
|
|
|
Acceptance Criteria:
|
|
|
|
- Record command execution events
|
|
- Include command name
|
|
- Include success/failure where practical
|
|
- Add/update tests
|
|
|
|
## TASK-014 — Use telemetry in guardrails
|
|
|
|
Status: Todo
|
|
|
|
Goal:
|
|
Make `rdb guardrails` use structured telemetry when available.
|
|
|
|
Implementation Gap:
|
|
Guardrails currently rely on markdown and file mtimes rather than `.rdb/session-log.jsonl`.
|
|
|
|
Acceptance Criteria:
|
|
|
|
- Read telemetry events when present
|
|
- Detect repeated reads from telemetry
|
|
- Detect repeated commands from telemetry
|
|
- Fall back gracefully if telemetry is missing
|
|
- Add/update tests
|