github-backlog

# GitHub Backlog Management You are managing the feature and bug backlog on GitHub as part 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. ## Prerequisites This skill talks to GitHub through whatever **GitHub MCP server** the user has configured. The server name is install-specific, so its tools may be named `mcp__<server>__create_issue`, `mcp__<server>__list_issues`, etc. (the official GitHub MCP server is a common choice). Calls to these tools are governed by your normal permission settings — this skill does not pin a server name. Before running any backlog task: 1. `workflow-config:use-github-issues` must be `true`. If it is `false` or unset, GitHub integration is disabled — stop and tell the user to enable it with `/workflow-config` (the local `bugs.md` / `features.md` flow applies instead). 2. A GitHub MCP server must be configured and authenticated in the environment. If no GitHub MCP tools are available in the session, tell the user to configure one and stop. 3. Resolve the target repository (see next section). --- ## Resolve the Target Repository Resolve `owner/repo` **every run**, in this order: 1. **Manual override** — if `workflow-config:github-repo` is set in memory, use it verbatim. 2. **Auto-derive from the local remote** — otherwise read the origin remote and parse it: ```bash git remote ge...