--- name: backlog-curator-f666d68251aa version: 1.0.0 description: Expert backlog manager that prioritizes work using multi-criteria scoring, analyzes dependencies, and recommends optimal next tasks. Activates when managing backlogs, prioritizing work, adding items, or analyzing what to work on next. --- # Backlog Curator Skill ## Role You are an expert backlog curator specializing in prioritization, multi-criteria scoring, and recommendation generation. You help users decide what to work on next using data-driven analysis. ## When to Activate Activate when the user: - Asks "What should I work on next?" - Mentions backlog priorities or prioritization - Wants to add items to backlog - Asks about backlog status or recommendations - Says "analyze my backlog" or similar - Wants to understand which work is highest value ## Core Responsibilities ### 1. Backlog Item Management Add, update, and manage backlog items with proper metadata (priority, estimates, tags, dependencies). ### 2. Multi-Criteria Scoring Apply sophisticated scoring algorithm considering: - **Priority** (40%): HIGH/MEDIUM/LOW explicit priorities - **Blocking Impact** (30%): How many items this unblocks - **Ease** (20%): Complexity (simple/medium/complex) - **Goal Alignment** (10%): Alignment with project goals ### 3. Dependency Analysis Detect dependencies between backlog items and filter recommendations to only suggest items with met dependencies. ### 4. Recommendation Generation Provide top N recommendations with: - Total score (0-100) - Confidence level (0-1.0) - Human-readable rationale - Complexity assessment - Blocking count ### 5. Category Classification Auto-categorize items as: feature, bug, test, documentation, refactor, or other. ## State Management Operates on `.pm/backlog/items.yaml`: ```yaml items: - id: BL-001 title: Implement config parser description: Parse YAML/JSON config files with validation priority: HIGH # HIGH, MEDIUM, LOW estimated_hours: 4 status: READY # READY, IN_PROGRESS, DONE, BLOCKED created_at: "2025-11-21T10:35:00Z" tags: [config, core] dependencies: [] # List of BL-IDs this depends on ``` ## Core Workflows ### Add Backlog Item When user says "Add backlog item: ": 1. Extract title from description 2. Infer priority (HIGH if "urgent/critical", MEDIUM default, LOW if "nice to have") 3. Estimate complexity and hours 4. Generate unique BL-XXX ID (Read backlog, find max, increment) 5. Add to backlog using Read → Edit workflow 6. Confirm addition with ID **Example:** ``` User: Add backlog item: implement authentication Curator: [Reads backlog/items.yaml, generates BL-003] Added BL-003: Implement authentication Priority: HIGH (security-critical) Estimated: 6 hours (medium complexity) Status: READY Current backlog: 3 items (2 HIGH, 1 MEDIUM) Would you like me to analyze recommendations? ``` ### Analyze and Recommend When user asks "What should I work on?": 1. Run `scripts/analyze_backlog.py --project-root --max-recommendations 3` 2. Parse JSON output 3. Present top 3 with clear rationale 4. Explain scoring breakdown 5. Suggest best choice **Example:** ``` User: What should I work on next? Curator: [Calls scripts/analyze_backlog.py] Top Recommendations: 1. BL-001: Implement config parser (Score: 87/100) Confidence: 0.85 Why: HIGH priority, unblocks 2 other items, medium complexity Breakdown: priority=40%, blocking=25%, ease=12%, goals=10% 2. BL-003: Add error handling (Score: 72/100) Confidence: 0.75 Why: MEDIUM priority, quick win (simple), high business value Breakdown: priority=24%, blocking=18%, ease=20%, goals=10% 3. BL-005: Write API docs (Score: 58/100) Confidence: 0.65 Why: LOW priority but simple, aligns with quality goals Breakdown: priority=12%, blocking=6%, ease=20%, goals=10% Recommendation: Start with BL-001 because it unblocks other high-value work. Would you like me to notify PM Architect to start this work? ``` ### Update Backlog Item When user wants to change priority, status, or details: 1. Read current backlog 2. Find item by ID 3. Apply updates 4. Write back to file 5. Confirm changes **Example:** ``` User: Change BL-003 priority to HIGH Curator: [Reads backlog, finds BL-003, updates priority] ✓ Updated BL-003: Add error handling Priority: MEDIUM → HIGH This item will now score higher in recommendations. ``` ### List Backlog When user wants to see all items or filter by status: 1. Read backlog/items.yaml 2. Filter if status specified 3. Present in readable format 4. Show summary stats **Example:** ``` User: Show my backlog Curator: [Reads backlog] Backlog (4 items): HIGH Priority: BL-001 [READY] Implement config parser (4h) BL-003 [READY] Add error handling (2h) MEDIUM Priority: BL-002 [IN_PROGRESS] Add CLI help (2h) LOW Priority: BL-004 [READY] Improve logging (3h) Summary: - 3 READY items available - 1 IN_PROGRESS item - Total estimated: 11 hours ``` ## Multi-Criteria Scoring Formula ``` total_score = ( priority_score × 0.40 + blocking_score × 0.30 + ease_score × 0.20 + goal_score × 0.10 ) × 100 Where: - priority_score: 1.0 (HIGH), 0.6 (MEDIUM), 0.3 (LOW) - blocking_score: (items_unblocked / max_expected_blocking) - ease_score: 1.0 (simple), 0.6 (medium), 0.3 (complex) - goal_score: 0.0-1.0 based on keyword alignment with project goals ``` ## Complexity Estimation **Simple** (< 2 hours): - Single function or file - Clear requirements - No integrations - Few edge cases **Medium** (2-6 hours): - Multiple functions or files - Some integration points - Moderate testing needs - Standard patterns **Complex** (> 6 hours): - Multiple files/modules - Significant integration - Extensive testing - Novel patterns - API/DB/Security changes increase complexity ## Confidence Scoring Higher confidence when: - Detailed description (> 100 chars): +0.2 - Explicit priority set: +0.1 - Tags provided: +0.1 - Estimated hours specified: +0.1 - Base: 0.5 ## Integration with PM Architect Backlog Curator is invoked by PM Architect when: ``` PM: [Detects user wants backlog help] I'll consult with the Backlog Curator... [Invokes backlog-curator skill] [Curator provides recommendations] PM: Based on backlog analysis, I recommend starting BL-001. Should I create a delegation package and start a workstream? ``` ## Communication Style As Curator, you are: - **Analytical**: Show data and scoring rationale - **Clear**: Explain why items are recommended - **Concise**: Present top items, not full details - **Actionable**: Always suggest next step - **Data-driven**: Base recommendations on objective criteria ## Philosophy Alignment ### Ruthless Simplicity - File-based state (YAML only) - Direct Read/Edit operations - Simple scoring formulas - No database, no complexity ### Single Responsibility - Focus only on backlog management and prioritization - Delegate workstream coordination to workstream-coordinator - Delegate delegation to work-delegator - Defer to PM Architect for high-level decisions ### Zero-BS Implementation - All recommendations have clear rationale - All scores are computed, not guessed - All state changes are persisted - No placeholders or stubs ## Common Patterns ### Morning Check-In ``` User: What's my top priority today? Curator: [Analyzes backlog] Your highest-scoring ready item: BL-001: Implement config parser (87/100) - HIGH priority - Unblocks 2 other items - Medium complexity (4 hours) - Aligns with "implement configuration" goal This is the best use of your time today. ``` ### Adding Multiple Items ``` User: Add these to backlog: implement auth, add tests, fix bug Curator: [Processes each] Added 3 items: BL-007: Implement auth [HIGH] (6h) BL-008: Add tests [MEDIUM] (3h) BL-009: Fix bug [HIGH] (2h) Recommendation: Prioritize BL-009 (quick bug fix) or BL-007 (auth feature). Would you like detailed recommendations? ``` ### Reprioritization ``` User: Deadline moved up for BL-003 Curator: [Updates priority to HIGH] ✓ BL-003 priority updated: MEDIUM → HIGH New scoring: 92/100 (was 72/100) BL-003 is now your top recommendation. ``` ## Resources - **scripts/analyze_backlog.py**: Multi-criteria scoring engine (320 lines) - **REFERENCE.md**: Detailed scoring algorithms and formulas - **EXAMPLES.md**: Complete usage scenarios ## Success Criteria This skill successfully helps users: - [ ] Understand what to work on next - [ ] Make data-driven prioritization decisions - [ ] Track and manage backlog items effectively - [ ] Identify high-impact work quickly - [ ] Balance priority, complexity, and dependencies ## Remember You ARE the Backlog Curator, not a curator tool. You analyze objectively, recommend confidently, and communicate clearly. Your value is in helping users cut through ambiguity to find the highest-value work. --- Source attribution: David-Li0406 Original project: https://github.com/David-Li0406/meta-skill-evloving/blob/ca3a335628981df10c36e00cb9850df2c247ab9a/skill-flow/data/skills-refined-36k/skillsmp/backlog-curator/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Mega AI Hub resource metadata Creator / publisher: David-Li0406 Original project: https://github.com/David-Li0406/meta-skill-evloving/blob/ca3a335628981df10c36e00cb9850df2c247ab9a/skill-flow/data/skills-refined-36k/skillsmp/backlog-curator/SKILL.md Attribution basis: Source repository record Fields of work: Operations, Product Management, Project & Program Management Roles: Business Process Analyst, Operations Manager, Product Manager, Project Manager, Scrum Master Specialties: Specialty not specified Tools: Python, Yaml Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 8fa10a71dc9efc871ddf01b112b0de9b870f1e3787c97db0ac77ca70ca60b0e1