docfactory-backlog

Generates a Phase 1 backlog document with 30–90 minute tasks and acceptance criteria.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/burakdirin/skills --skill docfactory-backlog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docfactory-backlog
Source: https://github.com/burakdirin/skills/tree/main/skills/docfactory-backlog
Command: npx skills add https://github.com/burakdirin/skills --skill docfactory-backlog

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill generates a structured backlog (06-backlog.md) that breaks work into 30–90 minute tasks for a solo developer, ensuring predictable delivery and clear success signals.

Core Features & Use Cases

  • Produces a Phase 1 backlog with 20+ tasks, each with acceptance criteria and verification steps.
  • Defines dependencies, phases, epics, and a critical path, aligned to 00-project-brief.md through 04-tech-architecture.md.
  • Includes a validation script and templates to support IDE agent execution.

Quick Start

Copy the docfactory-backlog/ directory into your agent's configured skills directory and run it after completing prerequisites to generate 06-backlog.md.

Frequently Asked Questions about docfactory-backlog

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

FAQPage Schema
How do I break down software engineering tasks into 30-90 minute backlog items?

Task slicing for a solo developer backlog involves decomposing project work into 30-90 minute items with clear acceptance criteria and verification steps. This task slicing approach ensures predictable delivery and clear success signals for solo development workflows.

How do I generate a project backlog with phases, epics, and a critical path?

Generating a project backlog with phases, epics, and a critical path requires relying on prior artifacts like the project brief and tech architecture. These artifacts define dependencies and structure the critical path suitable for solo development workflows.

Do I need a project brief and tech architecture before creating a Phase 1 backlog?

Yes, you need a project brief through a tech architecture document before creating a Phase 1 backlog. These prior artifacts provide the foundational context required to define phases, epics, dependencies, and the critical path for the backlog.

What is the best way to ensure my backlog tasks have clear verification steps?

The best way to ensure backlog tasks have clear verification steps is using a validation script with predefined templates. This enforces structure adherence, guaranteeing each 30-90 minute task includes explicit acceptance criteria and verification steps.

Can I use backlog templates for IDE agent execution in solo development?

Yes, you can use backlog templates for IDE agent execution in solo development. Copy the backlog directory into your agent's configured skills directory to generate structured backlog documents supporting consistent automated execution.

Why does my backlog validation fail when generating Phase 1 tasks?

Backlog validation fails when the generated structure does not adhere to the template format. Ensure your output references the correct templates and that all 30-90 minute tasks include explicit acceptance criteria and verification steps.