← ClaudeAtlas

get-backlog-specslisted

sr:get-backlog-specs — View product-driven backlog from GitHub Issues and propose top 3 for implementation.
fjpulidop/specrails-core · ★ 9 · AI & Automation · score 76
Install: claude install-skill fjpulidop/specrails-core
Display the product-driven backlog by reading issues/tickets from the configured backlog provider (read from .specrails/backlog-config.json). These are feature ideas generated through VPC-based product discovery — evaluated against user personas. Use `/specrails:auto-propose-backlog-specs` to generate new ideas. **Input:** $ARGUMENTS (optional: comma-separated areas to filter. If empty, show all.) --- ## Phase 0: Environment Pre-flight Verify the backlog provider is accessible: Read `.specrails/backlog-config.json` to determine `BACKLOG_PROVIDER` (default: `github`). - If `BACKLOG_PROVIDER=github`: run `gh auth status 2>&1`. If it fails, stop: "GitHub CLI is not authenticated. Run `gh auth login` first." - If `BACKLOG_PROVIDER=local`: check for `.specrails/local-tickets.json`. If missing, stop: "No local tickets file found. Run `/specrails:auto-propose-backlog-specs` to generate ideas." - If `BACKLOG_PROVIDER=none`: stop: "No backlog provider configured. Run `/specrails:setup` to configure." Set `GH_AVAILABLE` based on whether gh auth succeeded. --- ## Execution Launch a **single** sr-product-analyst agent (`subagent_type: sr:product-analyst`) to read and prioritize the backlog. The product-analyst receives this prompt: > You are reading the product-driven backlog from the configured backlog provider (read from .specrails/backlog-config.json) and producing a prioritized view. 1. **Fetch all open product-driven backlog items:** If `BACKLOG_PROVIDER=github`: