What is get-backlog-specs?

A command that displays a product backlog, which is a prioritized list of possible features and improvements, from the configured issue tracker.

Use it to show all backlog items or filter them by area. The backlog source is read from the project configuration.

It gives the team a view of product ideas already evaluated against user needs instead of requiring them to search the tracker manually.

get-backlog-specs — Skill for Claude Code by fjpulidop

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add fjpulidop/specrails-core --skill get-backlog-specs

Clone the repo

git clone --depth 1 https://github.com/fjpulidop/specrails-core

Made for: Claude Code.

Or install specrails, the plugin that ships this one along with the rest of its 28 skills, 14 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/fjpulidop/specrails-core/get-backlog-specs/github.svg)](https://agentmods.dev/skills/fjpulidop/specrails-core/get-backlog-specs)

Your own site

<a href="https://agentmods.dev/skills/fjpulidop/specrails-core/get-backlog-specs"><img src="https://agentmods.dev/badge/skills/fjpulidop/specrails-core/get-backlog-specs/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/fjpulidop/specrails-core/get-backlog-specs"><img src="https://agentmods.dev/badge/skills/fjpulidop/specrails-core/get-backlog-specs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,532 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00029	$0.02532
Opus 5	$0.00015	$0.01266
Sonnet 5	$0.00006	$0.00506
Haiku 4.5	$0.00003	$0.00253

Measured 8d ago against content hash 7c47d7c2593f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

get-backlog-specs scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

specrails-plugin/skills/get-backlog-specs/SKILL.md · 207 lines

How it starts

The opening of the file, as written. The whole thing — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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.

Fetch all open product-driven backlog items:

If BACKLOG_PROVIDER=github:
```
gh issue list --label "product-driven-backlog" --state open --json number,title,body,labels --limit 100
```
If BACKLOG_PROVIDER=local: read .specrails/local-tickets.json and extract the tickets array.
Parse each issue/ticket to extract metadata from the body:
- Area: from area:* label
- Persona Fit: from the body's Overview table — extract per-persona scores and total
- Effort: from the body's Overview table (High/Medium/Low)
- Description: from the body's "Feature Description" section
- User Story: from the body's "User Story" section

Read the full file on GitHub · 207 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

8d ago First seen · 207 lines · 29 tokens per session scan A 7c47d7c2593f

Subscribe to this mod's changes

get-backlog-specs is a skill published in the GitHub repository fjpulidop/specrails-core (9 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 2,532 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Claude Code Code Generation Project management ai-agents anthropic claude developer-tools

feature-dev

Guide a feature implementation through a structured seven-phase workflow with deep codebase understanding, clarifying questions, parallel architecture design, and quality review. Use this skill when the user asks to build a new feature, add functionality, or wants a methodical approach to implementation rather than…

waybarrios/opencode-power-pack · 62 tokens

memstack-business-client-onboarding

Use this skill when the user says 'client onboarding', 'new client', 'onboard client', 'kickoff meeting', 'intake form', 'welcome email', or needs welcome sequences, questionnaires, and setup checklists for new clients. Do NOT use for contracts or invoicing.

cwinvestments/memstack · 65 tokens

memstack-product-mvp-scoper

Use this skill when the user says 'MVP', 'minimum viable product', 'scope the MVP', 'what should I build first', 'strip to core', or needs to define the smallest build that validates a product hypothesis. Do NOT use for full PRDs or roadmap planning.

cwinvestments/memstack · 65 tokens

memstack-product-roadmap-builder

Use this skill when the user says 'roadmap', 'product roadmap', 'quarterly plan', 'now/next/later', 'OKRs', or needs strategic planning with themes, milestones, resource allocation, and stakeholder-ready views. Do NOT use for MVP scoping or sprint-level planning.

cwinvestments/memstack · 67 tokens

memstack-product-user-story-generator

Use this skill when the user says 'user stories', 'write stories', 'backlog', 'sprint planning', 'acceptance criteria', or needs prioritized stories with Given/When/Then criteria and story point estimates. Do NOT use for full PRDs or detailed feature specs.

cwinvestments/memstack · 64 tokens

memstack-marketing-marketplace-submit

Use when the user says 'submit to marketplace', 'publish my skill', 'share this skill', 'list on marketplace', 'submit plugin', 'publish to community', or needs to submit a skill or plugin to a community marketplace via PR. Do NOT use for building skills or writing plugin code.

cwinvestments/memstack · 68 tokens