Add /issues skill and outstanding-work memory ledger

[BigSimmo]

Summary

• Adds a durable, cross-session tracker for outstanding tasks, recommendations, and issues, recalled with /issues.
• docs/outstanding-issues.md — the persistent memory (single source of truth). Chat context resets between sessions; this committed file does not. Seeded with 5 genuinely-open items imported from existing repo docs, each with a source pointer (process-hardening.md debts + one rag-hybrid-findings-and-todo.md recommendation).
• .claude/skills/issues/SKILL.md — the issues skill. A plain /issues is read-only: it reads the ledger and states the open items back, grouped by priority with a count. /issues add|done|update|capture … mutate the ledger and commit only that file (no push unless handing off).
• AGENTS.md — a short pointer so future sessions and other tools discover the memory and the read-only-by-default contract.

Verification

• npm run verify:pr-local

Verification not run: docs/skill-only change — adds two Markdown files (docs/, .claude/skills/) and one AGENTS.md doc edit; no source, config, or test code is touched, so the code gates do not apply. Prettier formatting was applied to the new Markdown files and the pre-push format guard passed.

• npm run verify:ui when UI, routing, styling, browser behavior, reduced-motion, or forced-colors behavior changed — n/a
• npm run verify:release before release or handoff confidence claims — n/a

Risk and rollout

• Risk: Minimal — additive documentation and a Claude Code skill definition. No runtime, retrieval, ranking, clinical, privacy, or deployment behavior changes.
• Rollback: Delete the two new files and revert the AGENTS.md pointer.
• Provider or production effects: None.

Clinical Governance Preflight

Not applicable — the change does not touch ingestion, answer generation, search/ranking, source rendering, document access, privacy, production env, or clinical output. It only records references to such work as tracked items; acting on any recorded item later still goes through the usual gates.

Notes

• IDs are monotonic via a <!-- issues:next-id=NNN --> marker; resolved items are archived (not deleted) for an auditable history.
• The skill respects the repo's RAG/clinical/privacy flagging rules: recording an item is fine, but acting on one that touches a protected surface still needs the usual approval gate.

🤖 Generated with Claude Code

https://claude.ai/code/session_018v3T5ahDyiT8nHqdjCdfB8

---

Generated by Claude Code

[coderabbitai]

Warning

Review limit reached

@BigSimmo, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 27 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 3d48cdf5-0589-4152-9216-b8c7bf534a3e

📥 Commits

Reviewing files that changed from the base of the PR and between c308fdc and 658761d.

📒 Files selected for processing (3)

• .claude/skills/issues/SKILL.md
• AGENTS.md
• docs/outstanding-issues.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/task-tracking-issues-skill-82jxwr

---

_{Comment @coderabbitai help to get the list of available commands.}

[supabase]

This pull request has been ignored for the connected project sjrfecxgysukkwxsowpy because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.

---

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.