Loading...
Loading...
Capture explored work as a backlog item for future implementation. Use when you've explored an enhancement, alternative approach, or feature but decided to defer it. Creates comprehensive plan files in backlog/ directory with enough context for a future session to execute efficiently.
npx skill4agent add fairchild/dotclaude backlogbacklog/AGENTS.mdbacklog/{feature}-{category}.md---
status: pending
category: {plan|followup|task-list|ideas}
pr: null
branch: null
score: null
retro_summary: null
completed: null
---
# {Feature Name}
## Problem Statement
{1-2 paragraphs explaining why this work matters and what problem it solves}
## Key Decisions
| Decision | Choice | Rationale |
|----------|--------|-----------|
| {decision point} | {what we'd choose} | {why} |
## Architecture
{ASCII diagram if helpful}
## Implementation Phases
### Phase 1: {Name}
**Files to modify:**
- `path/to/file.ts` - {what changes}
**Files to create:**
- `path/to/new-file.ts` - {purpose}
**Acceptance criteria:**
- [ ] {testable outcome}
- [ ] {testable outcome}
### Phase 2: {Name}
...
## Verification Commands
```bash
# Commands to verify the implementation works
### Step 4: Include Research Artifacts
Incorporate what we learned during exploration:
- Code snippets we prototyped or found
- Configuration examples
- API patterns from existing code
- External documentation links
### Step 5: Commit
Commit the backlog file with message:
## Quality Checklist
Before finishing, verify the backlog file:
- [ ] Has enough context that a fresh session can understand without the original conversation
- [ ] Includes specific file paths (with line numbers when relevant)
- [ ] Has verification commands or acceptance criteria
- [ ] References related code patterns in the codebase
- [ ] Follows the frontmatter schema from `backlog/AGENTS.md`
## List Backlog Items
To see all backlog items, run:
```bash
~/.claude/skills/backlog/scripts/status.shdone/~/.claude/skills/backlog/scripts/groom.sh [path/to/backlog]references/grooming.mdUser: /backlog
Claude: I'll help capture the work we explored for future implementation.
What feature/enhancement are we deferring?
> R2 storage for docs assets
Why did we explore it?
> Docs screenshots are gitignored, wanted persistent storage without git bloat
Why are we deferring?
> Works fine locally for now, R2 adds complexity we don't need yet
What did we learn?
> R2 bindings in wrangler.jsonc, Worker route pattern, wrangler CLI for uploads
[Creates backlog/docs-r2-storage-plan.md with full implementation plan]references/agents-schema.mdreferences/agents-schema.mdreferences/grooming.mdreferences/README.md