[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6CY9PJ981E3XNQ1PVA0FCCF":3,"skill-same:01M6CY9PJ981E3XNQ1PVA0FCCF":68},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":13,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":48,"install":49,"resources":61},"01M6CY9PJ981E3XNQ1PVA0FCCF","file-todos",null,"This skill should be used when managing the file-based todo tracking system in the todos\u002F directory. It provides workflows for creating todos, managing status and dependencies, conducting triage, and integrating with slash commands and code review processes.","The-Rabak\u002Fnaysmith","The-Rabak","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F44833742?v=4","01M6CY211HB58Y8JNWWEV9FGN1","01M6CY8HJW3TE1AQW1F13PHYB2",0,"GPL-2.0","https:\u002F\u002Fgithub.com\u002FThe-Rabak\u002Fnaysmith\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ffile-todos\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36],"file","file todos","code review","directory","review","triage","workflows","status","code","system","tracking","todo","dependencies","commands","2026-11-10 10:12:30",false,"---\nname: file-todos\ndescription: This skill should be used when managing the file-based todo tracking system in the todos\u002F directory. It provides workflows for creating todos, managing status and dependencies, conducting triage, and integrating with slash commands and code review processes.\ndisable-model-invocation: true\n---\n\n# File-Based Todo Tracking Skill\n\n## Overview\n\nThe `todos\u002F` directory contains a file-based tracking system for managing code review feedback, technical debt, feature requests, and work items. Each todo is a markdown file with YAML frontmatter and structured sections.\n\nThis skill should be used when:\n- Creating new todos from findings or feedback\n- Managing todo lifecycle (pending → ready → complete)\n- Triaging pending items for approval\n- Checking or managing dependencies\n- Converting PR comments or code findings into tracked work\n- Updating work logs during todo execution\n\n## File Naming Convention\n\nTodo files follow this naming pattern:\n\n```\n{issue_id}-{status}-{priority}-{description}.md\n```\n\n**Components:**\n- **issue_id**: Sequential number (001, 002, 003...) - never reused\n- **status**: `pending` (needs triage), `ready` (approved), `complete` (done)\n- **priority**: `p1` (critical), `p2` (important), `p3` (nice-to-have)\n- **description**: kebab-case, brief description\n\n**Examples:**\n```\n001-pending-p1-mailer-test.md\n002-ready-p1-fix-n-plus-1.md\n005-complete-p2-refactor-csv.md\n```\n\n## File Structure\n\nEach todo is a markdown file with YAML frontmatter and structured sections. Use the template at [todo-template.md](.\u002Fassets\u002Ftodo-template.md) as a starting point when creating new todos.\n\n**Required sections:**\n- **Problem Statement** - What is broken, missing, or needs improvement?\n- **Findings** - Investigation results, root cause, key discoveries\n- **Proposed Solutions** - Multiple options with pros\u002Fcons, effort, risk\n- **Recommended Action** - Clear plan (filled during triage)\n- **Acceptance Criteria** - Testable checklist items\n- **Work Log** - Chronological record with date, actions, learnings\n\n**Optional sections:**\n- **Technical Details** - Affected files, related components, DB changes\n- **Resources** - Links to errors, tests, PRs, documentation\n- **Notes** - Additional context or decisions\n\n**YAML frontmatter fields:**\n```yaml\n---\nstatus: ready              # pending | ready | complete\npriority: p1              # p1 | p2 | p3\nissue_id: \"002\"\ntags: [laravel, performance, database]\ndependencies: [\"001\"]     # Issue IDs this is blocked by\n---\n```\n\n## Common Workflows\n\n### Creating a New Todo\n\n**To create a new todo from findings or feedback:**\n\n1. Determine next issue ID: `ls todos\u002F | grep -o '^[0-9]\\+' | sort -n | tail -1`\n2. Copy template: `cp assets\u002Ftodo-template.md todos\u002F{NEXT_ID}-pending-{priority}-{description}.md`\n3. Edit and fill required sections:\n   - Problem Statement\n   - Findings (if from investigation)\n   - Proposed Solutions (multiple options)\n   - Acceptance Criteria\n   - Add initial Work Log entry\n4. Determine status: `pending` (needs triage) or `ready` (pre-approved)\n5. Add relevant tags for filtering\n\n**When to create a todo:**\n- Requires more than 15-20 minutes of work\n- Needs research, planning, or multiple approaches considered\n- Has dependencies on other work\n- Requires manager approval or prioritization\n- Part of larger feature or refactor\n- Technical debt needing documentation\n\n**When to act immediately instead:**\n- Issue is trivial (\u003C 15 minutes)\n- Complete context available now\n- No planning needed\n- User explicitly requests immediate action\n- Simple bug fix with obvious solution\n\n### Triaging Pending Items\n\n**To triage pending todos:**\n\n1. List pending items: `ls todos\u002F*-pending-*.md`\n2. For each todo:\n   - Read Problem Statement and Findings\n   - Review Proposed Solutions\n   - Make decision: approve, defer, or modify priority\n3. Update approved todos:\n   - Rename file: `mv {file}-pending-{pri}-{desc}.md {file}-ready-{pri}-{desc}.md`\n   - Update frontmatter: `status: pending` → `status: ready`\n   - Fill \"Recommended Action\" section with clear plan\n   - Adjust priority if different from initial assessment\n4. Deferred todos stay in `pending` status\n\n**Use slash command:** `\u002Ftriage` for interactive approval workflow\n\n### Managing Dependencies\n\n**To track dependencies:**\n\n```yaml\ndependencies: [\"002\", \"005\"]  # This todo blocked by issues 002 and 005\ndependencies: []               # No blockers - can work immediately\n```\n\n**To check what blocks a todo:**\n```bash\ngrep \"^dependencies:\" todos\u002F003-*.md\n```\n\n**To find what a todo blocks:**\n```bash\ngrep -l 'dependencies:.*\"002\"' todos\u002F*.md\n```\n\n**To verify blockers are complete before starting:**\n```bash\nfor dep in 001 002 003; do\n  [ -f \"todos\u002F${dep}-complete-*.md\" ] || echo \"Issue $dep not complete\"\ndone\n```\n\n### Updating Work Logs\n\n**When working on a todo, always add a work log entry:**\n\n```markdown\n### YYYY-MM-DD - Session Title\n\n**By:** Claude Code \u002F Developer Name\n\n**Actions:**\n- Specific changes made (include file:line references)\n- Commands executed\n- Tests run\n- Results of investigation\n\n**Learnings:**\n- What worked \u002F what didn't\n- Patterns discovered\n- Key insights for future work\n```\n\nWork logs serve as:\n- Historical record of investigation\n- Documentation of approaches attempted\n- Knowledge sharing for team\n- Context for future similar work\n\n### Completing a Todo\n\n**To mark a todo as complete:**\n\n1. Verify all acceptance criteria checked off\n2. Update Work Log with final session and results\n3. Rename file: `mv {file}-ready-{pri}-{desc}.md {file}-complete-{pri}-{desc}.md`\n4. Update frontmatter: `status: ready` → `status: complete`\n5. Check for unblocked work: `grep -l 'dependencies:.*\"002\"' todos\u002F*-ready-*.md`\n6. Commit with issue reference: `feat: resolve issue 002`\n\n## Integration with Development Workflows\n\n| Trigger | Flow | Tool |\n|---------|------|------|\n| Code review | `\u002Fworkflows:review` → Findings → `\u002Ftriage` → Todos | Review agent + skill |\n| PR comments | `\u002Fresolve_pr_parallel` → Individual fixes → Todos | gh CLI + skill |\n| Code TODOs | `\u002Fresolve_todo_parallel` → Fixes + Complex todos | Agent + skill |\n| Planning | Brainstorm → Create todo → Work → Complete | Skill |\n| Feedback | Discussion → Create todo → Triage → Work | Skill + slash |\n\n## Quick Reference Commands\n\n**Finding work:**\n```bash\n# List highest priority unblocked work\ngrep -l 'dependencies: \\[\\]' todos\u002F*-ready-p1-*.md\n\n# List all pending items needing triage\nls todos\u002F*-pending-*.md\n\n# Find next issue ID\nls todos\u002F | grep -o '^[0-9]\\+' | sort -n | tail -1 | awk '{printf \"%03d\", $1+1}'\n\n# Count by status\nfor status in pending ready complete; do\n  echo \"$status: $(ls -1 todos\u002F*-$status-*.md 2>\u002Fdev\u002Fnull | wc -l)\"\ndone\n```\n\n**Dependency management:**\n```bash\n# What blocks this todo?\ngrep \"^dependencies:\" todos\u002F003-*.md\n\n# What does this todo block?\ngrep -l 'dependencies:.*\"002\"' todos\u002F*.md\n```\n\n**Searching:**\n```bash\n# Search by tag\ngrep -l \"tags:.*laravel\" todos\u002F*.md\n\n# Search by priority\nls todos\u002F*-p1-*.md\n\n# Full-text search\ngrep -r \"payment\" todos\u002F\n```\n\n## Key Distinctions\n\n**File-todos system (this skill):**\n- Markdown files in `todos\u002F` directory\n- Development\u002Fproject tracking\n- Standalone markdown files with YAML frontmatter\n- Used by humans and agents\n\n**Laravel Todo model:**\n- Database model in `app\u002FModels\u002FTodo.php`\n- User-facing feature in the application\n- Eloquent CRUD operations\n- Different from this file-based system\n\n**TodoWrite tool:**\n- In-memory task tracking during agent sessions\n- Temporary tracking for single conversation\n- Not persisted to disk\n- Different from both systems above\n","# File-Based Todo Tracking Skill\n\n## Overview\n\nThe `todos\u002F` directory contains a file-based tracking system for managing code review feedback, technical debt, feature requests, and work items. Each todo is a markdown file with YAML frontmatter and structured sections.\n\nThis skill should be used when:\n- Creating new todos from findings or feedback\n- Managing todo lifecycle (pending → ready → complete)\n- Triaging pending items for approval\n- Checking or managing dependencies\n- Converting PR comments or code findings into tracked work\n- Updating work logs during todo execution\n\n## File Naming Convention\n\nTodo files follow this naming pattern:\n\n```\n{issue_id}-{status}-{priority}-{description}.md\n```\n\n**Components:**\n- **issue_id**: Sequential number (001, 002, 003...) - never reused\n- **status**: `pending` (needs triage), `ready` (approved), `complete` (done)\n- **priority**: `p1` (critical), `p2` (important), `p3` (nice-to-have)\n- **description**: kebab-case, brief description\n\n**Examples:**\n```\n001-pending-p1-mailer-test.md\n002-ready-p1-fix-n-plus-1.md\n005-complete-p2-refactor-csv.md\n```\n\n## File Structure\n\nEach todo is a markdown file with YAML frontmatter and structured sections. Use the template at [todo-template.md](.\u002Fassets\u002Ftodo-template.md) as a starting point when creating new todos.\n\n**Required sections:**\n- **Problem Statement** - What is broken, missing, or needs improvement?\n- **Findings** - Investigation results, root cause, key discoveries\n- **Proposed Solutions** - Multiple options with pros\u002Fcons, effort, risk\n- **Recommended Action** - Clear plan (filled during triage)\n- **Acceptance Criteria** - Testable checklist items\n- **Work Log** - Chronological record with date, actions, learnings\n\n**Optional sections:**\n- **Technical Details** - Affected files, related components, DB changes\n- **Resources** - Links to errors, tests, PRs, documentation\n- **Notes** - Additional context or decisions\n\n**YAML frontmatter fields:**\n```yaml\n---\nstatus: ready              # pending | ready | complete\npriority: p1              # p1 | p2 | p3\nissue_id: \"002\"\ntags: [laravel, performance, database]\ndependencies: [\"001\"]     # Issue IDs this is blocked by\n---\n```\n\n## Common Workflows\n\n### Creating a New Todo\n\n**To create a new todo from findings or feedback:**\n\n1. Determine next issue ID: `ls todos\u002F | grep -o '^[0-9]\\+' | sort -n | tail -1`\n2. Copy template: `cp assets\u002Ftodo-template.md todos\u002F{NEXT_ID}-pending-{priority}-{description}.md`\n3. Edit and fill required sections:\n   - Problem Statement\n   - Findings (if from investigation)\n   - Proposed Solutions (multiple options)\n   - Acceptance Criteria\n   - Add initial Work Log entry\n4. Determine status: `pending` (needs triage) or `ready` (pre-approved)\n5. Add relevant tags for filtering\n\n**When to create a todo:**\n- Requires more than 15-20 minutes of work\n- Needs research, planning, or multiple approaches considered\n- Has dependencies on other work\n- Requires manager approval or prioritization\n- Part of larger feature or refactor\n- Technical debt needing documentation\n\n**When to act immediately instead:**\n- Issue is trivial (\u003C 15 minutes)\n- Complete context available now\n- No planning needed\n- User explicitly requests immediate action\n- Simple bug fix with obvious solution\n\n### Triaging Pending Items\n\n**To triage pending todos:**\n\n1. List pending items: `ls todos\u002F*-pending-*.md`\n2. For each todo:\n   - Read Problem Statement and Findings\n   - Review Proposed Solutions\n   - Make decision: approve, defer, or modify priority\n3. Update approved todos:\n   - Rename file: `mv {file}-pending-{pri}-{desc}.md {file}-ready-{pri}-{desc}.md`\n   - Update frontmatter: `status: pending` → `status: ready`\n   - Fill \"Recommended Action\" section with clear plan\n   - Adjust priority if different from initial assessment\n4. Deferred todos stay in `pending` status\n\n**Use slash command:** `\u002Ftriage` for interactive approval workflow\n\n### Managing Dependencies\n\n**To track dependencies:**\n\n```yaml\ndependencies: [\"002\", \"005\"]  # This todo blocked by issues 002 and 005\ndependencies: []               # No blockers - can work immediately\n```\n\n**To check what blocks a todo:**\n```bash\ngrep \"^dependencies:\" todos\u002F003-*.md\n```\n\n**To find what a todo blocks:**\n```bash\ngrep -l 'dependencies:.*\"002\"' todos\u002F*.md\n```\n\n**To verify blockers are complete before starting:**\n```bash\nfor dep in 001 002 003; do\n  [ -f \"todos\u002F${dep}-complete-*.md\" ] || echo \"Issue $dep not complete\"\ndone\n```\n\n### Updating Work Logs\n\n**When working on a todo, always add a work log entry:**\n\n```markdown\n### YYYY-MM-DD - Session Title\n\n**By:** Claude Code \u002F Developer Name\n\n**Actions:**\n- Specific changes made (include file:line references)\n- Commands executed\n- Tests run\n- Results of investigation\n\n**Learnings:**\n- What worked \u002F what didn't\n- Patterns discovered\n- Key insights for future work\n```\n\nWork logs serve as:\n- Historical record of investigation\n- Documentation of approaches attempted\n- Knowledge sharing for team\n- Context for future similar work\n\n### Completing a Todo\n\n**To mark a todo as complete:**\n\n1. Verify all acceptance criteria checked off\n2. Update Work Log with final session and results\n3. Rename file: `mv {file}-ready-{pri}-{desc}.md {file}-complete-{pri}-{desc}.md`\n4. Update frontmatter: `status: ready` → `status: complete`\n5. Check for unblocked work: `grep -l 'dependencies:.*\"002\"' todos\u002F*-ready-*.md`\n6. Commit with issue reference: `feat: resolve issue 002`\n\n## Integration with Development Workflows\n\n| Trigger | Flow | Tool |\n|---------|------|------|\n| Code review | `\u002Fworkflows:review` → Findings → `\u002Ftriage` → Todos | Review agent + skill |\n| PR comments | `\u002Fresolve_pr_parallel` → Individual fixes → Todos | gh CLI + skill |\n| Code TODOs | `\u002Fresolve_todo_parallel` → Fixes + Complex todos | Agent + skill |\n| Planning | Brainstorm → Create todo → Work → Complete | Skill |\n| Feedback | Discussion → Create todo → Triage → Work | Skill + slash |\n\n## Quick Reference Commands\n\n**Finding work:**\n```bash\n# List highest priority unblocked work\ngrep -l 'dependencies: \\[\\]' todos\u002F*-ready-p1-*.md\n\n# List all pending items needing triage\nls todos\u002F*-pending-*.md\n\n# Find next issue ID\nls todos\u002F | grep -o '^[0-9]\\+' | sort -n | tail -1 | awk '{printf \"%03d\", $1+1}'\n\n# Count by status\nfor status in pending ready complete; do\n  echo \"$status: $(ls -1 todos\u002F*-$status-*.md 2>\u002Fdev\u002Fnull | wc -l)\"\ndone\n```\n\n**Dependency management:**\n```bash\n# What blocks this todo?\ngrep \"^dependencies:\" todos\u002F003-*.md\n\n# What does this todo block?\ngrep -l 'dependencies:.*\"002\"' todos\u002F*.md\n```\n\n**Searching:**\n```bash\n# Search by tag\ngrep -l \"tags:.*laravel\" todos\u002F*.md\n\n# Search by priority\nls todos\u002F*-p1-*.md\n\n# Full-text search\ngrep -r \"payment\" todos\u002F\n```\n\n## Key Distinctions\n\n**File-todos system (this skill):**\n- Markdown files in `todos\u002F` directory\n- Development\u002Fproject tracking\n- Standalone markdown files with YAML frontmatter\n- Used by humans and agents\n\n**Laravel Todo model:**\n- Database model in `app\u002FModels\u002FTodo.php`\n- User-facing feature in the application\n- Eloquent CRUD operations\n- Different from this file-based system\n\n**TodoWrite tool:**\n- In-memory task tracking during agent sessions\n- Temporary tracking for single conversation\n- Not persisted to disk\n- Different from both systems above\n",{"name":5,"description":7,"disable-model-invocation":42},true,"main","b097d394a335a9ec3c8a02d64e111f1a9c96703d",".github\u002Fskills\u002Ffile-todos","https:\u002F\u002Fgithub.com\u002FThe-Rabak\u002Fnaysmith","https:\u002F\u002Fgithub.com\u002FThe-Rabak","2026-03-04 03:03:05",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":42},[51,54,57],{"tool":52,"command":53},"npx","npx skills add The-Rabak\u002Fnaysmith --skill file-todos",{"tool":55,"command":56},"bunx","bunx skills add The-Rabak\u002Fnaysmith --skill file-todos",{"tool":58,"command":59},"pnpm","pnpm dlx skills add The-Rabak\u002Fnaysmith --skill file-todos","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FThe-Rabak\u002Fnaysmith\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ffile-todos\u002FSKILL.md",[62],{"path":63,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":67},"assets\u002Ftodo-template.md","ASSET","资产文件",3747,"https:\u002F\u002Fgithub.com\u002FThe-Rabak\u002Fnaysmith\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ffile-todos\u002Fassets\u002Ftodo-template.md",[69,80,92,105,120,134],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":37},"01M6CYBMHFVAMC4T3J8QFYN42M","workflows-work","Execute work plans efficiently while maintaining quality and finishing features","https:\u002F\u002Fgithub.com\u002FThe-Rabak\u002Fnaysmith\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fworkflows-work\u002FSKILL.md",[],[76,77,29,78,79],"workflows work","work","execute","quality",{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":37},"01M6CYBJ1KP7W3X8HEG49KST9Q","workflows-review","Perform exhaustive code reviews using multi-agent analysis, ultra-thinking, and worktrees","https:\u002F\u002Fgithub.com\u002FThe-Rabak\u002Fnaysmith\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fworkflows-review\u002FSKILL.md",[],[87,29,27,88,89,90,91,31],"workflows review","thinking","worktrees","multi-agent","analysis",{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":37},"01M6CYBEW8DDBXW62Q2CA29BPR","workflows-plan","Transform feature descriptions into well-structured project plans following conventions","https:\u002F\u002Fgithub.com\u002FThe-Rabak\u002Fnaysmith\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fworkflows-plan\u002FSKILL.md",[],[29,99,100,101,102,103,104],"workflows plan","plan","project","structured","following conventions","conventions",{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":114,"publishedAt":37},"01M6CYBBKAHJJ85JC2PS380TGZ","workflows-compound","Document a recently solved problem to compound your team's knowledge","https:\u002F\u002Fgithub.com\u002FThe-Rabak\u002Fnaysmith\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fworkflows-compound\u002FSKILL.md",[111],{"categoryNo":112,"categoryName":113,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000021","资料检索与研究",[115,116,29,117,118,119],"compound","workflows compound","document","knowledge","team",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":37},"01M6CYB9062GMP8VSA7N7PB4NW","workflows-brainstorm","Explore requirements and approaches through collaborative dialogue before planning implementation","https:\u002F\u002Fgithub.com\u002FThe-Rabak\u002Fnaysmith\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Fworkflows-brainstorm\u002FSKILL.md",[],[127,128,29,129,130,131,132,133],"workflows brainstorm","brainstorm","planning","requirements","explore","implementation","dialogue",{"skillNo":135,"name":28,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":37},"01M6CYB6S7GKWH62CRV3K79MHW","Triage and categorize findings for the CLI todo system","https:\u002F\u002Fgithub.com\u002FThe-Rabak\u002Fnaysmith\u002Fblob\u002Fmain\u002F.github\u002Fskills\u002Ftriage\u002FSKILL.md",[],[28,32,140,34,141],"categorize","cli"]