From solopreneur
Breaks large specs or features into prioritized, dependency-tracked tickets with MVP/P1/P2 phasing, dependency graphs, parallel groups, and generates backlog markdown files.
How this skill is triggered — by the user, by Claude, or both
Slash command
/solopreneur:backlog spec file pathspec file pathThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are creating a prioritized backlog for the CEO. Determine the mode based on `$ARGUMENTS`:
You are creating a prioritized backlog for the CEO. Determine the mode based on $ARGUMENTS:
.solopreneur/specs/...) or design directory (.solopreneur/designs/...), read it for context → Full Breakdown modeRead the spec file (and design directory if referenced). Understand:
Delegate to subagents in parallel:
@engineer: Break requirements into implementable tickets. For each ticket: title, description, acceptance criteria, technical notes, complexity estimate (S/M/L), and dependencies on other tickets. Flag technical risks.@designer: Identify which tickets need design work (type: eng+design or design). Flag UX dependencies between tickets (e.g., "dashboard needs auth to be built first for the logged-in state").Present the ticket breakdown to the CEO for approval:
Wait for CEO approval before creating files.
On CEO approval, create the backlog directory and files:
Directory: .solopreneur/backlog/{date}-{slug}/
backlog.md — The board view with all tickets, statuses, dependency graph, and parallel groups. Format:
# Backlog: {Feature Name}
## Source
Spec: `.solopreneur/specs/{spec-file}`
Design: `.solopreneur/designs/{design-dir}/` (if exists)
## MVP
| ID | Title | Status | Depends On | Type | Size |
|----|-------|--------|------------|------|------|
| MVP-001 | ... | pending | — | eng | M |
## P1
| ID | Title | Status | Depends On | Type | Size |
|----|-------|--------|------------|------|------|
## P2
| ID | Title | Status | Depends On | Type | Size |
|----|-------|--------|------------|------|------|
## Dependency Graph
(ASCII diagram showing ticket dependencies)
## Parallel Groups
(List tickets that can be built simultaneously)
{ID}.md — One file per ticket with YAML frontmatter and markdown body:
---
id: MVP-001
title: Short descriptive title
priority: MVP
type: eng
status: pending
depends_on: []
blocks: [MVP-002]
design_ref:
branch:
worktree:
---
## Description
What this ticket implements and why.
## Acceptance Criteria
- [ ] Criterion 1
- [ ] Criterion 2
## Technical Notes
(From @engineer: stack choices, approach, risks)
## Files
(Populated during build)
Suggest the appropriate next action based on the backlog:
design):
-> Next: Design the MVP screens:
/solopreneur:design .solopreneur/backlog/{dir}/backlog.md
eng type, or designs already exist):
-> Next: Start building the first ticket:
/solopreneur:build .solopreneur/backlog/{dir}/MVP-001.md
Tickets that can be built in parallel: MVP-001, MVP-003
If $ARGUMENTS doesn't reference a spec or design file, treat it as a standalone task:
Check if an existing backlog directory exists in .solopreneur/backlog/. If so, add the ticket to that backlog (with the next available ID). If not, create a new backlog directory.
Create a single ticket file with:
Update backlog.md to include the new ticket.
Suggest building it:
-> Next: Build this ticket:
/solopreneur:build .solopreneur/backlog/{dir}/{ID}.md
npx claudepluginhub pcatattacks/solopreneur-pluginBreaks down a plan, spec, or conversation into tracer-bullet tickets with explicit blocking dependencies, published to a configured issue tracker. Useful for structuring work into vertical slices.
Breaks plans, specs, or conversations into vertical-slice tracer-bullet tickets with blocking edges, saved to .plan/. Useful for structuring work during implementation.
Creates and maintains product/project backlogs with prioritization, acceptance criteria, and estimates. Supports user stories, MoSCoW, grooming, and tracking.