backlog-md — Skillopedia

Backlog.md Task Tracking for Agents Task tracking system optimized for agent workflows via Backlog.md CLI. Three Primary Use Cases 1. Implementer: Deferring Issues During Feature Work File P2-P4 issues discovered during implementation. Use label for deferred review findings. - Create with plan : You have implementation context at filing time - Assign priority : See priority guide - Add type label (required) + app labels (optional) 2. Reviewer: Audit Findings Create structured issues from security/audit reviews. Link dependencies and assign to milestones. - Create with plan : You're creating f…

Line1\\nLine2\\n\\nFinal'\nbacklog task edit 42 --plan

Important: agents should read /llm.txt, /llms.txt, or /.well-known/skills.json to discover the public Skillopedia API.

1. A\\n2. B'\nbacklog task edit 42 --notes

Important: agents should read /llm.txt, /llms.txt, or /.well-known/skills.json to discover the public Skillopedia API.

Done A\\nDoing B'\nbacklog task edit 42 --append-notes

Important: agents should read /llm.txt, /llms.txt, or /.well-known/skills.json to discover the public Skillopedia API.

Progress update line 1\\nLine 2'\nbacklog task edit 42 --final-summary

Important: agents should read /llm.txt, /llms.txt, or /.well-known/skills.json to discover the public Skillopedia API.

Shipped A\\nAdded B'\nbacklog task edit 42 --append-final-summary

Important: agents should read /llm.txt, /llms.txt, or /.well-known/skills.json to discover the public Skillopedia API.

Added X\\nAdded Y'\n```\n\n### POSIX portable (printf)\n\n```bash\nbacklog task edit 42 --notes \"$(printf 'Line1\\nLine2')\"\n```\n\n### PowerShell (backtick n)\n\n```powershell\nbacklog task edit 42 --notes \"Line1`nLine2\"\n```\n\n**Note**: `\"...\\n...\"` with regular double quotes passes the literal backslash + n — it does not create a newline.\n\n## Implementation Notes Formatting\n\n- Keep notes concise and time-ordered: progress, decisions, blockers\n- Use short paragraphs or bullet lists\n- Use Markdown bullets (`-` unordered, `1.` ordered)\n- Include explicit newlines in `--append-notes`:\n\n```bash\nbacklog task edit 42 --append-notes

Important: agents should read /llm.txt, /llms.txt, or /.well-known/skills.json to discover the public Skillopedia API.

