backlog

Capture, view, promote, and remove backlog ideas with schema validation.

3|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/infraspecdev/tesseract --skill backlog-infraspecdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backlog
Source: https://github.com/infraspecdev/tesseract/tree/main/shield/skills/general/backlog
Command: npx skills add https://github.com/infraspecdev/tesseract --skill backlog-infraspecdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction of capturing, organizing, promoting, and removing project ideas across a shared Shield backlog, so teams can track work without losing context or creating duplicate records.

Core Features & Use Cases

It supports backlog capture during research, PRD, planning, and implementation, plus viewing and reconciling entries as work progresses. It is designed for managing feature-linked ideas, epic-based removal gates, and safe promotion or cleanup of backlog items in a structured engineering workflow. Use it when you need a durable idea inbox, a readable backlog view, or a controlled path from rough concept to removed or promoted work.

Quick Start

Use the backlog skill to capture this idea in the project backlog with the right feature and epic, or ask it to view, promote, or remove an existing entry.

Frequently Asked Questions about backlog

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

FAQPage Schema
How do I capture and organize project backlog ideas without losing context or creating duplicates?

To capture project backlog ideas without drift, use a centralized backlog system that enforces uuid4 entry IDs and schema validation. This ensures every idea is uniquely tracked, preventing duplicate records and preserving original context across research and planning phases.

Can I use a structured JSON schema to validate backlog entries in an engineering workflow?

Yes, using a structured JSON schema to validate backlog entries ensures data integrity across research, PRD, planning, and implementation phases. Enforcing uuid4 IDs and schema rules during capture prevents malformed records and maintains a clean project backlog.

How do I safely remove backlog entries without losing project history?

Safely removing backlog entries requires a system that enforces removal logging and epic-based removal gates. This approach captures the deletion context and validates dependencies, ensuring you can clean up the project backlog without losing historical visibility.

Does backlog capture work for both agent-side and human-driven engineering workflows?

Backlog capture supports both agent-side and human-driven engineering workflows within Shield-managed projects. It provides a durable idea inbox that accepts entries during research, PRD, planning, and implementation, ensuring consistent tracking regardless of the capture source.

When do I need reconciliation rules for managing a project backlog?

You need reconciliation rules for managing a project backlog when promoting or removing entries across complex engineering workflows. These rules enforce epic-linked validation and schema checks, preventing context drift and uncontrolled deletion of feature-linked ideas.