# Backlog Feature Sweep

> Plan and implement a feature by first creating a detailed code-informed backlog, then processing it to completion. Use when the user wants an end-to-end feature sweep, from interview and task breakdown through implementation.

- Skill: `frnyb/backlog-feature-sweep` (Agent Skill)
- Install (CLI): `npx skillmds@latest add frnyb/backlog-feature-sweep`
- Raw SKILL.md: https://api.skillmd.com/api/skills/frnyb/backlog-feature-sweep/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: frnyb (https://skillmd.com/u/frnyb)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/frnyb/backlog-feature-sweep

---


# Backlog Feature Sweep

Run the complete feature workflow: create a backlog, verify it is ready for unattended implementation, then process that backlog until every task is complete.

## Workflow

1. Use the `create-backlog` workflow.
   - Interview the user one question at a time.
   - Inspect the codebase whenever the answer can be discovered locally.
   - Write or update `codex-backlogs/<feature-slug>.md`.
   - Decompose the converged design into detailed atomic tasks with acceptance criteria and tests.
   - Review the backlog against the agreed understanding and revise it before coding.
   - Finish all interviewing, clarification, verification, and backlog enrichment before implementation begins.

2. Use the `process-backlog` workflow on that backlog.
   - Verify the full backlog is detailed enough to implement unattended.
   - Move one task at a time from `Incomplete` to `In-Progress`.
   - Implement it fully, review the changes, run specified tests, and verify acceptance criteria.
   - Move it to `Completed` only when fully resolved.
   - Refresh the processing instructions before each task cycle.
   - Continue until both `Incomplete` and `In-Progress` are empty.

## Stop Conditions

A final response is allowed only when `Incomplete` and `In-Progress` are both empty, a blocker cannot be resolved from code, tests, docs, backlog, or reasonable engineering judgment, or the user explicitly says stop, pause, summarize only, or gives a new conflicting task.

Passing a subset of tests, finishing a phase, completing a long task chunk, context pressure, or reaching a useful checkpoint is not a stop condition. If work is extensive, continue across multiple tool cycles and use brief progress updates instead of final summaries.

## Operating Rules

- Keep the backlog document as the source of truth throughout the sweep.
- Maintain high implementation quality even during long runs.
- Do not skip unclear decisions; resolve them before coding through code inspection or one-at-a-time user questions.
- Once coding begins, do not return to the user for ordinary clarification; use the backlog, codebase, tests, and reasonable implementation judgment unless truly blocked.
- Do not stop after planning if implementation is feasible in the current workspace.