- Added new API endpoint\\n- Updated tests\\n- TODO: monitor staging deploy'\n```\n\n## Final Summary Formatting\n\nTreat the Final Summary as a PR description. Cover:\n- **What changed** and **why**\n- **User impact**\n- **Tests run**\n- **Risks/follow-ups** when relevant\n\nExample:\n\n```\nAdded Final Summary support across CLI/MCP/Web/TUI to separate PR summaries from progress notes.\n\nChanges:\n- Added `finalSummary` to task types and markdown section parsing/serialization.\n- CLI/MCP/Web/TUI now render and edit Final Summary; plain output includes it.\n\nTests:\n- bun test src/test/final-summary.test.ts\n- bun test src/test/cli-final-summary.test.ts\n```\n\nAvoid single-line summaries unless the change is truly tiny.\n","content_type":"text/markdown; charset=utf-8","language":"markdown","size":7908,"content_sha256":"d34ecd8dbffc364a0cfcb814d4f51bc8f4459944b7976cafe00fbfe7313acfa5"},{"filename":"references/issue-creation-guide.md","content":"# Issue Creation Patterns\n\nThree distinct scenarios with different requirements. Required field: **type label + priority**.\n\n## Scenario 1: Deferred Issues During Feature Implementation\n\n**When:** You're implementing a feature and discover a bug, edge case, or tech debt.\n**How:** File immediately with implementation plan (you have context now).\n**Plan rule:** ✅ INCLUDE detailed plan — you'll likely fix it.\n\n### Example Workflow\n\nDuring implementation, you find that error handling is incomplete:\n\n```bash\nbacklog task create \"Handle null reference in payment processor\" \\\n -d \"During PaymentService refactor, found case where null processor reference isn't handled, could cause runtime error in production\" \\\n -l bug,remediation \\\n -l synapse-pingora \\\n -p 2 \\\n --ac \"Service returns meaningful error when processor is null\" \\\n --ac \"Edge case handled in existing tests\" \\\n --plan \"1. Add null check before processor call\\n2. Add test for null case\\n3. Verify with existing integration tests\"\n```\n\n### Field Checklist\n\n- ✅ **Title**: Clear, specific (not \"Fix bugs\")\n- ✅ **Description**: What you found and why it matters\n- ✅ **Type label**: `remediation` (for deferred review issues)\n- ✅ **App label(s)**: What app(s) this affects\n- ✅ **Priority**: Use your judgment (most are P2)\n- ✅ **Acceptance Criteria**: What \"done\" means\n- ✅ **Implementation Plan**: Steps to fix it\n\n## Scenario 2: Reporting Found Issues (No Plan)\n\n**When:** You discover an issue but won't be implementing it immediately.\n**How:** File without plan (let the assignee plan it).\n**Plan rule:** ❌ DO NOT include plan — implementer will add it.\n\n### Example Workflow\n\nYou find a security issue but it's not your responsibility to fix:\n\n```bash\nbacklog task create \"Potential XSS vulnerability in user input sanitization\" \\\n -d \"Found unsanitized user input accepted in comment field. Could allow XSS if user provides HTML/script tags.\" \\\n -l bug \\\n -l signal-horizon-ui,signal-horizon-api \\\n -p 1 \\\n --ac \"All user inputs sanitized before rendering\" \\\n --ac \"XSS test coverage added\"\n```\n\n**No plan**, no implementation details. Implementer adds plan when they claim it.\n\n### Field Checklist\n\n- ✅ **Title**: Clear, specific\n- ✅ **Description**: What's broken, why it matters\n- ✅ **Type label**: bug|feature|documentation|refactor\n- ✅ **App label(s)**: What affects this\n- ✅ **Priority**: P0|P1|P2, use `priority-review` label if unsure\n- ✅ **Acceptance Criteria**: Success conditions\n- ❌ **NO Implementation Plan**: Leave this for implementer\n\n## Scenario 3: Audit Findings (Structured)\n\n**When:** Reviewer is doing security audit or code quality review.\n**How:** Create issues with dependencies and milestones.\n**Plan rule:** ✅ INCLUDE plan — you have audit context.\n\n### Example Workflow\n\nSecurity audit finds three related issues:\n\n```bash\n# Issue 1: Core vulnerability\nbacklog task create \"Remove hardcoded API credentials from environment configs\" \\\n -d \"Security audit found hardcoded credentials in .env.example and config files. Violates OWASP A02:2021. Must use environment variables.\" \\\n -l bug,remediation \\\n -l synapse-pingora,signal-horizon-api \\\n -p 1 \\\n --ac \"No hardcoded secrets in any config files\" \\\n --ac \"All secrets loaded from env variables\" \\\n --plan \"1. Scan codebase for hardcoded credentials\\n2. Update config to use env vars\\n3. Update docs for setup\\n4. Run security linter\"\n\n# Issue 2: Depends on issue 1\nbacklog task create \"Update deployment docs for credential handling\" \\\n -d \"Related to credential hardcoding fix. Document new env var requirements.\" \\\n -l documentation,remediation \\\n -l synapse-pingora,signal-horizon-api \\\n -p 2 \\\n --ac \"Deployment guide includes env var setup\" \\\n --ac \"Example .env.example provided\"\n\n# Issue 3: Different finding\nbacklog task create \"Upgrade deprecated crypto library\" \\\n -d \"Audit found crypto-js version 4.1.0 is vulnerable (CVE-2023-xyz). Upgrade to 4.1.5+.\" \\\n -l bug,remediation \\\n -l signal-horizon-api \\\n -p 1 \\\n --ac \"Crypto-js updated to 4.1.5 or higher\" \\\n --ac \"All crypto calls still functional after upgrade\"\n```\n\n### With Dependencies and Milestones\n\nAfter creating issues, link them:\n\n```bash\n# Link issue 2 to depend on issue 1\nbacklog task edit \u003cissue-2-id> --dep \u003cissue-1-id>\n\n# Assign to milestone if needed\nbacklog task edit \u003cissue-1-id> --milestone \"Security Hardening Q1\"\n```\n\n### Field Checklist\n\n- ✅ **Title**: Clear, specific\n- ✅ **Description**: What audit found, why it matters, any standards violated\n- ✅ **Type label**: bug|remediation (usually for audit findings)\n- ✅ **App label(s)**: What affects this\n- ✅ **Priority**: Based on severity (security = usually P0/P1)\n- ✅ **Acceptance Criteria**: How to verify fix\n- ✅ **Implementation Plan**: Steps to remediate\n- ✅ **Dependencies** (if applicable): Link related issues\n- ✅ **Milestone** (if applicable): Assign to release cycle\n\n## Scenario 4: Explicitly Asked to Plan Work\n\n**When:** User says \"Plan out this work\" or \"Create a task and plan how you'd do it\".\n**How:** Create with detailed, step-by-step implementation plan.\n**Plan rule:** ✅ INCLUDE detailed plan — requirement, not deferral.\n\n### Example Workflow\n\nUser asks you to plan a feature:\n\n```bash\nbacklog task create \"Implement real-time notifications for order status\" \\\n -d \"Add real-time push notifications when order status changes. Users should receive browser notifications and see update in dashboard within 2 seconds.\" \\\n -l feature \\\n -l signal-horizon-ui,signal-horizon-api \\\n -p 2 \\\n --ac \"Browser push notification sent on status change\" \\\n --ac \"Dashboard updates in real-time (\u003c 2s latency)\" \\\n --ac \"Works offline gracefully (queues until reconnect)\" \\\n --ac \"E2E test coverage for notification flow\" \\\n --plan \"1. Design notification schema and API contract\\n2. Implement backend status change webhook\\n3. Add notification queue service\\n4. Implement browser notification handler\\n5. Add dashboard real-time sync via WebSocket\\n6. Write integration tests\\n7. Performance test latency requirements\"\n```\n\n### Detailed Plan Guidelines\n\n- **Be thorough**: Break down major steps\n- **Include research**: If uncertain about approach, include \"1. Research X options\"\n- **Include tests**: Add test/validation steps\n- **Include doc**: Add \"Update docs\" if applicable\n- **Phase-based**: Can organize by layer (backend/frontend) or workflow phase\n\n## Decision Tree: Which Scenario?\n\n```\nAre you implementing a feature?\n ├─ Yes, found a bug/tech debt → Scenario 1 (defer with plan)\n └─ No, just reporting it → Scenario 2 (report no plan)\n\nAre you reviewing/auditing?\n └─ Yes → Scenario 3 (audit with plan + dependencies)\n\nDid user explicitly ask for a plan?\n └─ Yes → Scenario 4 (plan as required)\n```\n\n## Common Mistakes\n\n| Mistake | Problem | Fix |\n|---------|---------|-----|\n| Reporting without type label | Issue won't be categorized properly | Always add type label (bug, feature, etc.) |\n| Adding plan when reporting | Constrains implementer's approach | Only add plan for scenarios 1, 3, 4 |\n| Using wrong remediation | `remediation` is for deferred review issues only | Don't use for new feature ideas |\n| Missing priority | Can't be triaged | Always set P0-P4 (or priority-review) |\n| Vague description | Implementer doesn't understand context | Include \"why\" and \"what\" clearly |\n| Too detailed AC | Implementer interprets as implementation steps | Frame as outcomes, not methods |\n\n## Acceptance Criteria Quality\n\nGood (outcome-focused):\n- \"API returns 200 with correct schema\"\n- \"User sees success message after form submission\"\n- \"Response time \u003c 100ms for 1000 records\"\n\nBad (implementation-focused):\n- \"Add validateInput() function\"\n- \"Use Promise.all() for parallel requests\"\n- \"Refactor to strategy pattern\"\n\nAC should be testable, not prescriptive.\n","content_type":"text/markdown; charset=utf-8","language":"markdown","size":7895,"content_sha256":"d7933ccaca725bb409fd663c37037209a9b73994f4b450996d446b6646033ed2"},{"filename":"references/priority-labels.md","content":"# Priority and Labeling System\n\nAgent-optimized priority and labeling system for Backlog.md.\n\n## Priority Levels\n\n**Required** when creating issues. Use the following definitions:\n\n| Priority | Definition | Examples | Typical Workflow |\n|----------|-----------|----------|------------------|\n| **P0** | Critical problems, major breakage | Service down, security vulnerability, data loss | Fix immediately |\n| **P1** | Legitimate bugs impacting users | Feature broken, incorrect behavior, significant performance degradation | Fix in current cycle |\n| **P2** | Bugs, edge cases | Unusual input handling, minor UX issues, performance improvements | Schedule in sprint |\n| **P3** | Nice-to-have improvements, features we want to do | Convenience features, refactoring, code cleanup we plan for | Include in roadmap |\n| **P4** | Backlog, future ideas | Speculative features, long-term improvements | Archive until needed |\n\n## Priority Assignment Strategy\n\n**For implementers filing deferred issues during feature work:**\n- Most deferred issues are **P2** (bugs/edge cases found during implementation)\n- File P2 by default unless clearly critical (P0/P1)\n- If unsure between P2/P3: **use P2** (we want to fix it)\n- If unsure about P0/P1: Label with `priority-review` instead of guessing\n\n**For reviewers doing audits:**\n- Security findings: Likely P0/P1\n- Code quality issues: P2/P3\n- If unsure: Label with `priority-review` and let user decide later\n\n**Don't overthink it.** The priority-review label exists for borderline cases.\n\n## Labeling System\n\n### Type Labels (Required)\n\n**Single label per issue. Choose one:**\n\n| Label | Use For |\n|-------|---------|\n| `bug` | Bug fixes, defects, incorrect behavior |\n| `feature` | New functionality, feature requests |\n| `documentation` | Docs, guides, API documentation, comments |\n| `refactor` | Code cleanup, architecture improvements, no behavior change |\n| `remediation` | Deferred issues from reviews/audits (mark issues found during review) |\n\n### App Labels (Optional)\n\nCan use **multiple** app labels per issue. Examples:\n- `synapse-pingora`\n- `signal-horizon-ui`\n- `signal-horizon-api`\n- Others as needed\n\n### Custom Labels (Optional)\n\nAgents can add domain-specific labels for routing:\n- `performance` — performance improvement or investigation\n- `security` — security-related work\n- `priority-review` — priority uncertain, needs user decision\n- `blocked` — waiting on something external\n- Others as useful for agent workflows\n\n## Labeling Examples\n\n**Deferred bug found during code review:**\n```bash\nbacklog task create \"Handle null reference in payment processor\" \\\n -l bug,remediation \\\n -l synapse-pingora \\\n -p 2\n```\n\n**Security audit finding:**\n```bash\nbacklog task create \"Remove hardcoded credentials from config\" \\\n -l bug,remediation \\\n -l synapse-pingora,signal-horizon-api \\\n -p 1 \\\n -l priority-review # If you're unsure about P0 vs P1\n```\n\n**Feature work UI component:**\n```bash\nbacklog task create \"Add dark mode toggle to dashboard\" \\\n -l feature \\\n -l signal-horizon-ui \\\n -p 3\n```\n\n**Documentation for monitoring:**\n```bash\nbacklog task create \"Document monitoring setup for sidecars\" \\\n -l documentation \\\n -p 3\n```\n\n## When to Use priority-review Label\n\nIf you're filing an issue and the priority is unclear, **add the `priority-review` label instead of guessing:**\n\n```bash\nbacklog task create \"Investigate intermittent timeout in batch processor\" \\\n -l bug \\\n -l synapse-pingora \\\n -p 2 \\\n -l priority-review # You think it's P2 but might be P1 if it's affecting production\n```\n\nThe user can review these later and adjust priority as needed.\n\n## Frequency and Patterns\n\nBased on typical workflows:\n- **P0/P1 issues**: Usually assigned during code review or when critical bugs surface\n- **P2 issues**: Most common during feature implementation (deferred work)\n- **P3/P4 issues**: Less common in review cycles, more from long-term planning\n- **priority-review**: Use liberally when uncertain\n","content_type":"text/markdown; charset=utf-8","language":"markdown","size":3990,"content_sha256":"055d681a0fca80547ae5c17d41d9f53ebf9ba7235d26c3aeabc65ed68e29d24e"},{"filename":"references/task-workflow.md","content":"# Task Execution Workflow\n\nHow to work assigned tasks systematically from start to completion.\n\n## Step 1: Claim the Task\n\nSet the task to \"In Progress\" and assign to yourself:\n\n```bash\nbacklog task edit 42 -s \"In Progress\" -a @myself\n```\n\n## Step 2: Read Everything\n\nView the complete task:\n\n```bash\nbacklog task 42 --plain\n```\n\n**Read ALL fields:**\n- **Title**: What is this task?\n- **Description**: Why does this exist? What's the goal?\n- **Acceptance Criteria**: What defines \"done\"? (numbered list)\n- **Definition of Done**: Additional checklist items (tests, docs, etc.)\n- **References**: File paths or URLs relevant to implementation\n- **Documentation**: Links to design docs, specs, related materials\n\n**Open any attached files/URLs** to understand context. You have access to parent directories and can fetch permitted files.\n\n## Step 3: Understand the Implementation Plan\n\nIf an implementation plan exists, review it. It was created with context about how to approach the work.\n\nIf creating a plan (new work, not deferred), create one now:\n\n```bash\nbacklog task edit 42 --plan \"1. Research approach\\n2. Analyze codebase\\n3. Implement\\n4. Test\"\n```\n\n**Share plan with user and wait for approval before writing code.**\n\n## Step 4: Implement Systematically\n\nWork through acceptance criteria in order. After completing each:\n\n```bash\nbacklog task edit 42 --check-ac 1 # Mark AC #1 complete\n# implement more...\nbacklog task edit 42 --check-ac 2 # Mark AC #2 complete\n```\n\n**Record your progress progressively:**\n\n```bash\nbacklog task edit 42 --append-notes \"Completed AC #1: basic functionality working\"\nbacklog task edit 42 --append-notes \"Fixed edge case in AC #2\"\n```\n\n## Step 5: Write Final Summary\n\nWhen implementation complete, write PR-quality summary:\n\n```bash\nbacklog task edit 42 --final-summary \"Implemented feature X with strategy pattern for extensibility. Added 5 new tests covering edge cases. Files: src/parser.ts, src/strategies/. No breaking changes.\"\n```\n\nQuality bar: Write as if reviewer will read it. Include what changed, why, scope, and tests.\n\n## Step 6: Complete Definition of Done\n\nCheck all Definition of Done items:\n\n```bash\nbacklog task edit 42 --check-dod 1\nbacklog task edit 42 --check-dod 2\n```\n\nEnsure:\n- ✅ Tests pass (run locally)\n- ✅ Linting clean\n- ✅ Documentation updated if needed\n- ✅ No regressions\n\n## Step 7: Mark Complete\n\n```bash\nbacklog task edit 42 -s Done\n```\n\n## Definition of Done Checklist\n\nTask is truly complete only when ALL are satisfied:\n\n- [ ] All acceptance criteria checked (visible in task)\n- [ ] All definition of done items checked (visible in task)\n- [ ] Final summary written (PR-quality)\n- [ ] Status set to \"Done\"\n- [ ] Tests pass locally\n- [ ] Code self-reviewed\n- [ ] No regressions introduced\n- [ ] Related documentation updated\n\n## Understanding Task Fields\n\n| Field | Meaning | How to Use |\n|-------|---------|-----------|\n| **Description** | Why this task exists, the goal/context | Read to understand purpose |\n| **Acceptance Criteria** | Numbered list of success conditions | Follow each one systematically |\n| **Definition of Done** | Quality/process checklist | Check items off as complete |\n| **Implementation Plan** | How to approach the work | Follow steps (or create if new) |\n| **References** | File paths, URLs, related resources | Open and read as needed |\n| **Documentation** | Links to design/spec docs | Review to understand requirements |\n| **Implementation Notes** | Your progress log | Append as you make progress |\n| **Final Summary** | PR description for reviewers | Write when implementation done |\n\n## Common Patterns\n\n### When Task Has No Implementation Plan\n\nCreate one before starting code:\n```bash\nbacklog task edit 42 --plan \"1. Research dependencies\\n2. Design approach\\n3. Implement\\n4. Test and verify\"\nbacklog task edit 42 --append-notes \"Plan created and shared with user for approval\"\n```\n\n### When You Get Blocked\n\nDon't mark task done. Instead:\n1. Document the blocker in notes: `backlog task edit 42 --append-notes \"Blocked on: XYZ service unavailable\"`\n2. Leave task in \"In Progress\"\n3. Notify user of blocker\n\n### When Scope Expands\n\nDon't add scope silently. Instead:\n1. Update AC first: `backlog task edit 42 --ac \"New requirement\"`\n2. Or create follow-up task: `backlog task create \"Follow-up: New feature\"`\n3. Don't exceed original AC without discussion\n\n### When AC Is Ambiguous\n\nRead References and Documentation carefully. If still unclear:\n- Append notes: `backlog task edit 42 --append-notes \"AC #2 ambiguous—clarifying with user\"`\n- Pause implementation\n- Notify user\n","content_type":"text/markdown; charset=utf-8","language":"markdown","size":4607,"content_sha256":"0faa6b328477d76200d51712a7593dcca9772604a8a8f55876337bbd65ca572d"}],"content_json":{"type":"doc","content":[{"type":"heading","attrs":{"level":1},"content":[{"text":"Backlog.md Task Tracking for Agents","type":"text"}]},{"type":"paragraph","content":[{"text":"Task tracking system optimized for agent workflows via Backlog.md CLI.","type":"text"}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"Three Primary Use Cases","type":"text"}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"1. Implementer: Deferring Issues During Feature Work","type":"text"}]},{"type":"paragraph","content":[{"text":"File P2-P4 issues discovered during implementation. Use label ","type":"text"},{"text":"remediation","type":"text","marks":[{"type":"code_inline"}]},{"text":" for deferred review findings.","type":"text"}]},{"type":"bullet_list","content":[{"type":"list_item","content":[{"type":"paragraph","content":[{"text":"Create with plan","type":"text","marks":[{"type":"strong"}]},{"text":": You have implementation context at filing time","type":"text"}]}]},{"type":"list_item","content":[{"type":"paragraph","content":[{"text":"Assign priority","type":"text","marks":[{"type":"strong"}]},{"text":": See priority guide","type":"text"}]}]},{"type":"list_item","content":[{"type":"paragraph","content":[{"text":"Add type label","type":"text","marks":[{"type":"strong"}]},{"text":" (required) + ","type":"text"},{"text":"app labels","type":"text","marks":[{"type":"strong"}]},{"text":" (optional)","type":"text"}]}]}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"2. Reviewer: Audit Findings","type":"text"}]},{"type":"paragraph","content":[{"text":"Create structured issues from security/audit reviews. Link dependencies and assign to milestones.","type":"text"}]},{"type":"bullet_list","content":[{"type":"list_item","content":[{"type":"paragraph","content":[{"text":"Create with plan","type":"text","marks":[{"type":"strong"}]},{"text":": You're creating from audit context","type":"text"}]}]},{"type":"list_item","content":[{"type":"paragraph","content":[{"text":"Link dependencies","type":"text","marks":[{"type":"strong"}]},{"text":" as needed","type":"text"}]}]},{"type":"list_item","content":[{"type":"paragraph","content":[{"text":"Assign priority","type":"text","marks":[{"type":"strong"}]},{"text":": Ask user if uncertain (label ","type":"text"},{"text":"priority-review","type":"text","marks":[{"type":"code_inline"}]},{"text":")","type":"text"}]}]},{"type":"list_item","content":[{"type":"paragraph","content":[{"text":"Set milestones","type":"text","marks":[{"type":"strong"}]}]}]}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"3. Worker: Executing Assigned Tasks","type":"text"}]},{"type":"paragraph","content":[{"text":"Read task fully, understand all fields, follow acceptance criteria and definition of done.","type":"text"}]},{"type":"bullet_list","content":[{"type":"list_item","content":[{"type":"paragraph","content":[{"text":"Claim task","type":"text","marks":[{"type":"strong"}]},{"text":": ","type":"text"},{"text":"backlog task edit 42 -s \"In Progress\" -a @myself","type":"text","marks":[{"type":"code_inline"}]}]}]},{"type":"list_item","content":[{"type":"paragraph","content":[{"text":"Read everything","type":"text","marks":[{"type":"strong"}]},{"text":": All fields, attached files/URLs, linked documentation","type":"text"}]}]},{"type":"list_item","content":[{"type":"paragraph","content":[{"text":"Complete systematically","type":"text","marks":[{"type":"strong"}]},{"text":": AC → Implementation Notes → Final Summary → DoD → Done","type":"text"}]}]}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"Absolute Rules","type":"text"}]},{"type":"ordered_list","attrs":{"order":1,"listStyle":"number"},"content":[{"type":"list_item","content":[{"type":"paragraph","content":[{"text":"CLI only for writes","type":"text","marks":[{"type":"strong"}]},{"text":". ","type":"text"},{"text":"backlog task edit","type":"text","marks":[{"type":"code_inline"}]},{"text":" and ","type":"text"},{"text":"backlog task create","type":"text","marks":[{"type":"code_inline"}]},{"text":" only. Never edit files directly.","type":"text"}]}]},{"type":"list_item","content":[{"type":"paragraph","content":[{"text":"Always use ","type":"text","marks":[{"type":"strong"}]},{"text":"--plain","type":"text","marks":[{"type":"code_inline"},{"type":"strong"}]},{"text":" flag","type":"text","marks":[{"type":"strong"}]},{"text":" when reading: ","type":"text"},{"text":"backlog task 42 --plain","type":"text","marks":[{"type":"code_inline"}]},{"text":", ","type":"text"},{"text":"backlog task list --plain","type":"text","marks":[{"type":"code_inline"}]}]}]},{"type":"list_item","content":[{"type":"paragraph","content":[{"text":"Type label required","type":"text","marks":[{"type":"strong"}]},{"text":" (bug|feature|documentation|refactor|remediation), single value only","type":"text"}]}]},{"type":"list_item","content":[{"type":"paragraph","content":[{"text":"App labels optional","type":"text","marks":[{"type":"strong"}]},{"text":", can be multiple: synapse-pingora, signal-horizon-ui, signal-horizon-api, etc.","type":"text"}]}]},{"type":"list_item","content":[{"type":"paragraph","content":[{"text":"Custom labels allowed","type":"text","marks":[{"type":"strong"}]},{"text":" as agent-useful (priority-review, performance, security, etc.)","type":"text"}]}]}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"Implementation Plans: When Required","type":"text"}]},{"type":"table","attrs":{"layout":null},"content":[{"type":"tr","content":[{"type":"th","attrs":{"colspan":1,"rowspan":1,"colwidth":null,"alignment":""},"content":[{"type":"paragraph","content":[{"text":"Scenario","type":"text"}]}]},{"type":"th","attrs":{"colspan":1,"rowspan":1,"colwidth":null,"alignment":""},"content":[{"type":"paragraph","content":[{"text":"Include Plan?","type":"text"}]}]},{"type":"th","attrs":{"colspan":1,"rowspan":1,"colwidth":null,"alignment":""},"content":[{"type":"paragraph","content":[{"text":"Reason","type":"text"}]}]}]},{"type":"tr","content":[{"type":"td","attrs":{"colspan":1,"rowspan":1,"colwidth":null,"alignment":""},"content":[{"type":"paragraph","content":[{"text":"Deferred review issues","type":"text"}]}]},{"type":"td","attrs":{"colspan":1,"rowspan":1,"colwidth":null,"alignment":""},"content":[{"type":"paragraph","content":[{"text":"✅ YES","type":"text"}]}]},{"type":"td","attrs":{"colspan":1,"rowspan":1,"colwidth":null,"alignment":""},"content":[{"type":"paragraph","content":[{"text":"You have audit/review context now","type":"text"}]}]}]},{"type":"tr","content":[{"type":"td","attrs":{"colspan":1,"rowspan":1,"colwidth":null,"alignment":""},"content":[{"type":"paragraph","content":[{"text":"Reporting found issues","type":"text"}]}]},{"type":"td","attrs":{"colspan":1,"rowspan":1,"colwidth":null,"alignment":""},"content":[{"type":"paragraph","content":[{"text":"❌ NO","type":"text"}]}]},{"type":"td","attrs":{"colspan":1,"rowspan":1,"colwidth":null,"alignment":""},"content":[{"type":"paragraph","content":[{"text":"Implementer will plan when they work it","type":"text"}]}]}]},{"type":"tr","content":[{"type":"td","attrs":{"colspan":1,"rowspan":1,"colwidth":null,"alignment":""},"content":[{"type":"paragraph","content":[{"text":"Explicitly asked to plan work","type":"text"}]}]},{"type":"td","attrs":{"colspan":1,"rowspan":1,"colwidth":null,"alignment":""},"content":[{"type":"paragraph","content":[{"text":"✅ YES (detailed)","type":"text"}]}]},{"type":"td","attrs":{"colspan":1,"rowspan":1,"colwidth":null,"alignment":""},"content":[{"type":"paragraph","content":[{"text":"Required per instruction","type":"text"}]}]}]},{"type":"tr","content":[{"type":"td","attrs":{"colspan":1,"rowspan":1,"colwidth":null,"alignment":""},"content":[{"type":"paragraph","content":[{"text":"Regular task work","type":"text"}]}]},{"type":"td","attrs":{"colspan":1,"rowspan":1,"colwidth":null,"alignment":""},"content":[{"type":"paragraph","content":[{"text":"After claiming, before coding","type":"text"}]}]},{"type":"td","attrs":{"colspan":1,"rowspan":1,"colwidth":null,"alignment":""},"content":[{"type":"paragraph","content":[{"text":"Don't add at creation, add after starting","type":"text"}]}]}]}]},{"type":"paragraph","content":[{"text":"Never update an existing plan unless explicitly instructed.","type":"text","marks":[{"type":"strong"}]}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"Priority System (See references/priority-labels.md for details)","type":"text"}]},{"type":"bullet_list","content":[{"type":"list_item","content":[{"type":"paragraph","content":[{"text":"P0","type":"text","marks":[{"type":"strong"}]},{"text":": Critical problems, major breakage","type":"text"}]}]},{"type":"list_item","content":[{"type":"paragraph","content":[{"text":"P1","type":"text","marks":[{"type":"strong"}]},{"text":": Legitimate bugs impacting users","type":"text"}]}]},{"type":"list_item","content":[{"type":"paragraph","content":[{"text":"P2","type":"text","marks":[{"type":"strong"}]},{"text":": Bugs, edge cases","type":"text"}]}]},{"type":"list_item","content":[{"type":"paragraph","content":[{"text":"P3","type":"text","marks":[{"type":"strong"}]},{"text":": Nice-to-have improvements, features we want","type":"text"}]}]},{"type":"list_item","content":[{"type":"paragraph","content":[{"text":"P4","type":"text","marks":[{"type":"strong"}]},{"text":": Backlog, future ideas","type":"text"}]}]}]},{"type":"paragraph","content":[{"text":"Unsure about P0-P1? Label with ","type":"text"},{"text":"priority-review","type":"text","marks":[{"type":"code_inline"}]},{"text":" and let user decide.","type":"text"}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"Task Completion Checklist","type":"text"}]},{"type":"ordered_list","attrs":{"order":1,"listStyle":"number"},"content":[{"type":"list_item","content":[{"type":"paragraph","content":[{"text":"Status: \"In Progress\" + assign self","type":"text"}]}]},{"type":"list_item","content":[{"type":"paragraph","content":[{"text":"Read: All fields, attached documentation","type":"text"}]}]},{"type":"list_item","content":[{"type":"paragraph","content":[{"text":"Plan: Add implementation plan (if not deferred from review)","type":"text"}]}]},{"type":"list_item","content":[{"type":"paragraph","content":[{"text":"Work: Code implementation, mark AC as you complete each","type":"text"}]}]},{"type":"list_item","content":[{"type":"paragraph","content":[{"text":"Notes: Append progress notes as you go","type":"text"}]}]},{"type":"list_item","content":[{"type":"paragraph","content":[{"text":"Summary: Add final summary (PR-style)","type":"text"}]}]},{"type":"list_item","content":[{"type":"paragraph","content":[{"text":"DoD: Check all definition-of-done items","type":"text"}]}]},{"type":"list_item","content":[{"type":"paragraph","content":[{"text":"Done: Set status \"Done\"","type":"text"}]}]}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"Essential Commands","type":"text"}]},{"type":"code_block","attrs":{"wrap":false,"language":"bash"},"content":[{"text":"# Create issue (required: title, type label, priority)\nbacklog task create \"Title\" -d \"Description\" -l bug -p 2 --ac \"AC 1\"\n\n# Work a task\nbacklog task edit 42 -s \"In Progress\" -a @myself\nbacklog task 42 --plain # Read everything\nbacklog task edit 42 --check-ac 1 # Mark AC complete\nbacklog task edit 42 --append-notes \"Progress here\"\nbacklog task edit 42 --final-summary \"PR description\"\nbacklog task edit 42 -s Done\n\n# Search and filter\nbacklog task list -s \"To Do\" --plain\nbacklog search \"topic\" --plain","type":"text"}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"See ","type":"text"},{"text":"references/cli-reference.md","type":"text","marks":[{"type":"code_inline"}]},{"text":" for complete command reference. See ","type":"text"},{"text":"references/priority-labels.md","type":"text","marks":[{"type":"code_inline"}]},{"text":" for priority and labeling guidelines. See ","type":"text"},{"text":"references/issue-creation-guide.md","type":"text","marks":[{"type":"code_inline"}]},{"text":" for detailed issue creation patterns.","type":"text"}]}]},"metadata":{"date":"2026-06-05","name":"backlog-md","author":"@skillopedia","source":{"stars":15,"repo_name":"claude-ctx-plugin","origin_url":"https://github.com/nickcrew/claude-ctx-plugin/blob/HEAD/skills/backlog-md/SKILL.md","repo_owner":"nickcrew","body_sha256":"be082725bb3bb08b64fe67b8ba74668f3fac67fe8aceb914ca58de4aedb1fea4","cluster_key":"b38ab05fe385d039222d94c5eefe5f8358f00edea0f7f9f07a924fc585bddc18","clean_bundle":{"format":"clean-skill-bundle-v1","source":"nickcrew/claude-ctx-plugin/skills/backlog-md/SKILL.md","attachments":[{"id":"8234b12c-096c-5115-8cfc-0e7ea1bc79a7","key":"uploads/10433ee7-ad12-4ae0-b34e-97553e46c6c8/8234b12c-096c-5115-8cfc-0e7ea1bc79a7/attachment.md","path":"references/cli-reference.md","size":7908,"sha256":"d34ecd8dbffc364a0cfcb814d4f51bc8f4459944b7976cafe00fbfe7313acfa5","contentType":"text/markdown; charset=utf-8"},{"id":"9b8e338c-781d-5e65-8f3f-868d1fdc40c1","key":"uploads/10433ee7-ad12-4ae0-b34e-97553e46c6c8/9b8e338c-781d-5e65-8f3f-868d1fdc40c1/attachment.md","path":"references/issue-creation-guide.md","size":7895,"sha256":"d7933ccaca725bb409fd663c37037209a9b73994f4b450996d446b6646033ed2","contentType":"text/markdown; charset=utf-8"},{"id":"a31af63c-0b65-5290-833e-bb360d495c13","key":"uploads/10433ee7-ad12-4ae0-b34e-97553e46c6c8/a31af63c-0b65-5290-833e-bb360d495c13/attachment.md","path":"references/priority-labels.md","size":3990,"sha256":"055d681a0fca80547ae5c17d41d9f53ebf9ba7235d26c3aeabc65ed68e29d24e","contentType":"text/markdown; charset=utf-8"},{"id":"be8e6847-e235-528b-aff9-1cf5eeac981d","key":"uploads/10433ee7-ad12-4ae0-b34e-97553e46c6c8/be8e6847-e235-528b-aff9-1cf5eeac981d/attachment.md","path":"references/task-workflow.md","size":4607,"sha256":"0faa6b328477d76200d51712a7593dcca9772604a8a8f55876337bbd65ca572d","contentType":"text/markdown; charset=utf-8"}],"bundle_sha256":"60cb01530d3d7d3a89f0a87e786748e94372d2ec6cdc4aea54bd3d7ee7d348f5","attachment_count":4,"text_attachments":4,"attachment_storage":"skillopedia-attachments-v1","binary_attachments":0,"excluded_attachments":[]},"cluster_size":1,"skill_md_path":"skills/backlog-md/SKILL.md","import_metadata":{"date":"2026-06-05","author":"@skillopedia","version":"v1","category":"security","category_label":"Security"},"exact_dupes_collapsed_into_this":0},"version":"v1","category":"security","keywords":["task tracking","backlog CLI","project management","issue filing","agent workflows","backlog","backlog md"],"import_tag":"clean-skills-v1","description":"Task tracking system for agents via Backlog.md CLI. Use when creating deferred issues during implementation, filing audit findings, working assigned tasks, or managing project work. Optimized for agent workflows: structured issue filing, priority/labeling system, and task completion tracking."}},"renderedAt":1782987061408}

Important: agents should read /llm.txt, /llms.txt, or /.well-known/skills.json to discover the public Skillopedia API.