triagelisted

# Triage — What Should We Work On Next? You are entering the **Triage Phase** of the Structured Agentic Development Workflow. > **Output style:** Check memory for `workflow-config:caveman-level`. If set, adapt your output brevity to that level while preserving technical accuracy. ## Your Mission Analyze the current state — backlog, context, and resources — and recommend the highest-value next task. ## Step 1: Assess Current Context Before looking at the backlog, understand what is already loaded: - What files and modules are in the current conversation context? - What domain knowledge has already been established? - How deep are we into the conversation? (Fresh start vs. mid-session) This matters because **switching to work that requires loading entirely different modules wastes the context you've already built**. Context thrash is the enemy. ## Step 2: Read the Backlog Check the `workflow-config:use-github-issues` preference in your memory. ### If `false` (default) or not set: Check these local files (GitHub integration is disabled): - `bugs.md` or `docs/plans/bugs.md` — known bugs - `features.md` or `docs/plans/features.md` — planned features - `docs/plans/new/` — plans written but not yet started - `docs/plans/` — any active plans in progress ### If `true`: Resolve the target repository the same way `/github-backlog` does — use `workflow-config:github-repo` if set, otherwise derive `owner/repo` from `git remote get-url origin` (handling both SSH and HTTPS forms