backlog

Name: backlog
Availability: InStock
Author: MakerLabs

Manage Specflow backlog on GitHub Project #4 via CLI scripts.

Updated Apr 22, 2026

Search Tags:#automation #workflow #github #backlog #issue-tracking #project-management

Ready to run

npx skills add https://github.com/mkrlabs/specflow --skill backlog-mkrlabs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: backlog
Source: https://github.com/mkrlabs/specflow/tree/main/.claude/skills/backlog
Command: npx skills add https://github.com/mkrlabs/specflow --skill backlog-mkrlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, and includes scripts (resource) components.

What problem does it solve?

Manage Specflow's product backlog directly on GitHub Project #4, providing a single source of truth and removing the need for local markdown mirrors.

Core Features & Use Cases

List backlog items and their statuses on Project #4.
Add new backlog items as GitHub issues and attach them to the project.
Move items between Backlog, Ready, In progress, In review, and Done using governance via the Product Owner subagent.
Open issues for specific work items and track progress through the product lifecycle.
All mutations route through the Product Owner agent to ensure governance and auditability.

Quick Start

Run the backlog scripts to list, view, add, or move items on the Specflow GitHub Project #4.

Frequently Asked Questions about backlog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I manage a GitHub project backlog without keeping a local markdown mirror?▼

You can manage a GitHub project backlog directly using gh CLI wrappers to list, add, and move issues. This provides a single source of truth, removing the need for local markdown mirrors.

How do I move GitHub issues between Backlog, Ready, and In progress columns?▼

You can move GitHub issues between project columns by routing status mutations through a Product Owner agent. This governance ensures all backlog transitions are auditable and controlled.

Do I need the gh CLI installed to automate GitHub issue tracking?▼

Yes, you need the gh CLI installed to automate GitHub issue tracking and project management. The skill relies on gh CLI wrappers and jq to interact with GitHub Project boards and perform mutations.

What is the best way to add new issues to a specific GitHub Project board?▼

The best way to add new issues to a specific GitHub Project is through automated gh CLI scripts. These scripts create issues and attach them directly to the project backlog, ensuring proper tracking.

Can I use a Product Owner agent to control GitHub project workflows?▼

Yes, you can use a Product Owner agent to control GitHub project workflows. All backlog mutations route through this agent to ensure governance, auditability, and a structured product lifecycle.

Why does my GitHub backlog automation require jq alongside gh?▼

Your GitHub backlog automation requires jq to parse and manipulate JSON data returned by gh CLI commands. The gh wrapper scripts depend on jq to accurately reflect project state and process issue data.